Smithery is now a part of Arcade.dev! Read more in our announcement here
Use this skill when you want to learn about generating high-quality insights that will be automatically captured...
This skill guides you on creating valuable insights that will be automatically captured by hooks. You don't need to manually save insights - just generate them in the ā
Insight format and the Stop/SubagentStop hooks will extract them from the transcript.
1. You generate: ā
Insight āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
[valuable knowledge]
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
2. Hook automatically:
- Parses transcript after your response
- Extracts content between markers
- Saves to ~/.claude/knowledge-extraction/{session-id}/insights.md
- Tracks state to avoid duplicates
Generate ā
Insight markers when you discover:
| Type | Description | Example |
|---|---|---|
code-pattern |
Reusable patterns | "Prefer useReducer for complex form state" |
workflow |
Efficient processes | "Run tests before commit hooks" |
debugging |
Root cause findings | "Memory leak caused by unclosed listener" |
architecture |
Design decisions | "Use event sourcing for audit trail" |
tool-usage |
Effective techniques | "Combine Grep + Read for targeted searches" |
standard |
Standards and conventions | "JSON files use 2-space indentation" |
convention |
Naming and file patterns | "Scripts follow entity-action.js naming" |
Use the standard format for automatic extraction:
ā
Insight āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
[2-5 lines of valuable, reusable knowledge]
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
After insights accumulate:
/insights - View collected insights/insights extract - Convert to Skills/Commands/CLAUDE.md/Rules Files/insights clear - Clear session insights