Help us improve
Share bugs, ideas, or general feedback.
Catalogs 10 epistemic protocols for Claude Code with cluster groupings, command lookups, and situation matching. Invoke /catalog for quick reference or details.
npx claudepluginhub jongwony/epistemic-protocols --plugin epistemic-cooperativeHow this skill is triggered — by the user, by Claude, or both
Slash command
/epistemic-cooperative:catalogThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Instant reference handbook for 10 epistemic protocols. Browse by cluster, look up by command, or find the right protocol for a situation.
Recommends epistemic protocols from recent sessions or guides users through scenario-based learning, trials, and quizzes for quick onboarding.
Use when creating new protocols, editing existing protocols, or validating protocols work before deployment
Enforces thinking disciplines for rigorous collaborative reasoning: map territory first, name confidence, sit with fog, verify before proposing, genuine agreement/disagreement. Auto-loaded by /figure-out, /define, and similar skills.
Share bugs, ideas, or general feedback.
Instant reference handbook for 10 epistemic protocols. Browse by cluster, look up by command, or find the right protocol for a situation.
Invoke this skill when:
Skip when:
/onboard)/report)/dashboard)| Invocation | Behavior |
|---|---|
/catalog | Overview: 10 protocols grouped by cluster, 1-line each + usage hints |
/catalog {cluster} | Cluster detail: expanded protocol cards with scenarios |
/catalog {command} | Single protocol detail: full card from scenarios.md |
Argument normalization: case-insensitive, accepts /command or bare name (e.g., /catalog clarify = /catalog /clarify = /catalog Hermeneia).
| Protocol | Command | When to Use |
|---|---|---|
| Hermeneia | /clarify | What you said differs from what you meant |
| Telos | /goal | Goal is vague — no success criteria or scope |
| Aitesis | /inquire | Context is insufficient for confident execution |
| Protocol | Command | When to Use |
|---|---|---|
| Prothesis | /frame | No framework — need analytical lenses or multi-perspective team |
| Analogia | /ground | Abstract idea needs concrete domain validation |
| Protocol | Command | When to Use |
|---|---|---|
| Syneidesis | /gap | About to act — potential gaps unexamined |
| Protocol | Command | When to Use |
|---|---|---|
| Prosoche | /attend | Execution risks not yet classified or delegated |
| Protocol | Command | When to Use |
|---|---|---|
| Epharmoge | /contextualize | Output is correct but may not fit the actual context |
| Protocol | Command | When to Use |
|---|---|---|
| Horismos | /bound | Unclear who decides what — ownership boundaries undefined |
| Katalepsis | /grasp | AI did work but you don't fully understand what or why |
When a cluster name or protocol command/name is provided as argument:
Normalize the argument:
/ if presentFor cluster arguments: display all protocol cards in that cluster with expanded "When to Use" descriptions from the tables above.
For protocol arguments: call Read on epistemic-cooperative/skills/onboard/references/scenarios.md, extract the matching ## ProtocolName /command block, and present:
/{command} — direct invocation promptIf no match found: list the closest matches and suggest /catalog for the full overview.
/ prefix; match against both protocol names and commands.