agentleFS
tykisgodtykisgod/quick-question/skills/grandma/SKILL.md

grandma

Skill12 starsChanged 8 months agoMITView on GitHub

Explain technical concepts using everyday analogies that a grandma or 5-year-old could understand.

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
  1. Distinctive:

    Understand the topic: If it's a project module, quickly read design docs and core code to understand what it actually does

    line 11
  2. Distinctive:

    If the concept has multiple layers, use different roles/stages within the SAME scenario — don't switch scenarios

    line 15
  3. Distinctive:

    Start with the scene: "Imagine you're at..."

    line 17
  4. Distinctive:

    After the analogy, "translate" back in one sentence: "What we just called X is actually Y in the code"

    line 19
  5. Distinctive:

    Use technical jargon (unless the user is asking what a specific term means)

    line 22

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).

Arguments: $ARGUMENTS — any technical concept, module, or design decision (e.g., "ECS", "why does the task system use a push model", "what is MCP", "A* pathfinding algorithm")

Behavior

  1. Understand the topic: If it's a project module, quickly read design docs and core code to understand what it actually does
  2. Find an everyday life analogy that:
    • Uses a scenario everyone has experienced (cooking, queuing, moving house, school, grocery shopping...)
    • Covers the core mechanism, not just a surface similarity
    • If the concept has multiple layers, use different roles/stages within the SAME scenario — don't switch scenarios
  3. Explain the entire concept through the analogy:
    • Start with the scene: "Imagine you're at..."
    • Map each role and action in the scene to key parts of the technical concept
    • After the analogy, "translate" back in one sentence: "What we just called X is actually Y in the code"
  4. If there are common misconceptions, address them: "Many people think... but actually..."
  5. Don't:
    • Use technical jargon (unless the user is asking what a specific term means)
    • Show code
    • Say "simply put" followed by something not simple
    • Say "it's like in programming..." — the audience doesn't know programming, that's not an analogy
    • Be condescending ("this is basic", "you can think of it as")

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.