AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

writing-simplified-technical-english

Write English that a reader cannot misread: one meaning per word, active voice, simple tenses, one idea per sentence, short sentences. Based on ASD-STE100 (Simplified Technical English), the controlled-language standard written for aircraft maintenance manuals. Use it for any prose an agent produces that someone else acts on. That covers reports and findings, PR descriptions and commit messages, instructions handed to another agent, tool descriptions, error messages, status summaries, and prompts. Also use it on request, with triggers like "simplify this", "make this readable", "too dense", "rewrite in STE", "simplified technical english", "ASD-STE100".

Original source
posthog
License
MIT
Pinned revision
cac7c80a9e5b73484d18eda1bffb47297c938e0c

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read posthog--writing-simplified-technical-english at revision cac7c80a9e5b73484d18eda1bffb47297c938e0c, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 3

references/writing-rules.md

ASD-STE100 writing rules

This file gives the detail behind the rule table in SKILL.md. It paraphrases the rule categories of the standard. It does not reproduce the text of the standard or its dictionary.

What the standard is

ASD-STE100 is a controlled natural language. European airlines asked for it, because most of their maintenance staff read English as a second language. A misread instruction on an aircraft can kill people. The standard first shipped in 1986. ASD (the AeroSpace and Defense Industries Association of Europe) maintains it through the Simplified Technical English Maintenance Group. It has been free to download since 2013. The current edition is Issue 9, from January 2025.

The standard has two parts:

  • 53 writing rules across 9 sections. They cover word choice, grammar, sentence structure, and style.
  • A dictionary of about 900 approved words. Each word has one meaning and one part of speech. About 1,200 more words are listed as words to avoid, each with a replacement.

An organization may add its own approved technical nouns and verbs on top of the base dictionary. That is how a domain term survives the rules: approve it once, define it once, then use it the same way every time.

Detail behind the rules

Verb forms. Use the infinitive, the imperative, the simple present, the simple past, the simple future, and the past participle as an adjective. Do not use the present perfect, the past perfect, or other compound forms. Use an "-ing" form only inside a technical noun, never as a verb form.

Voice. Use the active voice for procedures and instructions. The passive voice is allowed in descriptive text, and only when the actor is unknown or irrelevant to the reader.

Missing words. Do not drop the verb, the subject, or the article to shorten a sentence. The standard warns that this creates ambiguity rather than clarity. This is the rule that most often surprises a writer who equates short with clear.

Safety instructions. Open a safety-critical instruction with the command or the condition. Do not bury it mid-sentence. The reader must know the risk before they read the detail.

What this skill does not do

  • It does not reproduce the approved dictionary. When exact approved wording matters, download the standard and check word by word.
  • It does not certify a document as STE compliant. It is a clarity tool built on the same rules.

Sources

This skill is adapted from danyuchn/asd-ste100-skill, published under the MIT license.