plain
Skill2 starsChanged 38 days agoMITView on GitHub
Explain a change in everyday words, as a brief and as a primer. Use to summarize a change, cut jargon, explain a diff, or write the plain summary in a pull request.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- michele-orsini-71/claude-skillstheir own version, first seen Oct 13, 2026
- dtiger1889-ops/claude-harness-toolboxtheir own version, first seen Oct 12, 2026
- rolandtolnay/llm-toolkittheir own version, first seen Oct 11, 2026
- petekp/claude-code-setuptheir own version, first seen Sep 23, 2026
- trebaud/skillstheir own version, first seen Aug 18, 2026
- rizukirr/vibekittheir own version, first seen Jul 31, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- petekp/claude-code-setup★ 48same name
- dtiger1889-ops/claude-harness-toolbox★ 31same name
- rizukirr/vibekit★ 20same name
- selfishprimate/plain★ 16same name
- rolandtolnay/llm-toolkit★ 1same name
- trebaud/skills★ 1same name
- michele-orsini-71/claude-skills★ 0same name
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 repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- atlassianSkill
- auditSkill
- code-qualitySkill
- commit-expertSkill
- create-issueSkill
- create-prSkill
- debugSkill
- defineSkill
- deliverSkill
- final-reviewSkill
- gherkinSkill
- githubSkill
- handoffSkill
- second-opinionSkill
- senior-technical-writerSkill
- testingSkill
- triageSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
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 13
Explain what matters: Use short sentences and preserve the real names of skills, commands and project terms.
“Common” is measured: kept by at least 6 in 10 of the 5 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
Plain
A brief names the outcome for someone familiar with the area. A primer explains the same change for someone unfamiliar with it, adding only the context needed to understand it.
Rules
- Keep the facts consistent. Lead each version with what changes. Ground the primer's context in the same evidence as the brief.
- Explain what matters. Use short sentences and preserve the real names of skills, commands and project terms. Explain an unfamiliar term only when its meaning is needed to understand the change; prefer explaining the behaviour and its consequence.
Output
## Brief
...
## Primer
...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.