Simplified Technical English Writer
The problem
Technical documentation and runbooks often suffer from ambiguity, long sentences, and AI-generated filler. This causes non-native English speakers or stressed engineers to misinterpret critical instructions, leading to errors and downtime.
What it does
Enforces the 53 rules of the ASD-STE100 Simplified Technical English standard.
Shortens sentences to a 20-word limit for procedures and 25-word limit for descriptions.
Replaces ambiguous verbs like "check" or "ensure" with standardized, approved vocabulary.
Restructures instructions to place conditions before commands for immediate clarity.
Eliminates "AI slop" like "leverage," "comprehensive," and "seamlessly."
Why this beats prompting it yourself
Generic LLM prompts for "simple text" often result in childish tone or loss of technical detail. This skill applies a specific aerospace engineering standard with precise word-count enforcement and vocabulary discipline that basic prompts cannot maintain consistently across long documents.
Use cases
Rewrite DevOps runbooks to prevent human error during incident response.
Standardize API documentation for international developer audiences.
Format system error messages to be actionable and free of polite filler.
Audit existing README files for grammatical ambiguity and translation readiness.
Known limitations
STE is designed for technical facts and procedures. It is not suitable for marketing copy, creative writing, or brand storytelling as it intentionally removes persuasive and decorative language.
