Agent skill

Simplified Technical English

by NeverSight in NeverSight/learn-skills.dev

Writes and rewrites text in Simplified Technical English (ASD-STE100), a controlled language for clear technical documentation.

MITAuto-check passedWriting & Content

Install Simplified Technical English

skills CLI
$ npx skills add NeverSight/learn-skills.dev --skill simplified-technical-english -a claude-code

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

GitHub CLI
$ gh skill install NeverSight/learn-skills.dev simplified-technical-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/NeverSight/learn-skills.dev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/data/skills-md/0xpili/simplified-technical-english/simplified-technical-english .claude/skills/simplified-technical-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
simplified-technical-english
GitHub stars
216
Used in
1 other repo
Token cost
~1.7k tokens
SKILL.md length
972 words
Files
13
Skills in repo
42
Repo updated
First seen
Licence
MIT

At a glance

Writes and rewrites text in Simplified Technical English (ASD-STE100), a controlled language for clear technical documentation.

  • Works in 6 steps: Classify the text → Obey the verb rules → Obey the sentence rules → …
  • The user asks for STE
  • SKILL.md covers Scope, Step 1: Classify the text, Step 2: Obey the verb rules and Step 3: Obey the sentence rules, plus 5 more sections
  • Calls python3

What it does

Simplified Technical English is an agent skill from NeverSight/learn-skills.dev. Writes and rewrites text in Simplified Technical English (ASD-STE100), a controlled language for clear technical documentation. Use when the user asks for STE, Simplified Technical English, controlled language, or plain technical writing, and when the user asks to write, rewrite, review, or check technical documentation, procedures, manuals, instructions, warnings, or reports.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files (for example `stats.json`).

It sits in Writing & Content, covering Technical documentation and Technical writing. The repository describes itself as: Curated high-quality AI Agent Skills. Search, install, copy and share. Works with Claude Code, Cursor, OpenClaw, and other AI coding tools. The licence is MIT.

When your agent uses it

  • The user asks for STE
  • Simplified Technical English
  • Controlled language
  • Plain technical writing

Example prompts

  • “Use the simplified-technical-english skill to write and rewrites text in Simplified Technical English (ASD-STE100), a controlled language for clear…”
  • “/simplified-technical-english”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Classify the text
  2. Obey the verb rules
  3. Obey the sentence rules
  4. Obey the word rules
  5. Write safety instructions correctly
  6. Check your text

What it can do on your machine

Read from SKILL.md and the folder at commit 50f7fc9. 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

    Shell commands in SKILL.md call:

    • python3

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

  • Network

    Links to these hosts (documentation or services it may open):

    • asd-ste100.org

    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.

Context cost

Simplified Technical English loads about 1.7k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 972 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

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 NeverSight/learn-skills.dev at commit 50f7fc9, republished under its MIT licence (© NeverSight). 972 words, ~1,725 tokens.

Download SKILL.mdSave it as .claude/skills/simplified-technical-english/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
simplified-technical-english
description
Writes and rewrites text in Simplified Technical English (ASD-STE100), a controlled language for clear technical documentation. Use when the user asks for STE, Simplified Technical English, controlled language, or plain technical writing, and when the user asks to write, rewrite, review, or check technical documentation, procedures, manuals, instructions, warnings, or reports.
license
MIT for the text of this skill. The word list in references/word-list.md comes from the ASD-STE100 dictionary, which is the property of ASD. Refer to NOTICE.md.
metadata.source-specification
ASD-STE100 Issue 7 (2017-01-25)

Simplified Technical English

This skill makes you write in Simplified Technical English (STE). STE is a controlled language for technical documentation. The specification ASD-STE100 gives 53 writing rules and a dictionary of approved words. Text in STE is clear to readers who do not know much English.

Obey the rules in this file for all the technical text that you write. The rules in this file are the most important rules. The full set of rules is in references/writing-rules.md. The approved words are in references/word-list.md.

Scope

Apply STE to technical output: documentation, procedures, manuals, instructions, reports, error messages, and answers about technical subjects.

Do not apply STE to:

  • Marketing text or brand text
  • Poems, stories, or conversation
  • Code blocks, identifiers, commands, file paths, and quoted error messages
  • Quoted text and official names of products, parts, and documents.

If the user asks for a different style, the request of the user wins.

Step 1: Classify the text

Before you write, classify each part of the text:

  • Procedural text tells the reader to do something. Example: "Remove the four bolts."
  • Descriptive text gives information. Example: "The pump supplies fuel to the engine."

The two types have different limits. Do not mix the two types in one paragraph.

Step 2: Obey the verb rules

  • Use only these verb forms: infinitive, imperative, simple present, simple past, future with "will", and past participle as an adjective.
  • Do not use the "-ing" form of a verb. Approved "-ing" words are only: mating, missing, remaining, lighting, opening, routing, servicing, during.
  • Do not use a helping verb with a past participle. Write "the operator adjusted the linkage", not "the operator has adjusted the linkage".
  • Use the active voice. Write "a relay connects the circuits", not "the circuits are connected by a relay".
  • In procedures, use the imperative. Write "Set the switch to ON."
  • If there is no agent, use "you" or "we" as the subject.
  • Use only "can", "must", and "will" as helping verbs. Do not use "should", "would", "may", "might", or "shall".
  • A past participle after "is" or "are" shows a condition and is permitted. "The wires are disconnected."

