mcpField
E
explaining

explaining

github.com/alexanderstephenthompsonProductivity36 installs
Repository

About explaining

A skill for structuring clear explanations, aimed at people teaching, onboarding, or communicating concepts. It distinguishes explanations about a subject from decision-oriented explanations, then guides structure, depth, and supporting techniques.

Key features

  1. 01Classifies Subject and Situational requests
  2. 02Applies a three-phase explanation structure
  3. 03Scales explanations to three depths
  4. 04Uses examples and analogies when useful
  5. 05Includes checklists and worked examples

Use cases

  1. 01Explaining how a concept or process works
  2. 02Helping an audience decide between approaches
  3. 03Preparing onboarding or teaching material
  4. 04Rebuilding understanding when confusion appears

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/alexanderstephenthompson/claude-hub --skill explaining

After installing, type/explainingin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

assets/
depth-comparison.md
explanation-checklist.md
references/
subject-tools.md
situational-domains.md
situational-tools.md
subject-examples.md
situational-examples.md

Details

From the project README

Explaining Skill

Version: 1.0 Source: Explaining Things Playbook

Structure before technique. Depth before detail. Context before content.


Scope and Boundaries

This skill covers: Producing clear explanations — classifying requests, choosing structure, scaling depth, and applying relatability tools.

This skill does NOT cover: Writing style or tone for marketing copy, formal academic writing, or persuasive sales. It covers the structure of persuasion (Situational framework) but not copywriting craft.

Relationship to other skills:

  • Works alongside documentation (which covers what to document; this covers how to explain it)
  • Can be applied inside any domain skill when teaching, onboarding, or communicating concepts

North Star

Goal: The listener builds the right mental model on the first pass.

Definition: A good explanation doesn't just deliver information — it orients the listener, builds understanding in sequence, and connects meaning to something they already care about.

Smell: If the listener asks "but wait, what is it?" after your explanation, you skipped Context. If they ask "okay, but why should I care?" you skipped Connection. If they ask "how does it actually work?" you rushed Content.


Quick Start

Already know the framework? Start here:

I want to...Go to
Explain what something is or how it worksUse the Subject framework (default)
Explain why something matters, persuade, or help someone decideUse the Situational framework
See Subject worked examples at different depthsreferences/subject-examples.md
See Situational worked examples at different depthsreferences/situational-examples.md
See domain-specific mappings (storytelling, data, consulting, etc.)references/situational-domains.md
Browse Subject techniques by phasereferences/subject-tools.md
Browse Situational techniques by phasereferences/situational-tools.md
Compare Short / Medium / Long depth side by sideassets/depth-comparison.md
Follow a step-by-step checklistassets/explanation-checklist.md

For the full framework, read on.


Execution Order

For every explanation request, follow this order without skipping steps:

  1. Classify the request (Subject vs Situational)
  2. Apply the matching 3-phase structure
  3. Choose depth (Short / Medium / Long)
  4. Add supporting tools (examples, analogy, reframing) only if they improve clarity

Classification

Subject (Default)

Use when explaining what something is, how it works, how to do something, or why it exists.

The listener needs to understand a thing.

Situational

Use when explaining why something matters, why one approach is better, how to decide, or how to persuade/reframe behavior.

The listener needs to make a decision or change perspective.

Default Behaviors
  • Default mode: Subject — unless the listener is clearly deciding, justifying, persuading, or reframing.
  • Default structure: Use the full 3-phase framework. Do not skip Context.
  • Default clarity move: If confusion appears, step backward one phase and rebuild the mental model before continuing. Do not add more detail forward — rewind to the missing phase (usually Context), re-establish the model, then continue.

Subject Framework

Use a 3-phase structure. Support explanations with relatability tools when helpful.

Phase 1: Context — Anchor Understanding

Orient the listener. Establish what the thing is, where it fits, and why it exists. Assume no prior knowledge.

Begin with the "what" and "why care." You're orienting, not persuading. Give the simplest possible definition or overview and make it relatable.

Phase 2: Content — Show How It Works

Explain how it works or how to do it. Be concrete, semantic, and example-driven. Avoid abstraction unless necessary.

Break the subject down visually or logically. Use analogy, sequence, or demonstration to make it tangible.

Phase 3: Connection — Translate Meaning

Translate meaning. Explain why it matters, when it's useful, or how it changes outcomes.

End with relevance or impact: how it fits into life, why it's useful, or what it reveals about the world.

Full examples at each depth: references/subject-examples.md Technique catalog by phase: references/subject-tools.md


Situational Framework

Use a 3-phase structure. Keep explanations semantic, practical, and grounded. Favor concrete mental models over formal definitions.

Phase 1: Establish Context

Frame understanding by giving people orientation, purpose, and relevance before going anywhere else. Explain what's happening, why it matters, and connect it to something the listener values so they're aligned and facing the same direction.

Phase 2: Reveal Problem or Opportunity

Focus attention and emotional gravity by surfacing the gap between the current state and a better one. Expose the tension or unmet potential, spark curiosity or concern, and define what's at stake if nothing changes.

