ste-writing

Rewrite prose into ASD-STE100 Simplified Technical English with a linting script.

Updated Jul 17, 2026
One-click install
npx skills add https://github.com/unnxt30/skills --skill ste-writing-unnxt30
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ste-writing
Source: https://github.com/unnxt30/skills/tree/main/ste-writing
Command: npx skills add https://github.com/unnxt30/skills --skill ste-writing-unnxt30

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about ste-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make AI-generated documentation not sound like AI?

Rewrite the text with Simplified Technical English rules: active voice, one name per thing, short common words, and sentences under 20 words. This Skill applies those rules and its linter flags marketing adjectives, passive voice, and banned words like utilize and leverage.

What is ASD-STE100 Simplified Technical English?

ASD-STE100 is a controlled language standard for technical documentation that restricts vocabulary and sentence structure for clarity. This Skill implements its core mechanical rules, such as active voice and sentence length caps, while noting that full compliance also needs human judgment.

What is the difference between strict and STE-flavored mode?

Strict mode applies every rule including both length caps and is meant for procedures, runbooks, safety text, and error messages. STE-flavored mode keeps sentence, paragraph, and active-voice discipline but relaxes the limited dictionary so general prose reads naturally.

Does the STE linter check code blocks?

No. The ste-linter.py script strips fenced code blocks and inline code before analysis, so identifiers and command syntax are not flagged. It only lints prose, matching the rule that STE applies to writing, never to code.

What are the limitations of automated STE checking?

The linter catches mechanical issues like long sentences, semicolons, contractions, and banned words, but it cannot judge whether a sentence makes sense or uses the right technical noun. The Skill fixes the form of the text, not the truth of its content.