simply
Skill0 starsChanged 54 days agoMITView on GitHub
Re-explain the current discussion, plan, or design in plain language with short analogies and simple diagrams. Use when the user says /simply, simply, eli5, plain English, simplify, or asks to restate the plan so it is easy to follow.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Alex-Broughton/claude-skillstheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Alex-Broughton/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 repository9 other files it gives its agents.
- agent-browserSkill
- anti-slopSkill
- better-colorsSkill
- better-typographySkill
- better-uiSkill
- hydrateSkill
- ingestSkill
- make-interfaces-feel-betterSkill
- shipSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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 18
No new recommendations unless required to clear a real confusion.
- Distinctive: line 19
Avoid code dumps and long path lists.
- Distinctive: line 20
Prefer short sentences and everyday words.
- Distinctive: line 21
If a technical term is unavoidable, define it in one line on first use.
- Distinctive: line 51
Only include terms that appeared in the discussion.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/simply
Restate the ongoing discussion or proposed plan so it is easy to understand quickly. Do not implement, expand scope, or re-litigate decisions unless asked.
Hard rules
- No new recommendations unless required to clear a real confusion.
- Avoid code dumps and long path lists; one concrete example is enough when useful.
- Prefer short sentences and everyday words.
- If a technical term is unavoidable, define it in one line on first use.
- Lead with the big picture in ≤3 sentences.
Output format
1. In one breath
2–3 sentences: what we are doing and why.
2. The plan like a story
Numbered steps a smart non-expert can follow:
- …
- …
- …
3. Picture it
One of:
- a small ASCII diagram, or
- a short Mermaid flowchart (about 5–12 lines)
4. Words that sound scary
| Term | Plain meaning |
| … | … |
Only include terms that appeared in the discussion.
5. What “done” looks like
3–5 bullets of observable outcomes (not implementation chores).
6. Open questions (only if real)
Bullets for unresolved choices that still need a human decision. Omit if none.
Tone
Direct, clear, lightly conversational. No fluff, no praise filler, no prompt restating.
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.