From compound-knowledge
Persists feedback on knowledge capture/retrieval behaviors across sessions. Triggers on corrections ('don't capture that', 'wrong category') or commands ('save feedback', 'show feedback', 'clear', 'consolidate').
npx claudepluginhub joshuaoliphant/claude-plugins --plugin compound-knowledgeThis skill uses the workspace's default tool permissions.
Persist feedback about knowledge capture and retrieval across sessions. Stored feedback is automatically
Use when completing any meaningful task - distill patterns, lessons, and insights from the interaction and persist them for future sessions
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 patterns, decisions, gotchas, procedures, and feature knowledge from conversations into durable skills for on-demand reuse. Invoked via /learn or 'please remember'.
Share bugs, ideas, or general feedback.
Persist feedback about knowledge capture and retrieval across sessions. Stored feedback is automatically loaded when compound-capture or compound-retrieve runs, ensuring corrections are never repeated.
When the user provides feedback on capture or retrieval behavior, save it:
echo '{"category": "<category>", "feedback": "<what the user said>", "context": "<optional context>"}' | \
python ${PLUGIN_ROOT}/scripts/feedback_manager.py compound-knowledge save-feedback
Categories: capture_format, categorization, triviality_threshold, cross_references, retrieval_depth, principle_style, general
Examples:
{"category": "triviality_threshold", "feedback": "Raise the bar — only capture solutions that required multiple investigation steps"}{"category": "capture_format", "feedback": "Include inline code examples in the solution body, not just descriptions"}{"category": "categorization", "feedback": "Design patterns belong in patterns/, even if discovered during debugging"}{"category": "retrieval_depth", "feedback": "Return top 5-7 results instead of top 3 when searching solutions"}{"category": "principle_style", "feedback": "Keep principle statements to one sentence maximum"}Display all stored feedback:
python ${PLUGIN_ROOT}/scripts/feedback_manager.py compound-knowledge show-feedback
Present as a readable list grouped by category.
Clear all feedback or feedback for a specific category:
# Clear all
python ${PLUGIN_ROOT}/scripts/feedback_manager.py compound-knowledge clear-feedback
# Clear only categorization feedback
python ${PLUGIN_ROOT}/scripts/feedback_manager.py compound-knowledge clear-feedback categorization
Graduate stable feedback into the actual SKILL.md files, making corrections permanent. This is a Claude-driven operation — no script needed.
When to consolidate: When the user says "update the plugin based on feedback", "consolidate feedback", "bake in my preferences", or "graduate feedback into the skill".
Process:
python ${PLUGIN_ROOT}/scripts/feedback_manager.py compound-knowledge show-feedback
Read the target SKILL.md files that the feedback applies to:
${PLUGIN_ROOT}/skills/compound-capture/SKILL.md${PLUGIN_ROOT}/skills/compound-retrieve/SKILL.mdFor each feedback entry, determine if it should be consolidated:
Present a consolidation plan to the user:
## Consolidation Plan
**Will bake into SKILL.md** (permanent):
- [feedback] → edit [file]: [what will change]
**Will keep as runtime feedback** (situational):
- [feedback] → reason: [why it stays runtime]
Proceed?
On approval:
python ${PLUGIN_ROOT}/scripts/feedback_manager.py compound-knowledge clear-feedback <category>
Report what changed and what remains as runtime feedback.
When compound-capture runs, it loads all feedback entries and applies them:
When compound-retrieve runs, it loads retrieval-related feedback:
This ensures the user never has to repeat the same correction twice.