simple-english

Rewrite technical text to comply with ASD-STE100 Simplified Technical English rules.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/loteiron/ZeusAgent --skill simple-english-loteiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: simple-english
Source: https://github.com/loteiron/ZeusAgent/tree/main/optional-skills/creative/simple-english
Command: npx skills add https://github.com/loteiron/ZeusAgent --skill simple-english-loteiron

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Technical documentation, error messages, and runbooks often contain long sentences, inconsistent terminology, hedging modals, and AI-style filler that confuse readers—especially non-native English speakers and on-call operators. This Skill rewrites or audits text against the 53 rules of ASD-STE100 Simplified Technical English so every sentence survives a single read. ## Core Features & Use Cases - STE Rewriting: Applies the full rule catalog (sentence limits, imperative procedures, condition-first commands, approved modals) to docs, READMEs, runbooks, and error messages in pragmatic or strict mode. - Compliance Auditing: Check mode reports each violation as rule number, offending text, and compliant rewrite, backed by a searchable verification checklist. - Vocabulary Discipline: Collapses synonym rotation (check/verify/confirm, config/settings) to one term per concept and replaces AI-slop words with plain alternatives. - Use Case: Paste a confusing troubleshooting section from your README and receive a rewritten version with 20-word sentences, conditions before commands, and consistent terminology—code blocks and error strings untouched. ## Quick Start Rewrite the troubleshooting section of my README.md using Simplified Technical English rules.

Frequently Asked Questions about simple-english

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

FAQPage Schema
How do I rewrite documentation to ASD-STE100 Simplified Technical English?▼

Provide your text inline or point to a file, and the Skill classifies each passage as procedural or descriptive, then applies the STE rule catalog. Procedural text gets imperative sentences under 20 words; descriptive text gets 25-word limits with one topic per paragraph.

What is the difference between simple-english and humanizer skills?▼

Simple-english enforces the ASD-STE100 controlled language for technical instructions like docs, runbooks, and error messages. Humanizer restores natural human voice for blog posts and essays. Do not apply both to the same text.

Can I audit text for STE compliance without rewriting it?▼

Yes, check mode reports each violation as rule number, offending text, and a compliant rewrite using the verification checklist. It searches for contractions, banned modals, semicolons, trailing conditions, and sentences over the word limits.

Does STE rewriting change code blocks or error messages?▼

No. Code blocks, inline code, identifiers, CLI commands, file paths, quoted error messages, product names, and config keys are untouchable technical names. They remain exact even when they break vocabulary rules.

When should I not use Simplified Technical English?▼

Do not apply STE to marketing copy, blog voice, or brand writing—it deletes persuasion by design. STE targets technical facts and instructions where a misread instruction has real cost, such as maintenance procedures and on-call runbooks.

What is the difference between pragmatic and strict STE mode?▼

Pragmatic mode (default) applies structural rules while keeping domain vocabulary like "webhook" or "idempotent". Strict mode adds full vocabulary discipline with approved dictionary words, and notes that full compliance requires the official ASD-STE100 dictionary.