New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Simple English

by moeru-ai in moeru-ai/airi

Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.

MITAuto-check passedDevelopment

Install Simple English

skills CLI
$ npx skills add moeru-ai/airi --skill simple-english -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install moeru-ai/airi simple-english --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/moeru-ai/airi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/simple-english .claude/skills/simple-english && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
simple-english
GitHub stars
50k
Used in
2 other repos
Token cost
~4.6k tokens
SKILL.md length
2,564 words
Files
3 (incl. references)
Skills in repo
24
Repo updated
First seen
Licence
MIT

At a glance

Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.

  • Works in 6 steps: Select the mode (pragmatic or strict,… → Classify each passage as procedural or… → Fix your vocabulary before drafting.… → …
  • Incident reports
  • SKILL.md covers Your Task, Two Modes, Step 1: Classify the Text and THE RULE CATALOG, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Simple English is an agent skill from moeru-ai/airi. Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. Enforces the standard's 53 rules: 20/25-word sentence limits, one word one…

Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/checklist.md` and `references/use-cases.md`). Compatibility notes: claude-code cursor codex gemini-cli opencode

It sits in Development, covering Technical documentation, Runbooks and postmortems and Changelog and release notes. The repository describes itself as: 💖🧸 Self hosted, you-owned Grok Companion, a container of souls of waifu, cyber livings to bring them into our worlds, wishing to achieve Neuro-sama's altitude. Capable of… The licence is MIT.

When your agent uses it

  • Incident reports
  • The user says STE
  • Simplified Technical English
  • Make this readable

Example prompts

  • “Simplified Technical English”
  • “ASD-STE100”
  • “de-slop”
  • “/simple-english”

Requirements

  • Compatibility (from SKILL.md): claude-code cursor codex gemini-cli opencode

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Select the mode (pragmatic or strict, below).
  2. Classify each passage as procedural or descriptive. Every other rule depends on this.
  3. Fix your vocabulary before drafting. Pick ONE verb for the check/verify/confirm/validate concept and ONE noun for config/settings. Use no…
  4. Apply the rules from the catalog below.
  5. Run the self-check before you deliver. This step is not optional.
  6. Never touch code, identifiers, commands, or quoted errors (see Untouchables).

What it can do on your machine

Read from SKILL.md and the folder at commit ec682e2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    claude-code cursor codex gemini-cli opencode

    From compatibility in the SKILL.md frontmatter.

Context cost

Simple English loads about 4.6k tokens when it runs, and up to ~6.4k if it reads all its reference files. Until then it costs about 149 tokens; SKILL.md has 2,564 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~149
When it runs · the whole SKILL.md, loaded when a task matches
~4.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from moeru-ai/airi at commit ec682e2, republished under its MIT licence (© moeru-ai). 2,564 words, ~4,602 tokens.

Download SKILL.mdSave it as .claude/skills/simple-english/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
simple-english
description
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. Enforces the standard's 53 rules: 20/25-word sentence limits, one word one meaning, simple tenses, active voice, condition before command.
compatibility
claude-code cursor codex gemini-cli opencode
version
1.0.0
license
MIT
metadata.standard
ASD-STE100 Issue 9 (2025-01-15)

Simple English: Write Like an Aerospace Manual

Write technical text with the rules of ASD-STE100 Simplified Technical English. STE is the controlled language that aerospace and defense manufacturers use for maintenance documentation. The rules exist so that a tired reader who is not a native English speaker cannot misread an instruction. They remove the usual signs of AI-generated text as a side effect: long sentences, synonym rotation, hedges, filler, and decorative clauses.

Write for that tired reader. Each sentence must survive one read.

Your Task

When asked to write or rewrite technical text:

  1. Select the mode (pragmatic or strict, below).
  2. Classify each passage as procedural or descriptive. Every other rule depends on this.
  3. Fix your vocabulary before drafting. Pick ONE verb for the check/verify/confirm/validate concept and ONE noun for config/settings. Use no other word for these concepts in the whole document.
  4. Apply the rules from the catalog below.
  5. Run the self-check before you deliver. This step is not optional.
  6. Never touch code, identifiers, commands, or quoted errors (see Untouchables).

When asked to CHECK text instead of writing it, report each violation as: rule number, the offending text, a compliant rewrite. Cite only rule numbers that exist in this file. Do not cite rule numbers from memory: the numbering is unintuitive and models invent it (tested — an agent without this file cited "Rule 3.1: short sentences"; the real Rule 3.1 is about verb forms).

Two Modes

ModeWhenWhat you apply
Pragmatic (default)Docs, READMEs, error messages — the user wants clear textAll structural rules. Domain words stay ("idempotent", "webhook").
StrictThe user names STE, ASD-STE100, or complianceStructural rules + full vocabulary discipline, and tell the user that full compliance needs the official dictionary (free at asd-ste100.org).

Step 1: Classify the Text

Procedural (instructions)Descriptive (explanations)
PurposeTell the reader what to doExplain what a thing is or does
Verb formImperative: "Install the pump."Simple present/past/future
Sentence limit20 words (Rule 5.1)25 words (Rule 6.3)
Unit ruleOne instruction per sentence (5.2)One topic per paragraph (6.5), max six sentences per paragraph (6.6)

Do not mix the two in one passage. A "Getting started" section is procedural. An "Architecture" section is descriptive. A note inside a procedure is descriptive (25-word limit, no imperative).

THE RULE CATALOG

53 rules in 9 sections, paraphrased from ASD-STE100 Issue 9 with software examples. The official wording is in the free standard at asd-ste100.org.

Section 1 — Words (Rules 1.1-1.14)
RuleInstruction
1.1Use only approved words, technical nouns, or technical verbs.
1.2Use an approved word only as its listed part of speech.
1.3Use an approved word only with its approved meaning.
1.4Use only the approved forms of verbs and adjectives.
1.5You can use domain words as technical nouns ("webhook", "commit", "endpoint").
1.6Use an unapproved word only when it is a technical noun or part of one.
1.7Do not use technical nouns as verbs.
1.8Use the technical nouns of your project or industry.
1.9When you pick a technical noun, pick a short and clear one.
1.10No regional, slang, or jargon words as technical nouns.
1.11One item, one name. Do not call it "config" here and "settings" there.
1.12You can use domain verbs as technical verbs ("deploy", "compile", "merge").
1.13Do not use technical verbs as nouns.
1.14Use American English spelling.

In pragmatic mode, rules 1.5, 1.8, and 1.12 do the heavy lifting: your domain vocabulary is legal. The ones agents break are 1.7, 1.11, and 1.13.

Before: You can webhook the event, then do a deploy. After: Send the event to the webhook. Then deploy the service.

Section 2 — Multi-word nouns (Rules 2.1-2.2)
RuleInstruction
2.1Write multi-word nouns of three words or fewer.
2.2When a technical noun needs more than three words, write it in full once, then give a short form or hyphenate the units.

Break long noun chains with prepositions (of, on, in, for):

Before: the connection pool timeout configuration value After: the timeout value for the connection pool

Section 3 — Verbs (Rules 3.1-3.7)
RuleInstruction
3.1Use only the verb forms that the dictionary gives.
3.2Use only: infinitive, imperative, simple present, simple past, simple future, past participle as adjective.
3.3Use the past participle only as an adjective ("the cached response").
3.4No auxiliary verbs for complex constructions. No present perfect, no "is to be installed".
3.5Use an "-ing" form only as a technical noun or inside one ("logging", "the mounting bracket") — never as a verb.
3.6Active voice. In descriptive text, passive is legal only when the agent is unknown.
3.7Describe an action with a verb, not a noun ("compress the file", not "perform compression of the file").

Approved modals: can, will, must. Banned: should, would, may, might, could. The standard rejects "could" even for possibility: write "an explosion can occur", never "could occur". For "should": a requirement becomes "must"; a suggestion is stated as fact or deleted. This matters double for agent instructions — models read "should" as optional.

Before: The migration has completed and the table is being rebuilt. After: The migration is complete. The database rebuilds the table.

Before: The flag can be set in the config file, making restarts unnecessary. After: You can set the flag in the config file. Then a restart is not necessary.

Before: The temperature must be adjusted. After: Adjust the temperature.

Section 4 — Sentences (Rules 4.1-4.5)
RuleInstruction
4.1Write short and clear sentences.
4.2Do not omit words or use contractions to shorten sentences. Keep articles, keep "that".
4.3Use a vertical list for complex text.
4.4Use connecting words between sentences on related topics ("Then", "As a result").
4.5Put an article (the, a, an) or a demonstrative adjective (this, these) before nouns where applicable.

Rule 4.2 is the anti-terseness rule. STE is short sentences with complete grammar, not telegraph style:

Wrong shortening: Ensure file exists before running. STE: Make sure that the file exists before you run the command.

Section 5 — Procedural writing (Rules 5.1-5.5)
RuleInstruction
5.1Maximum 20 words per sentence. Warnings and cautions included.
5.2One instruction per sentence, unless two actions happen at the same time.
5.3Write instructions in the imperative: "Run the migration."
5.4Put a required condition before the command, divided by a comma: "If the build fails, read the log."
5.5Notes give information, never instructions. Notes get the 25-word limit.

Before: You'll want to grab the API key from the dashboard before configuring the client, which you can do under Settings. After: Get the API key from the dashboard, under Settings. Then configure the client with this key.

Section 6 — Descriptive writing (Rules 6.1-6.6)
RuleInstruction
6.1Give information gradually: one new fact per sentence.
6.2Use key words and phrases to give the text a logical structure.
6.3Maximum 25 words per sentence.
6.4Group related information in paragraphs.
6.5One topic per paragraph.
6.6Maximum six sentences per paragraph.

No imperative in descriptive text. Descriptions explain; procedures instruct.

Section 7 — Safety instructions (Rules 7.1-7.3)
RuleInstruction
7.1Use a word that shows the risk level ("WARNING" = injury, "CAUTION" = damage).
7.2Start with a clear command or condition.
7.3Then give the risk or the possible result.

Never bury the instruction after the explanation. The pattern transfers directly to destructive CLI flags, irreversible migrations, and dangerous API options.

Before: Note that data loss may occur in some circumstances if the destructive flag happens to be enabled when running against production. After: CAUTION: Do not use the --force flag against production. The flag deletes rows that do not match the source.

Section 8 — Punctuation and word count (Rules 8.1-8.7)
RuleInstruction
8.1All standard punctuation is legal except the semicolon. Write two sentences instead.
8.2Use hyphens to connect words that act as one unit.
8.3Parentheses are legal for references, item numbers, abbreviations, plural forms, explanations, alternatives.
8.4In a vertical list, the lead-in colon ends a sentence for word count.
8.5Text inside parentheses counts as one word.
8.6Count as one word each: numbers, numbers with units, abbreviations, alphanumeric identifiers, quoted text, titles, labels, proper nouns.
8.7A hyphenated word counts as one word.

Rule 8.6 matters for software text: sqlpipe run --config sqlpipe.yaml in backticks is quoted text and counts as one word. Long identifiers do not blow your sentence budget.

Section 9 — Writing practices (Rules 9.1-9.4, GR-1 to GR-8)
RuleInstruction
9.1When a word-for-word replacement does not work, restructure the sentence.
9.2Use each approved word correctly: approved meaning, approved part of speech.
9.3Do not build phrasal verbs ("go down" → "decrease", "set up" → "install" or "configure").
9.4Keep one consistent style and terminology through the whole document.

General recommendations GR-1 to GR-8: keep the conjunction "that", be careful with "with", give pronouns clear referents, prefer "this + noun" over bare "this", avoid false friends, avoid Latin abbreviations, use inclusive language, and use the possessive apostrophe form only when you are sure it is correct (GR-8: if unsure, do not use it — non-native readers find it hard).

GR-6 for software docs: "e.g." → "for example", "i.e." → "that is", and delete "etc." — name the items or write "and more".

Show full SKILL.md (1,029 more words)Show less

VOCABULARY DISCIPLINE

The official dictionary (~900 approved words, ~1,200 banned words with alternatives) is copyrighted by ASD and is not reproduced here. Its mechanics apply without it: one word, one meaning, one part of speech.

Known part-of-speech rulings, useful as patterns:

WordRuling
test, check, workNoun only. "Do a test", not "test the pump". "Check that X" becomes "make sure that X".
oilNoun only as used in STE examples. For the verb, the dictionary gives "lubricate".
helpVerb only. For the noun, the dictionary gives "aid": "with the aid of".
fall"To move down by gravity" only, never "decrease".
follow"To come after" only, never "obey". Write "obey the instructions".
above, belowPhysical positions only. For limits write "more than", "less than".
The modal ladder
You wroteSTE writes
should (requirement)must
should (recommendation)Delete it, or state it as fact: "X is better because Y."
may / might / could (possibility)can
may (permission)can
would (hypothetical)Restructure: "If X occurs, Y occurs."
Slop-to-simple substitutions

This table is ours, not the ASD dictionary. It maps the words AI-generated docs overuse to plain replacements. If the word carries no fact, delete it instead of replacing it.

SlopWrite instead
leverage, utilizeuse
in order toto
prior tobefore
ensuremake sure that
it is worth noting that(delete)
it's important to, crucially(delete — state the fact)
simply, just, easily, seamlessly, effortlessly(delete)
robust, powerful, comprehensive, performant(delete, or give the measurable property)
functionalityfunction, feature
enables you to, allows you toyou can
is designed to, aims to(delete — say what it does)
facilitatehelp, make possible
dive into, delve intoread, examine
when it comes tofor
in the event thatif
due to the fact thatbecause
as needed, as necessary(state the condition)
and/orPick one, or write "X, or Y, or both"
e.g. / i.e. / etc.for example / that is / (name the items)
gracefully handles(say what it does: "retries three times, then stops")
out of the boxby default
under the hoodinternally
blazingly fast, state-of-the-artfast (give the number) / (delete)
streamlinemake simpler, make faster
plethora, myriadmany
addresses the issue, tacklescorrects the fault, removes the error
Consistency pass

Collapse these common rotations to one term each (Rules 1.11, 9.4):

  • check / verify / confirm / validate / ensure → pick one
  • config / configuration / settings / options → pick one
  • delete / remove / drop / destroy → one per meaning, kept consistent
  • error / issue / problem / failure → "error" for errors, "failure" for failed operations
  • run / execute / invoke / launch → pick one
  • show / display / render / present → pick one

Untouchables

These are technical names (Rules 1.5, 8.6). Leave them exact, even when they break vocabulary rules:

  • Code blocks, inline code, identifiers, CLI commands, flags, file paths
  • Quoted error messages and log lines
  • Product names, API endpoint names, config keys
  • Numbers with units — each counts as one word in the sentence limit

Beyond Documentation

Same rules, different targets. Full adaptations in references/use-cases.md:

  • Error messages: state what happened (simple past), the cause if known, then the fix as an imperative. No "Oops", no "Please ensure", no apology filler.
  • Runbooks: STE's home turf. Imperative steps, conditions first, warnings before the step.
  • Incident reports: simple past only. "We have identified an issue that may have impacted" becomes "Between 14:02 and 14:31 UTC, 12% of requests failed."
  • Release notes: breaking changes follow the warning pattern — command first, risk second.
  • Agent instructions (prompts, AGENTS.md): a system prompt is a procedure for a reader that cannot ask questions. One instruction per sentence, no "should", condition first.
  • Translation prep: STE's original job. One meaning per word plus complete grammar removes most translation ambiguity.

Self-Check Before You Deliver

This step is not optional. Run these four checks on your draft:

  1. Count words in your three longest sentences. Over the 20/25 limit → split them.
  2. Search your draft for: 'll, 're, 's (contraction), has been, have been, should, -ing verbs after a comma, semicolons.
  3. Search for every if and when. Each one stands at the START of its sentence, before the command. "Increase the timeout if the network is slow" → "If the network is slow, increase the timeout."
  4. Search for the verbs you did NOT pick in Your Task step 3 (the check/verify/confirm set). Replace every hit with your chosen verb.

Fix what you find, then deliver. For a full audit, run references/checklist.md.

Full Example

Before (real unedited AI output):

Connection timeouts. If sqlpipe hangs or fails with dial tcp: i/o timeout, check that the host running sqlpipe can reach the Postgres port (usually 5432) — this is often a security group or firewall rule blocking the connection. If you're connecting to a managed database (RDS, Cloud SQL, etc.), confirm the instance allows connections from sqlpipe's IP. You can also try increasing source.connect_timeout_seconds in your config, since a slow network path can trip the default timeout even when the connection eventually succeeds.

After (classified procedural, verb = "make sure", conditions first, one instruction per sentence):

Connection timeouts. sqlpipe stops with dial tcp: i/o timeout when it cannot reach the Postgres port (5432 by default).

  1. Make sure that the host that runs sqlpipe can reach the Postgres port. A firewall or security group usually blocks it.
  2. If the database is managed (RDS, Cloud SQL), make sure that the instance accepts connections from the IP of sqlpipe.
  3. If the network is slow, increase source.connect_timeout_seconds in the configuration.

What changed: 40-word sentences split under 20; "you're" expanded; "check/confirm" collapsed to "make sure that"; every condition moved before its command; "etc." removed; code and error strings untouched.

Limits

STE is for technical facts and instructions. Do not apply it to marketing copy, blog voice, or brand writing — it deletes persuasion by design. When a user asks for STE on marketing text, say so and offer it for the docs instead.

This skill is an unofficial aid. It is not affiliated with or endorsed by ASD or STEMG, and no tool can guarantee STE compliance. ASD-STE100 is a registered trademark of ASD. The official standard is a free download at asd-ste100.org.

References

  • references/checklist.md — full verification pass with searchable patterns, for check mode and final audits
  • references/use-cases.md — long-form adaptations: error messages, runbooks, incident reports, commits, UI copy, i18n

© moeru-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/simple-english of moeru-ai/airi.

  • SKILL.md
  • references/checklist.md
  • references/use-cases.md

Open the folder on GitHubat commit ec682e2

Used in 3 other repositories

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in moeru-ai/airi, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Simple English next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Simple English compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Simple English this skillmoeru-ai/airi50k2 repos~4.6kAutomated safety check: PassMIT
Simple Englishropensci/ckanr1043 repos~2kAutomated safety check: PassMIT
Simple Englishdanielvm-git/bigpowers260—~932Automated safety check: PassMIT
Human Writingkylesnowschwartz/SimpleClaude114—~3.6kAutomated safety check: PassNone
Create Docavibebuilder/claude-prime120—~812Automated safety check: PassMIT
Technical Writercuriositech/some_claude_skills244—~1.4kAutomated safety check: PassMIT

Similar skills

  • Simple English

    ropensci/ckanr

    Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before…

    104 GitHub starsUsed in 3 repos~2k tokens
    DevelopmentAuto-check passed

  • Simple English

    danielvm-git/bigpowers

    Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so the result is clear, unambiguous, and free of AI slop.

    260 GitHub stars~932 tokensUpdated 19 days ago
    DevelopmentAuto-check passed

  • Human Writing

    kylesnowschwartz/SimpleClaude

    MUST be used for any request to draft, write, compose, or reword text another person will read, including 'draft a message', 'draft a reply', 'draft a Slack message', 'write an email', 'draft a PR…

    114 GitHub stars~3.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Create Doc

    avibebuilder/claude-prime

    A skill your agent uses when the user wants to save knowledge as a file so others don't have to rediscover it — "turn this into a doc", "write this up", "document how X works", "we figured this out…

    120 GitHub stars~812 tokensUpdated 4 mo ago
    DevOps & CloudAuto-check passed

  • Technical Writer

    curiositech/some_claude_skills

    Expert technical documentation specialist for developer docs, API references, and runbooks.

    244 GitHub stars~1.4k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed

  • Mole CLI Release Flow

    tw93/Mole

    Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.

    70k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

More from moeru-ai/airi

All 24 skills in this repo

  • Enforce Rules For I18n

    moeru-ai/airi

    Review pending AIRI translations on Crowdin in a batch, then sync them into the repository.

    50k GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Upload GitHub Attachment

    moeru-ai/airi

    Upload a local image or file to GitHub's user-attachments storage and return a URL suitable for issue, pull request, discussion, or comment Markdown.

    50k GitHub stars~554 tokensUpdated today
    Auto-check passed

  • Create PR

    moeru-ai/airi

    Prepare and create an AIRI pull request with verifiable change context, architecture evidence, and required visual evidence.

    50k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Use Agent Browser For Airi

    moeru-ai/airi

    Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts.

    50k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Browser Electron

    moeru-ai/airi

    A skill your agent uses when Codex needs to inspect, debug, or automate an Electron app through agent-browser and Chrome DevTools Protocol, especially when the app has multiple BrowserWindow…

    50k GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • Analyze Io Traces

    moeru-ai/airi

    Read and analyze AIRI IO traces that Tamagotchi saved to local files.

    50k GitHub stars~542 tokensUpdated today
    Auto-check passed

Categories

Questions about Simple English

What does Simple English do?

Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop. Simple English is an agent skill from moeru-ai/airi. Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.

When should I use Simple English?

Simple English fits situations like: incident reports; the user says STE; simplified Technical English; make this readable.

How do I install Simple English in Claude Code?

Run `npx skills add moeru-ai/airi --skill simple-english -a claude-code`. Or copy the skill folder (.agents/skills/simple-english in moeru-ai/airi) into .claude/skills/simple-english in your project. Claude Code loads it when a task matches its description.

How do I install Simple English in Codex?

Run `npx skills add moeru-ai/airi --skill simple-english -a codex`. Or copy the skill folder (.agents/skills/simple-english in moeru-ai/airi) into .agents/skills/simple-english in your project. Codex loads it when a task matches its description.

Can I use Simple English in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add moeru-ai/airi --skill simple-english -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/simple-english, .gemini/skills/simple-english, .github/skills/simple-english and .opencode/skills/simple-english in your project.

What does Simple English need to run?

SKILL.md names no scripts, command-line tools or credentials: Simple English is instructions for the agent only. Compatibility (from SKILL.md): claude-code cursor codex gemini-cli opencode.

Does Simple English access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Simple English safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Simple English use?

Simple English is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Simple English use?

About 4.6k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.

What are the alternatives to Simple English?

Skills that share tags, products or a category with Simple English: Simple English (ropensci/ckanr, 104 stars), Simple English (danielvm-git/bigpowers, 260 stars), Human Writing (kylesnowschwartz/SimpleClaude, 114 stars) and Create Doc (avibebuilder/claude-prime, 120 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Simple English?

moeru-ai (a GitHub organization) maintains it in moeru-ai/airi, which has 50,267 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 11, 2026.

Source: moeru-ai/airi on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.