simplify-technical-writing

Rewrites prose into ASD-STE100 Simplified Technical English while preserving all source information.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nseng-ai/ns --skill simplify-technical-writing-nseng-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simplify-technical-writing
Source: https://github.com/nseng-ai/ns/tree/main/skills/incubating/writing/simplify-technical-writing
Command: npx skills add https://github.com/nseng-ai/ns --skill simplify-technical-writing-nseng-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Technical documents often use complex sentence structures and inconsistent vocabulary that confuse readers and translators. This Skill rewrites text into ASD-STE100 Simplified Technical English while guaranteeing that no facts, conditions, or qualifiers are lost in the process. ## Core Features & Use Cases - STE Rule Enforcement: Applies active voice, simple tenses, sentence length limits, and one-word-one-meaning vocabulary rules to every sentence. - Fidelity Contract: Preserves every claim, number, condition, modality, rationale, and evidence anchor from the source, with verbatim zones for code, commands, and identifiers. - Deviation Reporting: Appends a deviations list documenting every place where fidelity forced a break from an STE rule. - Use Case: Rewrite a dense engineering design document or README into Simplified Technical English so non-native speakers and translation teams can work with it, without losing any technical detail. ## Quick Start Ask the agent to rewrite the previous response or a specified file into Simplified Technical English using this skill.

Frequently Asked Questions about simplify-technical-writing

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

FAQPage Schema
How do I convert technical documentation to Simplified Technical English?

Invoke the skill with no argument to rewrite the previous response, pass a file path to rewrite that file in place, or paste text directly as the argument. The output follows ASD-STE100 rules for voice, tense, sentence length, and vocabulary.

What is ASD-STE100 Simplified Technical English?

ASD-STE100 is a controlled language specification that restricts vocabulary and grammar to make technical text unambiguous. This skill applies its core rules: active voice, simple tenses, one topic per sentence, and limits of 20 words per instruction and 25 per descriptive sentence.

Does rewriting to STE lose technical details or code?

No. A fidelity contract requires every claim, number, condition, and qualifier to survive the rewrite. Code blocks, commands, identifiers, and quoted material are verbatim zones copied exactly, with STE rules not applied inside them.

What happens when an STE rule conflicts with accuracy?

Fidelity outranks form: the skill keeps the information, breaks the rule, and records the deviation. The output ends with a deviations list documenting each place where preserving meaning forced a rule violation.

Can I use Simplified Technical English rewriting on files in place?

Yes. When the argument is a path to an existing file, the skill reads the full file content and writes the rewrite back to the same path, then reports the path. Document structure such as headings, tables, and links is preserved.