Help us improve
Share bugs, ideas, or general feedback.
From interknow
Knowledge Compounding (deprecated — use /clavain:compound)
npx claudepluginhub mistakeknot/interagency-marketplace --plugin interknowHow this skill is triggered — by the user, by Claude, or both
Slash command
/interknow:compoundThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Deprecated:** Knowledge entries have been converged into `docs/solutions/`. Use `/clavain:compound` instead, which writes to `docs/solutions/` with enum-validated schema and provenance tracking.
Capture knowledge — solutions, context docs, learnings, and principles. Use after fixing non-trivial bugs, creating context for AI, or discovering patterns worth preserving. Triggers: compound, document solution, capture fix, save solution, knowledge compound, document this, save this fix, context, create context, update context, build context, learn, save learning, remember this.
Captures solved problems as structured JSONL knowledge entries for fast recall in future sessions. Automatically activates after bug fixes or when a solution should be preserved.
Extracts patterns, quirks, and decisions from conversations; persists to Markdown files in knowledge/learnings/. Use /learn for quick or /learn --deep for thorough analysis.
Share bugs, ideas, or general feedback.
Deprecated: Knowledge entries have been converged into
docs/solutions/. Use/clavain:compoundinstead, which writes todocs/solutions/with enum-validated schema and provenance tracking.
Extract durable patterns from review findings and save them as knowledge entries.
After a flux-drive review completes, or when you discover a reusable pattern worth preserving across sessions.
Preferred: Use /clavain:compound instead — it writes to docs/solutions/ with the converged schema (compound docs format + interknow provenance fields).
Provide either:
For each finding, decide: compound or skip?
Compound (save as knowledge entry) when the finding is:
Skip when:
Write markdown files to ${CLAUDE_PLUGIN_ROOT}/config/knowledge/:
Filename: {short-kebab-case-description}.md
---
lastConfirmed: {today's date YYYY-MM-DD}
provenance: independent
---
{1-3 sentence finding description, phrased as a generalizable heuristic}
Evidence: {file paths, symbol names, line ranges from the review}
Verify: {1-3 concrete steps to confirm this finding is still valid}
If intersense is available, detect the project domain and include it in the finding description. This helps future retrieval prioritize domain-relevant knowledge.
provenance: independentlastConfirmed, set provenance: independentlastConfirmedBefore writing ANY entry:
Good: "Auth middleware often swallows context cancellation errors" Bad: "auth.go:47 in ProjectX has a bug"
After compounding, scan existing entries:
lastConfirmed dateconfig/knowledge/archive/Compounding is best-effort. If it fails, the review/session is still complete.