skills.rest
nabitllc
nabitllcOFFICIAL
Explore all skills by this author →
GitHub

simplified-english

Write user-facing documents in ASD-STE100 Simplified Technical English with approved vocabulary.

Updated Mar 26, 2026
Search Tags:#documentation#technical writing#style guide#clarity#controlled vocabulary#asd-ste100#simplified english
One-click install
npx skills add https://github.com/nabitllc/todero --skill simplified-english-nabitllc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: simplified-english
Source: https://github.com/nabitllc/todero/tree/main/packages/skills-catalog/catalog/optional/content/simplified-english
Command: npx skills add https://github.com/nabitllc/todero --skill simplified-english-nabitllc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Technical writing often uses jargon, long sentences, and ambiguous words that confuse readers. This Skill enforces ASD-STE100 Simplified Technical English rules so user-facing comments, plans, and documents are understood correctly the first time. ## Core Features & Use Cases - Controlled Vocabulary: Uses only approved ASD-STE100 words with one meaning each, plus house-preferred choices like "start" instead of "initiate" and "use" instead of "utilize". - Sentence Structure Rules: Enforces short sentences (procedures ≤ 20 words, descriptions ≤ 25 words), one instruction per sentence, active voice, and present tense. - Use Case: When drafting a product release plan or user-facing comment, apply this Skill to rewrite dense paragraphs into clear, unambiguous instructions that engineers, product managers, and end users all interpret identically. ## Quick Start Rewrite this project plan using Simplified Technical English with short sentences and approved words only.

Frequently Asked Questions about simplified-english

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

FAQPage Schema
How do I write documentation in Simplified Technical English?▼

Use short sentences (procedures under 20 words, descriptions under 25 words), one instruction per sentence, active voice, and present tense. Use only approved ASD-STE100 words with one meaning each, preferring simple choices like "start", "make", and "use".

What is ASD-STE100 Simplified Technical English?▼

ASD-STE100 is a controlled language specification with an approved dictionary where each word has exactly one meaning. It restricts sentence length and grammar so technical documents are unambiguous for all readers, including non-native speakers.

Which words should I avoid in technical writing?▼

Avoid synonyms and jargon such as "initiate", "commence", "terminate", "implement", "leverage", "utilize", "prior to", and "facilitate". Replace them with approved single-meaning words like "start", "stop", "make", "use", "before", and "help".

When should I not use Simplified Technical English?▼

STE is designed for user-facing comments, plans, and procedural documents. It is less suitable for marketing copy, narrative content, or creative writing where varied vocabulary and longer expressive sentences are appropriate.

Does Simplified Technical English work for non-native English readers?▼

Yes, STE was designed for international audiences. Its controlled vocabulary, short sentences, and single-meaning words reduce misinterpretation for readers whose first language is not English.

Related Skills

Explore More Content & Communication Skills→
jolequesjoleques

documentador-rag

Convert unstructured inputs into RAG-ready Markdown documents with YAML metadata.

Community
Intermediate
ShiroiKuma0ShiroiKuma0
25

changelog

Update CHANGELOG.md with categorized user-facing release notes.

Community
Advanced
OpenAnalystIncOpenAnalystInc
6

Content Editor

Review marketing content for grammar, style, brand voice, and readability.

Official
Advanced
humanizeraihumanizerai
39

readability

Compute Flesch-Kincaid, Gunning Fog, and SMOG readability scores with text statistics.

Official
Intermediate