ste
Skill9 starsChanged 33 days agoMITView on GitHub
Explain technical ideas in clear, precise language. Use when an explanation is confusing, jargon-heavy, vague, or hard to follow, or when the user asks for Standard Technical English.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- chrisdesmondSML/chris-skillsword for word, first seen Nov 8, 2026
- aditya-vermax/skillstheir own version, first seen Nov 8, 2026
- mryll/skillstheir own version, first seen Nov 1, 2026
- dualface/ste-zhtheir own version, first seen Oct 31, 2026
- Ronnasayd/aipptheir own version, first seen Oct 20, 2026
- tslateman/skillstheir own version, first seen Oct 11, 2026
Other versions16 projects use a version of this.
Word for word · 1
- chrisdesmondSML/chris-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 15
- penpot/penpot★ 62ksame name
- dualface/ste-zh★ 824same name
- takara-ai/miru-code★ 12same name
- mryll/skills★ 8same name
- nonatofabio/claude-writing-skills★ 8same name
- didier/skills★ 2same name
- aditya-vermax/skills★ 1same name
- cal1888/claude-code-skills★ 1same name
- geekxx/ai-assistant-starter-kit★ 1same name
- hastefuI/skills★ 1same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- agentationSkill
- animateSkill
- better-uiSkill
- codexSkill
- interviewSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Start with what the thing does and why it matters.
- Distinctive: line 13
Use one main idea per sentence.
- Distinctive: line 14
Prefer common, concrete words.
- Distinctive: line 16
Prefer active voice and name the actor: say what component performs each action.
- Distinctive: line 18
Put steps in the order they happen.
- Distinctive: line 20
Use a short example when the idea is abstract.
- Distinctive: line 21
Use lists for steps or parallel items.
- Distinctive: line 22
Remove filler, vague intensifiers, and decorative jargon.
- Distinctive: line 24
Do not make the explanation less accurate just to make it shorter.
- Distinctive: line 28
Before finishing, confirm that every pronoun has a clear referent, every technical term is defined or familiar to the intended reader, and …
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Clear Technical English
Explain the subject so the reader can understand it on the first pass without losing technical accuracy.
Write the explanation
- Start with what the thing does and why it matters.
- Use one main idea per sentence.
- Prefer common, concrete words. Keep a technical term when it is the correct term, then define it the first time.
- Expand an acronym the first time you use it.
- Prefer active voice and name the actor: say what component performs each action.
- State cause and effect directly.
- Put steps in the order they happen.
- Separate confirmed behavior, assumptions, and recommendations.
- Use a short example when the idea is abstract.
- Use lists for steps or parallel items. Use prose when the ideas depend on one another.
- Remove filler, vague intensifiers, and decorative jargon.
Do not make the explanation less accurate just to make it shorter. If a detail is uncertain, say what is unknown and what would verify it.
Check the result
Before finishing, confirm that every pronoun has a clear referent, every technical term is defined or familiar to the intended reader, and each step says what changes and why.
This skill follows the general goals of clear technical communication. It does not certify formal ASD-STE100 compliance.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.