explain-metaphor

Explains abstract concepts through concrete everyday metaphors with explicit mappings and stated limitations.

5|Updated Sep 24, 2017
One-click install
npx skills add https://github.com/madyankin/dotfiles --skill explain-metaphor-madyankin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: explain-metaphor
Source: https://github.com/madyankin/dotfiles/tree/main/.config/agents/skills/explain-metaphor
Command: npx skills add https://github.com/madyankin/dotfiles --skill explain-metaphor-madyankin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Abstract or technical concepts are hard to grasp and remember when explained only in formal terms. This Skill turns a difficult idea into a familiar everyday scene so the user can build an intuitive mental model without losing technical accuracy. ## Core Features & Use Cases - Causal Mapping: Identifies the concept's actors, state, events, and dependencies, then maps each element onto a familiar domain such as a kitchen, workplace, or traffic system. - Honest Limitations: Explicitly states where the metaphor breaks so the analogy never silently replaces an important technical qualification. - Structured Output: Delivers a compact five-part answer: one-sentence summary, metaphor, mapping, where it breaks, and a technically accurate restatement. - Use Case: A developer struggling to understand database connection pooling asks for an analogy and receives a restaurant-waiter metaphor with each component mapped back to pool size, checkout, and timeout behavior. ## Quick Start Ask the assistant to explain a concept like database indexing or recursion using the explain-metaphor skill with a concrete everyday analogy.

Frequently Asked Questions about explain-metaphor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I explain a technical concept with an analogy?▼

Identify the concept's causal skeleton first: actors, state, events, and dependencies. Then pick a familiar domain with the same relationships, map each element explicitly, and walk through one concrete scenario before returning to the real concept.

What makes a good metaphor for explaining complex ideas?▼

A good metaphor preserves relationships rather than superficial appearance, uses concrete nouns and actions, and comes from a domain familiar to the audience. One strong metaphor beats several loose analogies.

Can metaphors be used for safety-critical or legal topics?▼

Yes, but the metaphor must be labeled as intuition only, with the precise rule stated separately. The analogy should never silently replace a technically important qualification in medical, legal, or financial contexts.

When should I avoid using analogies to explain something?▼

Avoid analogies when they would infantilize the audience or sacrifice correctness for simplicity. If no familiar domain shares the concept's actual relationships, a direct technical explanation is more honest than a misleading comparison.

How do I compare two systems using a single metaphor?▼

Hold the scene constant and change only the mechanism that differs between the two systems. This isolates the actual distinction so the contrast is clear without introducing confounding differences from separate analogies.