simple-english

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

239k|48.8k|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/NousResearch/hermes-agent --skill simple-english
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simple-english
Source: https://github.com/NousResearch/hermes-agent/tree/main/optional-skills/creative/simple-english
Command: npx skills add https://github.com/NousResearch/hermes-agent --skill simple-english

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

AI-generated technical documentation tends to be verbose, full of filler, and uses synonym rotation that confuses non-native English readers and obscures instructions. This Skill enforces the ASD-STE100 controlled language standard so that maintenance docs, runbooks, and error messages read clearly on the first pass.

Core Features & Use Cases

  • Two operating modes: pragmatic for general docs and READMEs, strict for full ASD-STE100 compliance audits.
  • 53-rule catalog: paraphrases the official standard across vocabulary, verbs, sentence length, procedural vs descriptive writing, safety instructions, and punctuation.
  • Anti-AI-slop substitutions: maps filler words like "leverage", "seamlessly", and "robust" to plain replacements or deletion.
  • Use Case: Rewrite a README section so that every procedural sentence stays under 20 words, conditions appear before commands, and one term is used consistently for each concept.

Quick Start

Rewrite the attached README section using the simple-english skill in pragmatic mode.

Frequently Asked Questions about simple-english

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

FAQPage Schema
How do I rewrite technical documentation in Simplified Technical English?

Classify each passage as procedural or descriptive, then apply the STE rules: 20-word limit for procedures, 25-word limit for descriptions, imperative voice for instructions, and one term per concept. Run the self-check for contractions, banned modals, and trailing conditions before delivering.

What is the difference between pragmatic and strict STE mode?

Pragmatic mode applies structural rules while allowing domain technical nouns like webhook or commit. Strict mode adds full vocabulary discipline, requires make sure that for verification, and tells the user that full compliance needs the official ASD dictionary.

Can STE rules be applied to error messages and CLI output?

Yes. Error messages follow the procedural pattern: state what happened in simple past, give the cause if known, then provide the fix as an imperative. Remove filler like Oops, Please ensure, and apology phrases.

Why does STE ban the word should in technical instructions?

Should is not an approved modal under Rule 3.2. For requirements, write must. For recommendations, delete the word or state the fact directly. This matters for agent instructions because language models read should as optional.

When should STE not be applied to a document?

STE is designed for technical facts and instructions. Do not apply it to marketing copy, blog posts, brand writing, or persuasive content because the standard deletes persuasion by design. Use a human voice skill for those instead.