PR Finalize Review
microsoft/garnet
Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.
Write explanations and chat in the style of ASD-STE100 Simplified Technical English: short active sentences, one idea each, plain approved words.
Install Simplified Technical English
$ npx skills add OpenHands/extensions --skill simplified-technical-english -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OpenHands/extensions simplified-technical-english --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/simplified-technical-english .claude/skills/simplified-technical-english && rm -rf skills-srcUse ~/.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/
Install the "simplified-technical-english" agent skill from https://github.com/OpenHands/extensions/tree/main/skills/simplified-technical-english into .claude/skills/simplified-technical-english/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "simplified-technical-english", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/OpenHands/extensions/tree/main/skills/simplified-technical-englishType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add OpenHands/extensions --skill simplified-technical-english -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OpenHands/extensions simplified-technical-english --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/simplified-technical-english .agents/skills/simplified-technical-english && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "simplified-technical-english" agent skill from https://github.com/OpenHands/extensions/tree/main/skills/simplified-technical-english into .agents/skills/simplified-technical-english/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "simplified-technical-english", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenHands/extensions --skill simplified-technical-english -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OpenHands/extensions simplified-technical-english --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/simplified-technical-english .cursor/skills/simplified-technical-english && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "simplified-technical-english" agent skill from https://github.com/OpenHands/extensions/tree/main/skills/simplified-technical-english into .cursor/skills/simplified-technical-english/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "simplified-technical-english", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/OpenHands/extensions.git --path skills/simplified-technical-english--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add OpenHands/extensions --skill simplified-technical-english -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OpenHands/extensions simplified-technical-english --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/simplified-technical-english .gemini/skills/simplified-technical-english && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "simplified-technical-english" agent skill from https://github.com/OpenHands/extensions/tree/main/skills/simplified-technical-english into .gemini/skills/simplified-technical-english/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "simplified-technical-english", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install OpenHands/extensions simplified-technical-englishInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add OpenHands/extensions --skill simplified-technical-english -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/simplified-technical-english .github/skills/simplified-technical-english && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "simplified-technical-english" agent skill from https://github.com/OpenHands/extensions/tree/main/skills/simplified-technical-english into .github/skills/simplified-technical-english/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "simplified-technical-english", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenHands/extensions --skill simplified-technical-english -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OpenHands/extensions simplified-technical-english --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/simplified-technical-english .opencode/skills/simplified-technical-english && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "simplified-technical-english" agent skill from https://github.com/OpenHands/extensions/tree/main/skills/simplified-technical-english into .opencode/skills/simplified-technical-english/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "simplified-technical-english", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
simplified-technical-english- GitHub stars
- 157
- Token cost
- ~788 tokens
- SKILL.md length
- 391 words
- Files
- 5
- Skills in repo
- 78
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write explanations and chat in the style of ASD-STE100 Simplified Technical English: short active sentences, one idea each, plain approved words.
- Tasks that involve Commit messages
- SKILL.md covers Core rules, The hard boundary: prose, not…, When to use it and When not to use it, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Pull requests
What it does
Simplified Technical English is an agent skill from OpenHands/extensions. Write explanations and chat in the style of ASD-STE100 Simplified Technical English: short active sentences, one idea each, plain approved words. Use this when the reader benefits from maximum clarity: summaries, PR descriptions, safety- or ops-critical instructions, or any comment or reply that should be easy to read the first time. Applies to PROSE ONLY; it must never change code, identifiers, APIs, or commit messages.
Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `.plugin/plugin.json` and `README.md`).
It sits in Development, covering Commit messages and Pull requests. The repository describes itself as: Public registry for OpenHands extensions. The licence is MIT.
When your agent uses it
- Tasks that involve Commit messages
- Tasks that involve Pull requests
Example prompts
- “/simplified-technical-english”
What it can do on your machine
Read from SKILL.md and the folder at commit d008b81. 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.
Context cost
Simplified Technical English loads about 788 tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 391 words of instructions outside code blocks.
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 OpenHands/extensions at commit d008b81, republished under its MIT licence (© OpenHands). 391 words, ~788 tokens.
Download SKILL.mdSave it as
.claude/skills/simplified-technical-english/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- simplified-technical-english
- description
- Write explanations and chat in the style of ASD-STE100 Simplified Technical English: short active sentences, one idea each, plain approved words. Use this when the reader benefits from maximum clarity: summaries, PR descriptions, safety- or ops-critical instructions, or any comment or reply that should be easy to read the first time. Applies to PROSE ONLY; it must never change code, identifiers, APIs, or commit messages.
- license
- MIT
- triggers
- simplified technical english, STE, ASD-STE100
Simplified Technical English
ASD-STE100 Simplified Technical English is a controlled-language standard from aerospace and defense. It exists to make technical text easy to read the first time, especially for people who read English as a second language. This skill adapts its spirit for agent prose.
Apply it to your prose: chat replies, explanations, summaries, step lists, recommendations. The goal is easy reading, not dumbed-down thinking. Open the text up and keep the substance.
Core rules
- Prefer short sentences. Aim for 20 words or fewer, particularly for instructions.
- One idea per sentence, one topic per paragraph. Split a sentence that carries two ideas.
- Active voice. Write "Run the tests", not "The tests should be run".
- Plain, consistent words. Prefer a common word over a fancy one. Use one word for one idea. Do not switch synonyms for the same thing mid-text.
- Say the thing directly. Lead with the answer. Give the number, name, or path. Cut filler like "in terms of", "a range of", "going forward".
- Positive instructions. Tell the reader what to do, not only what to avoid.
The hard boundary: prose, not code
A controlled English vocabulary must never bleed into the code the agent writes.
- Do not simplify or rename variables, functions, types, files, config keys, CLI flags, API fields, or error strings to obey "approved words". Code needs exact, domain-precise names.
- Do not apply it to commit messages, code comments, or reference/API documentation, where technical precision and established terminology win.
- Do keep using the project's real domain terms in prose. Naming a concept correctly beats naming it "simply".
If clarity and a required technical term ever conflict in prose, keep the term and add a short plain-English gloss beside it.
Show full SKILL.md (108 more words)Show less
When to use it
- The user asked for plain or simple or clear text.
- Instructions where a misread is costly (ops, deploys, security steps).
- Long or dense explanations that need to be scannable.
When not to use it
- Code, identifiers, commit messages, or API/reference docs (see the boundary above).
- Creative or personal-voice writing, where rhythm and personality matter more than the controlled register.
- Cases where a precise domain term must stay exact. Keep the term.
Attribution
Standard: ASD-STE100 (ASD, the AeroSpace and Defence Industries Association of Europe). This skill adapts its principles for agent prose; it is not the official specification and does not reproduce its controlled dictionary.
© OpenHands, 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 4 other files in skills/simplified-technical-english of OpenHands/extensions.
- SKILL.md
- .claude-plugin
- .codex-plugin
- .plugin/plugin.json
- README.md
Open the folder on GitHubat commit d008b81
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Simplified Technical English this skillOpenHands/extensions | 157 | — | ~788 | Automated safety check: Pass | MIT | |
| PR Finalize Reviewmicrosoft/garnet | 12k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Git Workflow and Versioningaddyosmani/agent-skills | 102k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Emoji Commit ConventionsbaptisteArno/typebot.io | 11k | — | ~424 | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
Emoji Commit Conventions
baptisteArno/typebot.io
Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.
Commit And PR Messages
superplanehq/superplane
Write Git commit messages and pull request titles/descriptions using the Chris Beams / Tim Pope conventions (subject/body split, ~50-char subject, imperative mood, why-not-how body) plus ASD-STE100…
More from OpenHands/extensions
All 78 skills in this repoAgent Readiness Report
OpenHands/extensions
Evaluate how well a codebase supports autonomous AI-assisted development.
Discord
OpenHands/extensions
Build and automate Discord integrations (bots, webhooks, slash commands, and REST API workflows).
GitHub
OpenHands/extensions
Interact with GitHub repositories, pull requests, issues, and workflows using the GITHUBTOKEN environment variable and GitHub CLI.
GitHub Issue To PR
OpenHands/extensions
Create an automation that implements GitHub issues when a configurable trigger label is applied.
GitHub Repo Monitor
OpenHands/extensions
This skill should be used when the user asks to "monitor a GitHub repository", "watch GitHub for issues or PRs", "respond to @OpenHands mentions on GitHub", "set up an OpenHands GitHub integration"…
GitLab Issue To Mr
OpenHands/extensions
Create an automation that implements GitLab issues when a configurable trigger label is applied.
Related
Categories
Questions about Simplified Technical English
What does Simplified Technical English do?
Write explanations and chat in the style of ASD-STE100 Simplified Technical English: short active sentences, one idea each, plain approved words. Simplified Technical English is an agent skill from OpenHands/extensions. Write explanations and chat in the style of ASD-STE100 Simplified Technical English: short active sentences, one idea each, plain approved words.
When should I use Simplified Technical English?
Simplified Technical English fits situations like: tasks that involve Commit messages; tasks that involve Pull requests.
How do I install Simplified Technical English in Claude Code?
Run `npx skills add OpenHands/extensions --skill simplified-technical-english -a claude-code`. Or copy the skill folder (skills/simplified-technical-english in OpenHands/extensions) 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 OpenHands/extensions --skill simplified-technical-english -a codex`. Or copy the skill folder (skills/simplified-technical-english in OpenHands/extensions) 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 OpenHands/extensions --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?
SKILL.md names no scripts, command-line tools or credentials: Simplified Technical English is instructions for the agent only.
Does Simplified Technical 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 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 788 tokens (SKILL.md is roughly 3.2k 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: PR Finalize Review (microsoft/garnet, 12k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars) and Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k 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?
OpenHands (a GitHub organization) maintains it in OpenHands/extensions, which has 157 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 6, 2026.
Source: OpenHands/extensions on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.