Phase 3: Solve

Provide the answer, idea, or path forward with clarity, proof, and action. Present the key insight, support it with reasoning or evidence, and translate it into concrete next steps so people know what to do and why it works.

Full examples at each depth: references/situational-examples.md Domain-specific mappings: references/situational-domains.md Technique catalog by phase: references/situational-tools.md


Depth Scaling

Depth changes how much of the mental model is exposed, not which structure is used. All three depths use the same 3-phase framework.

Short

Prioritize clarity and definition. One or two sentences per phase. Minimal examples.

  • Tone: Crisp and direct — like concise teaching notes.
  • Tools: Rare — only brief, functional comparisons ("Think of it like...").
  • Best for: Elevator pitch, summary, quick answer, memory cue.
Medium

Explain mechanism and intuition. Expand cause-and-effect. Use one illustrative example.

  • Tone: Natural, conversational — reads like how a good teacher talks.
  • Tools: Occasional — similes and short analogies for accessibility.
  • Best for: Blog section, educational video, presentation voiceover, internal briefing.
Long

Explore nuance, tradeoffs, and deeper insight. Use multiple examples, analogies, or edge cases.

  • Tone: Reflective and narrative — reads like a storyteller teaching through insight.
  • Tools: Frequent — rich metaphors, analogies, and anecdotes for flow and memorability.
  • Best for: Long-form article, keynote, essay, documentary narration, deep-dive workshop.

Full comparison table: assets/depth-comparison.md


Relatability & Emphasis Tools

Add these only when they improve clarity. Structure carries the explanation; tools enhance it.

ToolWhat It DoesWhen to UseExample
SimileDirect comparison using "like" or "as"Making an idea vivid and easy to visualize"Explaining without context is like building a house without a foundation."
MetaphorImplies one thing is anotherCreating emotional resonance, collapsing distance between ideas"Context is the foundation of understanding."
AnalogyStructured comparison mapping one relationship onto anotherBuilding logical understanding through parallel structure"Just as a gardener prunes to help plants grow stronger, leaders remove obstacles so teams can thrive."
PersonificationGives human qualities to non-human thingsMaking abstract systems feel alive and empathetic"Data doesn't lie, but it whispers — you have to listen closely."
Example / AnecdoteShort, real-world story or instanceGrounding the abstract in experience, building trust"When I started composting, I realized waste isn't a problem — it's potential."
ParallelismSimilar sentence structure for rhythmAdding flow and emphasis, great for summaries"Measure clearly, act quickly, improve continuously."
Usage by Depth
DepthTool Usage
ShortRare — only brief functional comparisons
MediumOccasional — similes and short analogies
LongFrequent — rich metaphors, analogies, anecdotes

Quick Reference

Before Every Explanation
  • Classified as Subject or Situational
  • Using the correct 3-phase structure
  • Depth chosen (Short / Medium / Long)
  • Context phase is present and sufficient
During the Explanation
  • Phase 1 orients the listener before introducing complexity
  • Phase 2 is concrete, semantic, and example-driven (not abstract)
  • Phase 3 translates meaning back to the listener's world
  • Relatability tools support clarity, not replace structure
  • No phase is skipped
If Confusion Appears
  • Rewinding to the missing phase (usually Context)
  • Rebuilding the mental model before continuing forward
  • NOT adding more detail in the current phase

Anti-Patterns

Anti-PatternWhat It Looks LikeWhy It Fails
The Detail AvalancheListener is confused, so you add more informationConfusion means a phase is missing — more detail buries the gap deeper
The Headless ExplanationJumping straight into Content without ContextThe listener has no mental model to hang information on
The Dangling ExplanationContext and Content but no ConnectionInformation delivered but not translated into meaning or relevance
The Wrong LensUsing Subject framework when the listener needs to decideSubject teaches what; Situational addresses why it matters now
The Technique ShowEvery sentence has an analogy, metaphor, and exampleTools are seasoning, not the meal. Structure carries the explanation
The Expert CurseExplaining at your depth, not the listener'sMatch depth to the audience's starting point, not your knowledge
The Flat ExplanationSame depth across all three phasesContext can be short even when Content is long. Scale each phase to its purpose

References

  • references/subject-examples.md — Subject worked examples at all three depths (Lean Six Sigma, Gardening)
  • references/subject-tools.md — Subject technique catalog organized by phase (Context, Content, Connection)
  • references/situational-examples.md — Situational worked examples at all three depths (Learning to Cook, Small Teams)
  • references/situational-domains.md — Domain-specific mappings (storytelling, data, consulting, teaching, marketing, leadership)
  • references/situational-tools.md — Situational technique catalog organized by phase (Setting Context, Revealing Problems, Solutions)

Assets

  • assets/depth-comparison.md — Side-by-side Short / Medium / Long comparison across all dimensions
  • assets/explanation-checklist.md — Step-by-step execution checklist for producing explanations

Comments

Markdown supported