explain-for-grandma
Skill4 starsChanged 5 months agoMITView on GitHub
Re-explain the previous response in plain, beginner-friendly language — decode the jargon, buzzwords, and technical concepts.
In this repository18 other files it gives its agents.
- biz-validateSkill
- braindumpSkill
- catch-upSkill
- clone-websiteSkill
- double-checkSkill
- heavy-buildSkill
- heavy-reviewSkill
- heavySkill
- make-promptSkill
- monitor-claudeSkill
- orientSkill
- overnightSkill
- reelSkill
- sanity-checkSkill
- save-sessionSkill
- shipSkill
- what-breaksSkill
- yt-tranSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
If arguments were given ($ARGUMENTS), focus only on that specific word or part — and if it didn't actually appear in the previous response, …
- Distinctive: line 11
Use exactly this short structure:
- Distinctive: line 23
Keep it short and brief. This is a quick translation, not a lecture.
- Distinctive: line 25
Do not introduce any new jargon.
- Distinctive: line 26
Do not add new information, research anything, or use tools.
- Distinctive: line 27
Prefer everyday analogies over precise-but-confusing definitions.
- Distinctive: line 28
If there is no previous assistant response to explain, say so in one line and ask what they'd like explained.
≈ “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
The user just read your previous response and wasn't sure what some of it meant — the jargon, buzzwords, tools, models, or technical concepts. Re-explain that previous assistant message in plain, beginner-friendly language.
If arguments were given ($ARGUMENTS), focus only on that specific word or part — and if it didn't actually appear in the previous response, just explain the term itself. If empty, explain the whole previous response.
Use exactly this short structure:
What this was about One plain sentence: the problem being solved or the thing being discussed — the context, so they remember what it was for.
In plain words 2–4 simple sentences capturing the gist of the previous response — what it means and why it matters. No jargon here at all.
The jargon, decoded
A short bullet list. For each buzzword, technical term, tool, or model name that appeared in the previous response, one bullet: **term** — one simple sentence, with a real-world analogy if it helps. Skip trivial words; if the response was dense with terms, cover only the handful that actually matter for understanding it.
Rules:
- Keep it short and brief. This is a quick translation, not a lecture.
- Assume zero background knowledge, but never be condescending. "Grandma-friendly" means clear and jargon-free — not dumbed-down or patronizing.
- Do not introduce any new jargon. If a technical word is unavoidable, define it on the spot.
- Do not add new information, research anything, or use tools. Only re-explain what was already said in the previous response.
- Prefer everyday analogies over precise-but-confusing definitions.
- If there is no previous assistant response to explain, say so in one line and ask what they'd like explained.
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.

