Explain
Skill control-decks/think-it-through/plugins/think-it-through/skills/explain
A conversation-card deck for exploring, challenging, planning, and explaining ideas with AI.
npx -y skills add control-decks/think-it-through --skill explainAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Explain the current HACP Working Object at the user's requested or apparent level with the minimum detail needed for understanding while preserving its claims and caveats. Use when the user invokes explain, asks for an explanation, or passes a result from another deck into EXPLAIN; never add an explanation silently.
SKILL.md
1.4 KB, as published. Nobody here has run it
💡 Think Explain
ID: think-it-through/explain
HACP: 0.4
Kind: presentation
Mode: render
Traits: read-only, semantic
Default Binding: Current Working Object, latest substantive result, or
clearly named subject
Accepts: hacp/content, hacp/result; accept success and blocked, and
defer pending unless the human asks to explain the proposed action
Produces: think-it-through/explanation
Duration: once
Effect: Explain the smallest unclear point at the human's requested or apparent level while preserving the object's claims, caveats, and uncertainty.
Limits: Do not invent evidence, change claims, advise, choose a direction, repeat the complete source, explain HACP automatically, or use more than one example unless requested.
Format
Begin the complete combo trace with > 🎯 **<binding>** → 💡 **EXPLAIN** when
used alone. Add → 💡 **EXPLAIN** after earlier cards in a combo.
Use Explanation as the only required heading. Add Example only when one
short example removes real ambiguity.