Token导航 LogoToken导航TokenDH.com
待分类只读github未标认证来源可访问许可证需确认审计通过

explainingexplaining 命令行

Agent Skill

explaining 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

424

周安装

17

GitHub Stars

1

下载量

137
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:explaining(explaining 命令行)
来源仓库:https://github.com/alexanderstephenthompson/claude-hub
仓库路径:skills/explaining
安装命令:
npx skills add https://github.com/alexanderstephenthompson/claude-hub --skill explaining
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

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

简介

用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。

  • 适合在需要围绕仓库状态、代码变更或协作事项进行整理时使用。
  • 可结合来源仓库、安装命令和原始 README 继续核验具体用法。
  • 安装命令:npx skills add https://github.com/alexanderstephenthompson/claude-hub --skill explaining
  • 注意:使用前请确认权限范围和维护状态,避免触发不必要的网络请求或文件操作。

SKILL.md

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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude

33.38%
按下载量换算46

Codex

32.89%
按下载量换算45

Cursor

18.52%
按下载量换算25

Gemini CLI

9.36%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills