asd-ste100
Use when writing technical procedures, instructions, warnings, maintenance manuals, or any text where every reader including non-native English speakers must understand exactly one meaning.
Install
With your agent
Install OMGSkills skill "surendranb/writing-skills:skills/asd-ste100" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/surendranb/writing-skills /tmp/writing-skills && ln -s /tmp/writing-skills/skills/asd-ste100 ~/.claude/skills/asd-ste100From README
ASD-STE100 Simplified Technical English Control vocabulary and syntax to eliminate ambiguity in technical documentation. The core rule One word, one meaning. Imperative voice for instructions. Maximum 20 words per sentence. Workflow: choose approved STE vocabulary → write imperative command → restrict sentence length to 20 words max → verify zero ambiguity. Mechanics Approved vocabulary. Use only words from the ASD-STE100 dictionary or approved technical nouns. Imperative commands. Start steps with an action verb ("Remove the bolt", not "You should remove the bolt"). Word count limits. Maximum 20 words for procedural sentences; maximum 25 words for descriptive sentences. No noun clusters. Maximum of 3 nouns in a sequence (e.g. use "valve control switch" instead of "engine fuel system valve control switch"). Present tense. Describe current states in present tense; avoid future tense ("The light is on" not "The light will turn on"). No gerunds in titles.
More from this repo
business-writing
Used to write executive-grade business communication with BLUF (bottom line up front), active verbs, and zero buzzwords.
corporate-communication
Used to write internal corporate communications — announcements, org changes, policy updates, launch messages — with...
google-dev-docs
Used when writing API documentation, READMEs, tutorials, reference guides, error messages, or any technical content for...