asd-ste100

Write, rewrite, and check technical text against ASD-STE100 Simplified Technical English rules.

24|5|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/nuelcyoung/asd-ste100 --skill asd-ste100-nuelcyoung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asd-ste100
Source: https://github.com/nuelcyoung/asd-ste100
Command: npx skills add https://github.com/nuelcyoung/asd-ste100 --skill asd-ste100-nuelcyoung

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Technical documentation for aerospace, defense, and other regulated industries must follow ASD-STE100 Simplified Technical English, a controlled language with 53 writing rules and a controlled dictionary of about 900 approved words. Manual compliance checking is slow and error-prone, especially for part-of-speech violations and meaning drift during rewrites. ## Core Features & Use Cases - STE Writing and Rewriting: Converts existing manuals, procedures, and warnings into STE-compliant text while preserving technical meaning through a five-pass fidelity check. - Compliance Review: Checks text against the 9 rule sections, 20/25-word sentence limits, verb-form restrictions, and dictionary rulings with part-of-speech tagging, reporting each violation with a compliant rewrite. - Dictionary Verification: Guides lookup against the official Part 2 dictionary (user's PDF, web confirmation, or built-in fallback rulings) with a mandatory disclaimer when the official source is unavailable. - Use Case: A technical writer receives a maintenance procedure draft and asks for an STE compliance check; the skill classifies each passage as procedural or descriptive, tags every content word's part of speech, flags violations like "check" used as a verb, and delivers corrected text with a terminology table. ## Quick Start Ask the assistant to rewrite the attached maintenance procedure into ASD-STE100 Simplified Technical English and report any words that could not be verified against the official dictionary.

Frequently Asked Questions about asd-ste100

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

FAQPage Schema
How do I rewrite technical documentation into ASD-STE100 Simplified Technical English?

Classify each passage as procedural or descriptive, split sentences to the 20/25-word limits, convert to approved verb forms, then verify every content word against the Part 2 dictionary with its part of speech. The skill runs a proposition inventory first so no technical fact is changed during rewriting.

How do I check text for STE compliance?

Provide the text and ask for an STE compliance review. The skill tags each content word's part of speech in context, checks it against dictionary rulings, applies the 53 writing rules, and reports each violation with the rule broken, the offending text, and a compliant rewrite.

Why does a word in the STE dictionary still fail a compliance check?

The dictionary approves each word for one part of speech and one meaning only. For example, "check" is approved as a noun, so "Check the valve" is a violation while "do a check of the valve" is correct. Past participles also inherit their base verb's ruling, so "the required parts" fails because "require" is not an approved verb.

Can this skill verify words against the official ASD-STE100 dictionary?

Yes, if you provide your own official PDF copy (free from asd-ste100.org), the skill reads Part 2 directly for authoritative rulings. Without it, the skill falls back to known rulings and high-risk word tables, and states clearly that full compliance requires verification against the official standard.

What are the limitations of automated STE checking?

No tool can guarantee STE compliance, and ASD/STEMG do not endorse any checking tools. The skill is an unofficial study and writing aid; final approval always rests with the human writer, and the full controlled dictionary is copyrighted and not reproduced.