agentleFS
jsathjsath/simplified-technical-english/skills/technical-english/SKILL.md

technical-english

Skill66 starsChanged 3 months agoMITView on GitHub

Rewrite or audit any text using the principles of ASD-STE100 Simplified Technical English, the aerospace writing standard built for flight manuals. Kills AI slop by force - short sentences, one approved meaning per word, active voice, no filler. Use when asked to "simplify this", "de-slop this", "make this clearer", "rewrite in plain English", "apply STE", or when documentation, instructions, README files, or AI-generated text need to be readable by every English speaker, including non-native ones.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. autowarefoundation/autoware-harness★ 4same name
    2. andrewjohnharvey/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every word keeps its most common meaning and its most common part of speech.

    line 26
  2. Distinctive:

    If a word can be read two ways in context, replace it.

    line 28
  3. Distinctive:

    Write what is, not what will be or would be.

    line 49
  4. Distinctive:

    Do not drop "the", "a", "an" to save words.

    line 54
  5. Distinctive:

    Delete on sight, they carry no information: *delve, crucial, comprehensive, seamless, robust, cutting-edge, game-changer, landscape, realm, …

    line 90
  6. Distinctive:

    Read the whole text first.

    line 99
  7. Distinctive:

    Verify: recount sentence lengths, rescan for blocklist words and passive instructions.

    line 105
  8. Distinctive:

    Audit mode: When asked to audit (not rewrite), output only the violation report: rule number, quoted offending text, suggested fix, one …

    line 110

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Technical English (STE-inspired)

Aircraft maintenance manuals cannot afford ambiguity. A mechanic who misreads one sentence can kill people. So the aerospace industry built ASD-STE100 Simplified Technical English: a controlled language where every word has one meaning, every sentence has a length limit, and every instruction is a command.

AI-generated text fails in the exact opposite way: long sentences, hedged claims, five-syllable words doing two-syllable jobs, and filler that sounds like content. Applying STE principles to it is a mechanical de-slop pass.

This skill applies those principles. It is inspired by ASD-STE100 and is not the official specification (see the attribution note at the end).

The rules

Apply all of them. When two rules conflict, clarity wins.

1. One word, one meaning

Every word keeps its most common meaning and its most common part of speech. "Follow" means "come after", never "obey". "Check" is a verb, not a noun. If a word can be read two ways in context, replace it.

2. Sentence limits (count, do not guess)

  • Instructions: 20 words maximum.
  • Descriptions: 25 words maximum.
  • Paragraphs: 6 sentences maximum, one topic each. Count the words of every sentence you output. A 21-word instruction is a violation, not a style choice.

3. One instruction per sentence

"Remove the cover and disconnect the cable and check the seal" is three instructions. Write three sentences. Sequences become numbered lists.

4. Active voice, imperative instructions

  • Instruction: "Remove the bolt." Never "The bolt should be removed."
  • Description: name the agent. "The pump moves the fuel", not "the fuel is moved." Passive voice is permitted only when the agent is truly unknown or irrelevant, and never in an instruction.

5. Present tense

Write what is, not what will be or would be. "The valve opens when pressure reaches 30 psi." Use past or future only when the fact itself is past or future.

6. Keep the articles

Do not drop "the", "a", "an" to save words. "Close valve" reads like a telegram; "Close the valve" reads like an instruction.

7. Break noun clusters

More than three nouns in a row is a wall. "Main gearbox oil pressure warning light" becomes "the warning light for the oil pressure of the main gearbox."

8. Warnings come first

Command first, then the condition: "Do not open the cover before you disconnect the power." Never bury the danger at the end of the sentence.

9. The substitution table

Replace unapproved words with their plain equivalents:

Never writeWrite
utilize, leverageuse
commence, initiatestart
terminatestop
accomplish, perform, executedo
sufficientenough
demonstrate, indicateshow
ensuremake sure
facilitatehelp
prior tobefore
subsequent toafter
in order toto
additionally, furthermore, moreoveralso
approximatelyabout
numerousmany
obtainget
requireneed
attempttry
modificationchange

10. The AI-slop blocklist

Delete on sight, they carry no information: delve, crucial, comprehensive, seamless, robust, cutting-edge, game-changer, landscape, realm, tapestry, unlock, elevate, foster, streamline, "it's important to note", "it's worth mentioning", "in today's world", "at the end of the day". Also delete every em dash; use a comma, a colon, or a full stop.

How to run

Rewrite mode (default). Take the input text and:

  1. Read the whole text first. Identify its purpose: instruction, description, or mixed.
  2. List the violations you found (rule number + the offending words). Keep this list short and specific.
  3. Rewrite the full text under the rules above. Preserve every fact. Never add a fact, a number, or a claim that the input does not contain.
  4. Verify: recount sentence lengths, rescan for blocklist words and passive instructions. Fix what you find.
  5. Output the rewrite first, then the violation list under a ## What changed heading.

Audit mode. When asked to audit (not rewrite), output only the violation report: rule number, quoted offending text, suggested fix, one line each.

Light mode. For marketing copy, posts, or anything with a voice worth keeping, apply only rules 2, 4, 9, and 10, and say you did. Full STE strips personality by design; do not apply it to text that needs one unless asked.

What this skill refuses to do

  • It does not shorten by deleting facts. If the input is 40 facts, the output is 40 facts in shorter sentences.
  • It does not simplify quoted text, code, commands, or error messages. Those are exact strings; leave them exact.
  • It does not guess a missing fact to complete a sentence. It marks the gap: "[value missing]".

Example

Before (typical AI output, 44-word sentence):

In order to facilitate the seamless integration of the authentication module, it is important to note that developers should ensure that the configuration file has been comprehensively updated prior to commencing the deployment process, which can be accomplished via the CLI.

After (STE principles, longest sentence 11 words):

Update the configuration file before you start the deployment. Use the CLI to deploy. This connects the authentication module.

Same facts. A third of the words. No ambiguity.


Attribution: Inspired by ASD-STE100 Simplified Technical English, a specification maintained by the AeroSpace and Defence Industries Association of Europe. This skill applies its principles and is not the official specification or its dictionary. The official specification is available free from asd-ste100.org.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.