writing-simplified-technical-english

Rewrites prose using ASD-STE100 Simplified Technical English rules for unambiguous technical communication.

713|118|Updated Aug 11, 2020
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill writing-simplified-technical-english
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-simplified-technical-english
Source: https://github.com/PostHog/posthog-foss/tree/main/products/posthog_ai/skills/writing-simplified-technical-english
Command: npx skills add https://github.com/PostHog/posthog-foss --skill writing-simplified-technical-english

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Agent-written and human-drafted prose is often correct but hard to read: long sentences, passive voice, stacked hedges, and rotating synonyms that make one action look like three. This Skill applies the ASD-STE100 controlled-language standard so that reports, PR descriptions, error messages, and instructions cannot be misread by the person or agent acting on them.

Core Features & Use Cases

  • Rule-based rewriting: Applies a concrete rule table covering one meaning per word, active voice, simple tenses, one idea per sentence, sentence length caps, and noun-cluster limits.
  • Structured rewrite workflow: Reads for meaning first, names the broken rule per sentence, rewrites while preserving every fact, number, and condition, then re-checks the result.
  • Worked examples and rule detail: Ships reference files with before/after examples for tool descriptions, error messages, agent instructions, and report findings, plus background on the ASD-STE100 standard.
  • Use Case: You drafted a dense PR description or a vague error message like "An error may have occurred due to a possible mismatch." Ask for an STE rewrite and get short, active, single-idea sentences that name the actor and the fix.

Quick Start

Rewrite this error message in simplified technical English: "An error may have occurred while processing your request due to a possible mismatch in the expected data format."

Frequently Asked Questions about writing-simplified-technical-english

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

FAQPage Schema
How do I rewrite text in Simplified Technical English?

Read the text once for meaning, then go sentence by sentence naming which rule each sentence breaks. Rewrite to fix that break while keeping every fact, number, and condition, then check the result against the rules again since rewrites often introduce new long sentences.

What is ASD-STE100 and what rules does it define?

ASD-STE100 is a controlled natural language standard from the aerospace and defense industry, first shipped in 1986 and now at Issue 9. It defines 53 writing rules across 9 sections plus a dictionary of about 900 approved words, each with one meaning and one part of speech.

When should I not use Simplified Technical English?

Do not use it where voice is the point, such as marketing copy, blog posts, or persuasive writing, since STE is deliberately flat. Also leave quoted text alone: user quotes, logs, and documents stay exactly as written.

Does STE rewriting shorten sentences at the cost of losing information?

No. Precision beats brevity in this approach. If a shorter sentence would drop a safety condition, a scope qualifier, or a number, the longer sentence is kept with a one-line explanation of why.

Does this skill certify documents as ASD-STE100 compliant?

No. It is a clarity tool built on the same rules and does not reproduce the approved dictionary or certify compliance. When exact approved wording matters, download the official standard and check word by word.