Skip to content
Back to skills

Grandma

ASecurity

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

  • 11 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added May 26, 2026
developmentgo

Works with

  • mcp

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add tykisgod/quick-question --skill grandma --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Grandma?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Grandma
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tykisgod-grandma/badge)](https://www.skillsdirectory.com/skills/tykisgod-grandma)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: "Explain technical concepts using everyday analogies that a grandma or 5-year-old could understand."
---

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")

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.