Track improve
Skill onfire7777/universal-ai-skills-library/skills/track-improve
Router-first AI skill system for Codex, Claude, Cursor, Hermes, Paperclip, OpenCode, and local AI stacks: search, preflight-route, and load 1,812 skills on demand without duplicating the corpus.
npx -y skills add onfire7777/universal-ai-skills-library --skill track-improveAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Track mistakes and improvement opportunities with 5-whys root cause analysis. Use when Claude makes an error, gives a wrong answer, misunderstands intent, or when you spot a pattern worth capturing. Triggers on: 'track this mistake', 'log this issue', 'remember this for next time', 'you keep doing this', 'improvement opportunity', 'track improvement', 'what went wrong'.
SKILL.md
1.7 KB, as published. Nobody here has run it
Track & Improve
Capture mistakes and improvement opportunities with root cause analysis.
Track a Mistake or Improvement
When invoked:
- Extract the description of what went wrong
- Identify what persona/role was active
- Perform 5 whys root cause analysis
- Extract last 5 message exchanges for context
- Create a report in
~/.claude/trk-db/active/with format:
---
id: YYYY-MM-DD-HH-MM-SS
created: ISO8601 timestamp
project: current project name
status: active
category: rule-violation|improvement|confusion
---
# [Description]
## 5 Whys Analysis
1. **Why did this happen?** [Analysis]
2. **Why?** [Analysis]
3. **Why?** [Analysis]
4. **Why?** [Analysis]
5. **Root cause:** [Conclusion]
## Context (Last 5 Messages)
[Extracted conversation]
## Resolution
[Empty - filled when resolved]
- Git add and commit
Review Reports
Read all files from ~/.claude/trk-db/active/, present organized by recency and category, discuss patterns.
Resolve a Report
Move from active/ to resolved/, fill in resolution, git commit.
Rules
🚨 The 5 whys must be genuine root cause analysis, not surface restating. 🚨 Category must accurately reflect whether it's a rule violation, improvement idea, or confusion. 🚨 Reports are tracked in git for history and pattern analysis.