style-ste-writing

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

1.1k|206|Updated Mar 16, 2016
One-click install
npx skills add https://github.com/z88dk/z88dk --skill style-ste-writing-z88dk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: style-ste-writing
Source: https://github.com/z88dk/z88dk/tree/main/.agents/skills/style-ste-writing
Command: npx skills add https://github.com/z88dk/z88dk --skill style-ste-writing-z88dk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated prose often contains vague wording, passive voice, long sentences, and marketing filler. This Skill rewrites documentation, READMEs, PR descriptions, error messages, and release notes into ASD-STE100 Simplified Technical English, removing that slop while keeping the technical meaning intact. ## Core Features & Use Cases - Rule-based rewriting: Applies concrete STE rules covering word choice, active voice, sentence length caps (20 words for instructions, 25 for descriptions), punctuation, and paragraph structure. - Two modes: Strict mode for procedures, runbooks, safety text, and error messages; STE-flavored mode for general prose like READMEs and PR descriptions that needs more vocabulary range. - Built-in self-lint: A six-point checklist (sentence length, semicolons, contractions, passive voice, nominalizations, inconsistent naming) runs before text is returned. - Use Case: Paste a wordy README section and ask for an STE-flavored rewrite; the output uses short declarative sentences, one name per thing, and no marketing adjectives. ## Quick Start Rewrite the following README paragraph in STE-flavored Simplified Technical English, keeping all technical facts unchanged.

Frequently Asked Questions about style-ste-writing

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

FAQPage Schema
How do I rewrite documentation in Simplified Technical English?

Provide the prose and request an STE rewrite. The Skill applies ASD-STE100 rules: active voice, short common words, one name per thing, sentences under 20-25 words, no contractions or semicolons, and one topic per paragraph.

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

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

Can STE rewriting be applied to code or command syntax?

No. The Skill explicitly excludes code, identifiers, and command syntax. It only rewrites prose such as documentation, READMEs, PR descriptions, error messages, release notes, and comments.

Does Simplified Technical English work for marketing copy?

No. STE strips voice on purpose, so it is unsuitable for marketing copy, essays, or any text that needs a distinctive voice. It targets technical and procedural prose where clarity matters more than style.

What are the limitations of automated STE checking?

The mechanical rules (length, punctuation, voice) are lintable, but full STE compliance needs human judgment on correct technical nouns and whether a sentence makes sense. The Skill fixes the form of the text, not its factual substance.