Step 3: Obey the sentence rules

  • Procedural sentences: maximum 20 words.
  • Descriptive sentences: maximum 25 words.
  • Paragraphs: maximum 6 sentences, and only one topic.
  • Write only one instruction in each sentence. Two actions are permitted only when they occur at the same time.
  • Write only one topic in each sentence.
  • When a condition comes before a command, put a comma after the condition. "If the light comes on, stop the engine."
  • Keep the articles, the subjects, the verbs, and the conjunction "that". Write "make sure that the file exists".
  • Do not use contractions. Write "do not", not "don't".
  • Do not use semicolons. Write two sentences.
  • Use a vertical list for complex text. In a list of commands with "not", write "not" again in each item.

Step 4: Obey the word rules

  • Use only: approved words from references/word-list.md, technical names, and technical verbs.
  • A technical name is the official name of a part, tool, material, system, document, or term of your subject. Examples: "engine", "firewall", "torque wrench", "SKILL.md".
  • Use an approved word only as its given part of speech. "Test" is a noun, not a verb. Write "do a test", not "test the system".
  • Use one name for one item in the full text. Do not change between names for the same item.
  • Write noun clusters of maximum three words. Break long clusters with "of", "on", "in", or "for".
  • Do not make phrasal verbs. Write "extinguish the fire", not "put out the fire".
  • Do not use vague words. Write the specific quantity, name, or action.
  • Use American English spelling.
  • Common replacements are in references/substitutions.md.
Show full SKILL.md (357 more words)Show less

Step 5: Write safety instructions correctly

  • Use "WARNING" for a risk of injury or death to persons.
  • Use "CAUTION" for a risk of damage to objects.
  • Start with a simple command or condition. Then give the risk.
  • Example: "WARNING: Do not touch the connector. The connector can have a dangerous voltage."

Step 6: Check your text

After you write, check your text. Do these steps:

  1. If you can run scripts, run: python3 scripts/ste_check.py --mode <procedural|descriptive> <file>.
  2. If you cannot run scripts, do a manual scan of the checklist below.
  3. Correct each error.
  4. Check the text again. Stop only when the text has no errors.

Manual scan checklist:

  • Find semicolons and contractions. Remove them.
  • Find "has", "have", and "had" before a past participle. Use the simple past tense.
  • Find "should", "would", "may", "might", and "shall". Replace them or remove them.
  • Find "-ing" words that are not approved and are not in technical names. Rewrite them.
  • Find passive voice. Make the agent the subject, or use the imperative.
  • Count the words in the longest sentences. Divide sentences that are too long.
  • Count the sentences in each paragraph. Divide paragraphs that have more than 6 sentences.
  • Find words that are not approved and are not technical names. Replace them.

The check tool cannot find all the errors. The tool cannot know if a word has its approved meaning. You must also compare your words with references/word-list.md.

Reference files

  • references/writing-rules.md — all 53 rules and 4 recommendations, with examples. Read this file when you rewrite a document or when a rule is not clear.
  • references/word-list.md — the 869 approved words with their parts of speech and forms.
  • references/substitutions.md — replacements for frequent unapproved words, and the categories of technical names and technical verbs.
  • examples/before-after.md — examples of text before and after the change to STE.

Basis

The source of this skill is ASD-STE100 Issue 7 (2017). ASD releases new issues of the specification. You can get the specification free of charge from https://www.asd-ste100.org. This skill is not an official ASD document. This skill cannot make sure that your text obeys the official specification fully. Refer to NOTICE.md for the copyright information.

© NeverSight, 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 12 other files in data/skills-md/0xpili/simplified-technical-english/simplified-technical-english of NeverSight/learn-skills.dev.

  • SKILL.md
  • description_ar.txt
  • description_cn.txt
  • description_de.txt
  • description_en.txt
  • description_es.txt
  • description_fr.txt
  • description_it.txt
  • description_ja.txt
  • description_ko.txt
  • description_ru.txt
  • description_tw.txt
  • stats.json

Open the folder on GitHubat commit 50f7fc9

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in NeverSight/learn-skills.dev, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Simplified Technical 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.

Simplified Technical English compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Simplified Technical English this skillNeverSight/learn-skills.dev2161 repos~1.7kAutomated safety check: PassMIT
Beads Documentation Style Guidegastownhall/beads28k—~3.2kAutomated safety check: PassMIT
Technical Writing Standardcursor/plugins10k10 repos~2.4kAutomated safety check: PassNone
Heym Documentation Articlesheymrun/heym1.4k—~780Automated safety check: PassCustom licence
Developer Docs Technical Writervercel-labs/github-tools131—~3.9kAutomated safety check: PassMIT
Aholo Viewer Docsmanycoretech/aholo-viewer1.1k—~341Automated safety check: PassMIT

