What problem does it solve? Technical prose often sounds like generic AI output: marketing adjectives, passive voice, long sentences, and vague verbs. This Skill rewrites documentation, READMEs, PR descriptions, error messages, and release notes into ASD-STE100 Simplified Technical English so the text reads plain, direct, and human. ## Core Features & Use Cases - STE Rewriting Rules: Enforces one name per thing, short common words, active voice, plain verbs, 20-word sentence caps, no semicolons, and no contractions. - Two Modes: Strict mode for procedures, runbooks, and safety text; STE-flavored mode for general prose like READMEs and PR descriptions. - Built-in Linter: The ste-linter.py script counts violations per category (long sentences, passive voice, banned words, marketing adjectives, phrasal verbs) and reports totals per 100 words. - Use Case: Paste a draft README section and ask for an STE-flavored rewrite, then run ste-linter.py on the result to confirm zero semicolons, no banned words, and no sentence over 20 words. ## Quick Start Rewrite the attached README draft in STE-flavored Simplified Technical English and lint the result with ste-linter.py.