Diagram Design
cathrynlavery/diagram-design
Creates branded diagrams, from architecture, flowchart and sequence to charts and maps, as self-contained HTML with inline SVG, with import from draw.io, Mermaid and Excalidraw.
Write or rewrite text in ASD-STE100 Simplified Technical English.
Install Ste
$ npx skills add penpot/penpot --skill ste -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install penpot/penpot ste --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/penpot/penpot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/ste .claude/skills/ste && 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 "ste" agent skill from https://github.com/penpot/penpot/tree/develop/.agents/skills/ste into .claude/skills/ste/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ste", 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/penpot/penpot/tree/develop/.agents/skills/steType 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 penpot/penpot --skill ste -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install penpot/penpot ste --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/penpot/penpot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/ste .agents/skills/ste && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ste" agent skill from https://github.com/penpot/penpot/tree/develop/.agents/skills/ste into .agents/skills/ste/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ste", 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 penpot/penpot --skill ste -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install penpot/penpot ste --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/penpot/penpot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/ste .cursor/skills/ste && 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 "ste" agent skill from https://github.com/penpot/penpot/tree/develop/.agents/skills/ste into .cursor/skills/ste/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ste", 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/penpot/penpot.git --path .agents/skills/ste--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 penpot/penpot --skill ste -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install penpot/penpot ste --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/penpot/penpot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/ste .gemini/skills/ste && 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 "ste" agent skill from https://github.com/penpot/penpot/tree/develop/.agents/skills/ste into .gemini/skills/ste/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ste", 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 penpot/penpot steInstalls 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 penpot/penpot --skill ste -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/penpot/penpot.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/ste .github/skills/ste && 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 "ste" agent skill from https://github.com/penpot/penpot/tree/develop/.agents/skills/ste into .github/skills/ste/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ste", 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 penpot/penpot --skill ste -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install penpot/penpot ste --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/penpot/penpot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/ste .opencode/skills/ste && 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 "ste" agent skill from https://github.com/penpot/penpot/tree/develop/.agents/skills/ste into .opencode/skills/ste/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ste", 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
ste- GitHub stars
- 61k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 800 words
- Files
- 3 (incl. references)
- Skills in repo
- 24
- Repo updated
- First seen
- Licence
- MPL-2.0
At a glance
Write or rewrite text in ASD-STE100 Simplified Technical English.
- Works in 2 steps: Classify the text → Self-check pass
- The user explicitly invokes it by name — i.e
- SKILL.md covers When to use, Step 0 — Classify the text, Core rules and Step 2 — Self-check pass, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ste is an agent skill from penpot/penpot. Write or rewrite text in ASD-STE100 Simplified Technical English. ONLY use this skill when the user explicitly invokes it by name — i.e. they type "/ste" or literally write "use the ste skill" / "apply ASD-STE100". Do NOT trigger it on paraphrased intent such as "simplify this", "make it clearer", "write technical documentation", or "shorter sentences please" — the user has deliberately scoped this skill to explicit invocation only. For those requests, respond normally without loading this skill unless they name…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/examples.md` and `references/word-substitutions.md`).
It sits in Development, covering Technical documentation. The repository describes itself as: Penpot: The open-source design platform for Product teams that need scalable collaboration. The licence is MPL-2.0.
When your agent uses it
- The user explicitly invokes it by name — i.e
- It on paraphrased intent such as simplify this
- Make it clearer
- Write technical documentation
Example prompts
- “or literally write”
- “apply ASD-STE100”
- “simplify this”
- “/ste”
Workflow steps
2 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit fc8a126. 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
Ste loads about 1.5k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 131 tokens; SKILL.md has 800 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 penpot/penpot at commit fc8a126, republished under its MPL-2.0 licence (© penpot). 800 words, ~1,496 tokens.
Download SKILL.mdSave it as
.claude/skills/ste/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- ste
- description
- Write or rewrite text in ASD-STE100 Simplified Technical English. ONLY use this skill when the user explicitly invokes it by name — i.e. they type "/ste" or literally write "use the ste skill" / "apply ASD-STE100". Do NOT trigger it on paraphrased intent such as "simplify this", "make it clearer", "write technical documentation", or "shorter sentences please" — the user has deliberately scoped this skill to explicit invocation only. For those requests, respond normally without loading this skill unless they name it.
ASD-STE100 Simplified Technical English
Apply the ASD-STE100 standard to all prose you produce in this task. Do not announce that you use STE, do not name the standard, and do not explain the style unless the user asks. If the user later asks you to "write more naturally," ask one short question to confirm they want to leave STE before you drop it.
Compliance note (for you, not for output): the official specification and its dictionary are copyright ASD. This skill encodes paraphrased rules and a publicly sourced word list. For certified aerospace/defense deliverables, tell the user that full compliance requires the free official specification (asd-ste100.org) and a human sign-off. Never claim certified compliance.
When to use
Only when the user explicitly invokes it: they type /ste, or say "use
the ste skill" / "apply ASD-STE100". Requests like "simplify this",
"make it clearer", or "shorter sentences" do NOT invoke it — respond
normally unless it is named.
Step 0 — Classify the text
Before writing a single sentence, decide: is this procedural text (instructions someone follows) or descriptive text (explanation, background, description)? Every limit below depends on this. Mixed documents get classified section by section.
Core rules
Sentences
- Procedural: maximum 20 words per sentence.
- Descriptive: maximum 25 words per sentence.
- Maximum 6 sentences per paragraph. One topic per paragraph.
- One instruction per sentence. Two actions in one sentence only if they occur at the same time.
- Put a condition BEFORE its command: "If the pressure decreases, close the valve."
- Do not omit articles, subjects, or verbs to save words. "Ensure file exists" is wrong; "Make sure that the file exists" is correct. Keep the word "that" after verbs like "make sure."
- Numbers, units with numbers, abbreviations, quoted strings, code identifiers, and proper nouns each count as one word.
Verbs
- Allowed forms only: infinitive, imperative, simple present, simple past, simple future, and past participle used as an adjective.
- Never use present perfect or continuous forms. "We have received" → "We received." "is being tested" → a simple form.
- Never use an -ing form as a verb. An -ing word is allowed only inside a technical name ("the mounting bracket," "logging").
- Active voice. Passive is allowed only in descriptive text when the agent is unknown or unimportant.
- Instructions use the imperative: "Open the panel," not "You must open the panel" or "The panel should be opened."
- Express actions as verbs, not nouns: "compress the file," not "perform compression of the file."
- Modals: use can (possibility), will (future), must (requirement). Do not use should, would, could, may, might. A hedge becomes a fact or a "can": "an explosion can occur."
- No phrasal verbs: "go down" → "decrease," "set up" → "install," "carry out" → "do."
Show full SKILL.md (356 more words)Show less
Words
- One word, one meaning, one part of speech, used consistently. Never rotate synonyms: pick one name for a thing and repeat it.
- Before drafting, replace unapproved vocabulary. Read
references/word-substitutions.mdand apply it; it is the working dictionary for this skill. - Domain-specific nouns (part names, tool names, product names, UI labels) and domain verbs (drill, ream, boot, compile) are your technical nouns/verbs — keep them as-is, use each consistently, and do not verb a noun or noun a verb.
- Noun clusters: maximum 3 words ("overhead panel light" is the limit). Longer clusters get decomposed with prepositions or hyphenated on first use: "main-gear-door retraction-winch handle."
- American English spelling.
- No Latin abbreviations: "e.g." → "for example," "i.e." → "that is," delete "etc."
Punctuation
- No semicolons — write two sentences.
- Parentheses only for references, abbreviations, and item numbers.
- Hyphenate words that act as one unit; a hyphenated word counts as one word.
- No contractions.
Warnings, cautions, notes
- WARNING = risk of injury or death. CAUTION = risk of damage. NOTE = information only, never an instruction.
- Start a warning or caution with the command or condition, then give the risk: "WARNING: Do not touch the terminal. The terminal has a dangerous voltage."
- Notes obey the 25-word descriptive limit.
Step 2 — Self-check pass
After drafting, scan your text once for each of these and fix every hit before you respond:
- Any sentence over the 20/25-word limit for its type
- Contractions, semicolons
- "should," "would," "could," "may," "might"
- "has been," "have been," "had been," "is being," "was being"
- -ing words used as verbs
- Missing articles (a/an/the/this) before nouns
- Synonym rotation (the same object under two names)
- Any word in the unapproved column of
references/word-substitutions.md - Warnings that state the risk before the command
Reference files
references/word-substitutions.md— unapproved → approved word mappings and one-meaning rulings. Read it before drafting; it is short.references/examples.md— worked before/after rewrites (procedural, descriptive, warnings, common mistakes). Read it when rewriting existing text or when unsure how a rule applies.
What NOT to touch
Code blocks, command strings, file paths, error messages, quoted UI text, and proper nouns stay exactly as written. STE applies to the prose around them.
© penpot, MPL-2.0. 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/ste of penpot/penpot.
- SKILL.md
- references/examples.md
- references/word-substitutions.md
Open the folder on GitHubat commit fc8a126
Compare with similar skills
Ste 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 |
|---|---|---|---|---|---|---|
| Ste this skillpenpot/penpot | 61k | — | ~1.5k | Automated safety check: Pass | MPL-2.0 | |
| Diagram Designcathrynlavery/diagram-design | 44k | 1 repos | ~7.5k | Automated safety check: Pass | MIT | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Get API Docs with chubandrewyng/context-hub | 14k | 2 repos | ~775 | Automated safety check: Pass | MIT | |
| Doc SyncJetBrains/ideavim | 10k | 2 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Mailspring App ScreenshotsFoundry376/Mailspring | 18k | — | ~1.4k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Simple English
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.
Get API Docs with chub
andrewyng/context-hub
Fetches current documentation for third-party APIs and SDKs with the chub CLI before the agent writes code against them, instead of relying on remembered API shapes.
- Official
Doc Sync
JetBrains/ideavim
Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.
Mailspring App Screenshots
Foundry376/Mailspring
Captures screenshots of the running Mailspring dev app for docs, PRs or visual checks by launching it with a debugging port, driving the UI and clipping to an element.
Draw.io Diagram Studio
Agents365-ai/drawio-skill
Creates and edits editable draw.io diagrams from descriptions, code, infrastructure files, SQL and API schemas, with sync, review, test and export tools.
More from penpot/penpot
All 24 skills in this repoSecurity And Hardening
penpot/penpot
Hardens code against vulnerabilities. An agent skill from penpot/penpot.
Create PR
penpot/penpot
PR flow — open a new PR for the current task branch (validates base branch, commits, issue and push state) or update an existing PR's title or description to match Penpot conventions.
Bat Cat
penpot/penpot
A cat clone with syntax highlighting, line numbers, and Git integration - a modern replacement for cat.
Local CI
penpot/penpot
Run local CI-style checks with ./scripts/ci (lint, tests, format) per monorepo module.
Code Review Criteria
penpot/penpot
Code review criteria — the five review axes, core principles, severity format, and verdict for reviewing code changes.
Create Commit
penpot/penpot
Stage, review, and commit files following Penpot commit conventions.
Related
Categories
Questions about Ste
What does Ste do?
Write or rewrite text in ASD-STE100 Simplified Technical English. Ste is an agent skill from penpot/penpot. Write or rewrite text in ASD-STE100 Simplified Technical English.
When should I use Ste?
Ste fits situations like: the user explicitly invokes it by name — i.e; it on paraphrased intent such as simplify this; make it clearer; write technical documentation.
How do I install Ste in Claude Code?
Run `npx skills add penpot/penpot --skill ste -a claude-code`. Or copy the skill folder (.agents/skills/ste in penpot/penpot) into .claude/skills/ste in your project. Claude Code loads it when a task matches its description.
How do I install Ste in Codex?
Run `npx skills add penpot/penpot --skill ste -a codex`. Or copy the skill folder (.agents/skills/ste in penpot/penpot) into .agents/skills/ste in your project. Codex loads it when a task matches its description.
Can I use Ste 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 penpot/penpot --skill ste -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ste, .gemini/skills/ste, .github/skills/ste and .opencode/skills/ste in your project.
What does Ste need to run?
SKILL.md names no scripts, command-line tools or credentials: Ste is instructions for the agent only.
Does Ste 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 Ste 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 Ste use?
Ste is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ste use?
About 1.5k tokens (SKILL.md is roughly 6k 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.6k tokens, read only when the agent opens those files.
What are the alternatives to Ste?
Skills that share tags, products or a category with Ste: Diagram Design (cathrynlavery/diagram-design, 44k stars), Simple English (moeru-ai/airi, 50k stars), Get API Docs with chub (andrewyng/context-hub, 14k stars) and Doc Sync (JetBrains/ideavim, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ste?
penpot (a GitHub organization) maintains it in penpot/penpot, which has 60,770 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 7, 2026.
Source: penpot/penpot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.