ste-writing

Rewrite prose into ASD-STE100 Simplified Technical English with strict and flavored modes.

49|11|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/vstorm-co/agenticos --skill ste-writing-vstorm-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ste-writing
Source: https://github.com/vstorm-co/agenticos/tree/main/.claude/skills/ste-writing
Command: npx skills add https://github.com/vstorm-co/agenticos --skill ste-writing-vstorm-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated and human-drafted prose often sounds vague, wordy, or inconsistent, making documentation hard to read and translate. This Skill rewrites docs, READMEs, PR descriptions, error messages, release notes, and comments into ASD-STE100 Simplified Technical English, a controlled writing standard that enforces clarity. ## Core Features & Use Cases - Controlled vocabulary and grammar rules: Enforces one name per thing, short common words, active voice, plain verbs, and bans marketing adjectives, semicolons, and contractions. - Two modes: Strict mode applies every rule and length cap for procedures, runbooks, and safety text; STE-flavored mode relaxes the dictionary lockdown for general prose like READMEs and PR descriptions. - Built-in self-lint: A six-step checklist splits long sentences, expands contractions, fixes passive voice, and unifies terminology before returning text. - Use Case: Paste a wordy README section and ask for an STE rewrite; the Skill returns plain, active-voice prose with sentences under 20 words and no filler. ## Quick Start Rewrite the attached README section in Simplified Technical English using STE-flavored mode.

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 prose with a controlled style like ASD-STE100 Simplified Technical English. It enforces short common words, active voice, plain verbs, and sentence length caps, which mechanically removes the vague filler and stacked phrasing typical of AI output.

What is ASD-STE100 Simplified Technical English used for?▼

ASD-STE100 is a controlled writing standard for technical documentation that restricts vocabulary and grammar to improve clarity and translatability. It is used for procedures, runbooks, safety text, error messages, and general docs like READMEs and release notes.

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

Strict mode applies every STE rule including both sentence length caps, intended for procedures, runbooks, and safety text. STE-flavored mode keeps the sentence, paragraph, and active-voice discipline but relaxes the roughly 900-word dictionary lockdown so general prose reads naturally.

Can STE rules be applied to code or command syntax?▼

No. The rules apply only to prose such as documentation, comments, and error messages. Code, identifiers, and command syntax are explicitly excluded, as is marketing copy or essays that need a distinct voice.

What are the limitations of automated STE checking?▼

The mechanical rules like sentence length, semicolons, and contractions are lintable, but full STE compliance needs human judgment on correct technical nouns and whether sentences make good sense. The Skill fixes the form of writing but cannot make a hollow paragraph true.