ASD-STE100 Skill

Install

npx skillfoxx add skills/asd-ste100-skill

npx skills add danyuchn/asd-ste100-skill --skill asd-ste100 -a claude-code -y

npx skills add danyuchn/asd-ste100-skill --skill asd-ste100 -a cursor -y

npx skills add danyuchn/asd-ste100-skill --skill asd-ste100 -a github-copilot -y

npx skills add danyuchn/asd-ste100-skill --skill asd-ste100 -a codex -y

npx skills add danyuchn/asd-ste100-skill --skill asd-ste100 -a gemini-cli -y

npx skills add danyuchn/asd-ste100-skill --skill asd-ste100 -a cline -y

npx skills add danyuchn/asd-ste100-skill --skill asd-ste100 -a roo -y

npx skills add danyuchn/asd-ste100-skill --skill asd-ste100 -a opencode -y

git clone https://github.com/danyuchn/asd-ste100-skill.git
cp -r asd-ste100-skill ~/.claude/skills/asd-ste100

This is third-party code. Review the repository files before installing.

What it does

The skill takes ASD-STE100, the controlled-language standard the aerospace and defense industry built so maintenance instructions cannot be read two ways, and applies it to a different reader: an agent parsing another agent's output, a tool description, an error message or an inter-agent instruction with no human to resolve ambiguity. It picks a mode: strict for procedures, error messages and tool descriptions, STE-flavored for READMEs and explanatory prose. It then reviews the text sentence by sentence, flags rule violations such as passive voice with an unclear actor, complex tenses, several instructions in one sentence and oversized noun clusters, and rewrites the sentences without dropping facts or conditions. On request it shows a before and after table naming each broken rule. A deterministic Python linter ships with it and checks structural patterns like semicolons, phrasal verbs and over-long sentences.

Who it is for. For engineers and technical writers who author tool descriptions, system prompts and error messages that agents or pipelines parse without a human.

Example request

Rewrite this tool description so an agent cannot read it two ways and show which rules were broken

Limitations

The skill does not reproduce ASD's roughly 900-word official dictionary: the standard is free to obtain but not free to redistribute. So the lexical rules are applied as a direction of travel rather than a checkable standard, and the skill says so in its output. The linter checks structural patterns only and does not compare the original with the rewrite or prove that meaning was preserved. Certified standard-compliant documentation needs the real standard with a word-by-word check against the dictionary.

How to disable. Remove the asd-ste100 folder from the agent's skills directory, for example ~/.claude/skills/.

Security check

• The skill is instructions and rule references
• The Python linter runs locally and reads only the file passed to it, with no network access

README in short

The README explains why aerospace Simplified Technical English rules fit agents: a model parsing another agent's output has no back-channel to clarify meaning, just like a mechanic with an instruction. The skill runs in two modes and splits the rules into structural ones it applies with confidence and lexical ones it offers as a direction because ASD's dictionary is not free to redistribute. It ships before and after examples, a rule summary with citations and a Python linter that checks structural patterns and deliberately leaves hedges and modality alone. MIT licensed.

SKILL.md

---
name: asd-ste100
description: "Use when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and misreading has a real cost, or when text reads as dense, hedged, or easy to misparse. Triggers: disambiguate, STE100 rewrite, apply Simplified Technical English, plain-language rewrite, controlled-language rewrite, rewrite so an agent cannot misread this. Not for creative or marketing copy."
version: 0.4.0
---

# Simplified Technical English (ASD-STE100)

ASD-STE100 is a controlled-language standard built by the aerospace and defense industry (ASD, the AeroSpace and Defense Industries Association of Europe) to stop maintenance technicians from misreading English instructions. The standard removes the two biggest sources of misreading: words with more than one meaning, and sentences with more than one possible structure.

This skill borrows that same discipline for a different reader: an **AI agent or a downstream system** that has to parse an English string — an error message, a tool description, an inter-agent instruction, a status report — without a human in the loop to resolve ambiguity.

## When to Use This Skill

- An agent's output (explanation, instruction, log message, tool description) reads as dense, jargon-heavy, or ambiguous.
- Text will be consumed by another agent, a translation pipeline, or a non-native English reader, and misparsing has a real cost.
- You are writing a prompt, system message, or tool description and want to remove ambiguity before a model ever sees it.
- You want a **before/after** comparison showing exactly which rule was violated and how the rewrite fixes it.

Related