2.2 KiB
2.2 KiB
Troubleshooting Guide
No insights found
Symptoms: Phase 1 reports 0 insights
Solution:
- Verify
docs/lessons-learned/exists in project - Check for alternative locations (ask user)
- Verify insights were actually generated by extract-explanatory-insights hook
- Check file naming pattern matches YYYY-MM-DD-*.md
Prevention: Set up extract-explanatory-insights hook if not already configured
All insights cluster into one giant skill
Symptoms: Phase 2 creates one cluster with 10+ insights
Solution:
- Increase clustering threshold (e.g., 0.6 → 0.7)
- Enable sub-clustering (split by sub-topics or time periods)
- Manually split cluster in Phase 2 user review
- Create mode-based skill with different modes for different sub-topics
Prevention: Tune clustering-config.yaml thresholds for your domain
Generated skill doesn't load
Symptoms: Skill not recognized by Claude Code after installation
Solution:
- Check YAML frontmatter syntax (no tabs, proper dashes)
- Verify name field is lowercase kebab-case
- Check description doesn't contain special characters that break parsing
- Restart Claude Code session
- Check skill file permissions (should be readable)
Prevention: Always run validation in Phase 4 before installation
Trigger phrases don't activate skill
Symptoms: Using trigger phrase doesn't invoke the skill
Solution:
- Make trigger phrases more specific (avoid overly generic phrases)
- Include domain keywords in trigger phrases
- Add "PROACTIVELY when" to description for auto-triggering
- Try exact phrase match vs. semantic match
- Check for conflicts with built-in commands or other skills
Prevention: Test trigger phrases in Phase 5 before finalizing
Generated content quality is low
Symptoms: SKILL.md is vague, missing details, or poorly organized
Solution:
- Check insight quality (garbage in, garbage out)
- Manually edit SKILL.md to improve clarity
- Add more examples and context
- Reorganize sections for better flow
- Iterate to version 0.2.0 with improvements
Prevention: Filter low-quality insights in Phase 2, prioritize insights with clear action items