Similar skills

  • Sets the house style for the beads user docs: the canonical concept model, required terminology, prose and diagram conventions, and checks before docs work is done.

    28k GitHub stars~3.2k tokensUpdated today
    Writing & ContentAuto-check passed
  • Official

    Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.

    10k GitHub starsUsed in 10 repos~2.4k tokens
    Writing & ContentAuto-check passed
  • Creates and updates documentation articles for the Heym platform: category choice, manifest entry, markdown file and cross-links from existing pages.

    1.4k GitHub stars~780 tokensUpdated today
    Writing & ContentAuto-check passed
  • Developer Docs Technical Writer

    vercel-labs/github-tools

    Official

    Writes, reviews and edits developer documentation for SDKs, libraries and frameworks, from getting-started guides and API references to migration guides.

    131 GitHub stars~3.9k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Aholo Viewer Docs

    manycoretech/aholo-viewer

    Guides writing and maintaining Aholo Viewer documentation: README, AGENTS.md, architecture notes, bilingual manual pages and AI collaboration guides.

    1.1k GitHub stars~341 tokensUpdated today
    Writing & ContentAuto-check passed
  • Diataxis

    WebMCP-org/npm-packages

    Write technical documentation following the Diataxis framework by Daniele Procida.

    104 GitHub stars~1.7k tokensUpdated today
    Writing & ContentAuto-check passed

More from NeverSight/learn-skills.dev

All 42 skills in this repo
  • AI Marketing Videos

    NeverSight/learn-skills.dev

    Create AI marketing videos for ads, promos, product launches, and brand content.

    216 GitHub starsUsed in 3 repos~2.1k tokens
    Auto-check passed
  • Google Calendar

    NeverSight/learn-skills.dev

    Interact with Google Calendar via the Google Calendar API – list upcoming events, create new events, update or delete them.

    216 GitHub starsUsed in 2 repos~826 tokens
    Auto-check passed
  • Agent Orchestrator

    NeverSight/learn-skills.dev

    Meta-agent skill for orchestrating complex tasks through autonomous sub-agents.

    216 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed
  • AI Automation Workflows

    NeverSight/learn-skills.dev

    Build automated AI workflows combining multiple models and services.

    216 GitHub starsUsed in 1 repo~2.6k tokens
    Auto-check passed
  • AI Content Pipeline

    NeverSight/learn-skills.dev

    Build multi-step AI content creation pipelines combining image, video, audio, and text.

    216 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed
  • AI Podcast Creation

    NeverSight/learn-skills.dev

    Create AI-powered podcasts with text-to-speech, music, and audio editing.

    216 GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

Questions about Simplified Technical English

What does Simplified Technical English do?

Writes and rewrites text in Simplified Technical English (ASD-STE100), a controlled language for clear technical documentation. dev. Writes and rewrites text in Simplified Technical English (ASD-STE100), a controlled language for clear technical documentation.

When should I use Simplified Technical English?

Simplified Technical English fits situations like: the user asks for STE; simplified Technical English; controlled language; plain technical writing.

How do I install Simplified Technical English in Claude Code?

Run `npx skills add NeverSight/learn-skills.dev --skill simplified-technical-english -a claude-code`. Or copy the skill folder (data/skills-md/0xpili/simplified-technical-english/simplified-technical-english in NeverSight/learn-skills.dev) into .claude/skills/simplified-technical-english in your project. Claude Code loads it when a task matches its description.

How do I install Simplified Technical English in Codex?

Run `npx skills add NeverSight/learn-skills.dev --skill simplified-technical-english -a codex`. Or copy the skill folder (data/skills-md/0xpili/simplified-technical-english/simplified-technical-english in NeverSight/learn-skills.dev) into .agents/skills/simplified-technical-english in your project. Codex loads it when a task matches its description.

Can I use Simplified Technical 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 NeverSight/learn-skills.dev --skill simplified-technical-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/simplified-technical-english, .gemini/skills/simplified-technical-english, .github/skills/simplified-technical-english and .opencode/skills/simplified-technical-english in your project.

What does Simplified Technical English need to run?

Going by SKILL.md and its folder, Simplified Technical English needs the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Simplified Technical English access the network?

SKILL.md names 1 domain. As links in the text: asd-ste100.org. This is read from the text; nothing was executed.

Is Simplified Technical 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 Simplified Technical English use?

Simplified Technical 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 Simplified Technical English use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Simplified Technical English?

Skills that share tags, products or a category with Simplified Technical English: Beads Documentation Style Guide (gastownhall/beads, 28k stars), Technical Writing Standard (cursor/plugins, 10k stars), Heym Documentation Articles (heymrun/heym, 1.4k stars) and Developer Docs Technical Writer (vercel-labs/github-tools, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Simplified Technical English?

NeverSight (a GitHub organization) maintains it in NeverSight/learn-skills.dev, which has 216 GitHub stars. The repository holds 42 skills in this directory. The repository was last updated on October 9, 2026.

Source: NeverSight/learn-skills.dev on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.