.claude/skills/skill-evolution-tracker/SKILL.md
Track skill changes, improvements, and evolution over time. Task-based operations for version tracking, change documentation, impact measurement, and evolution analysis. Use when tracking skill versions, documenting changes over time, measuring improvement impact, or analyzing how skills evolved.
npx skillsauth add adaptationio/skrillz skill-evolution-trackerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
skill-evolution-tracker documents and analyzes how skills change and improve over time, providing visibility into evolution patterns and improvement effectiveness.
Purpose: Track and understand skill evolution for continuous improvement insights
The 4 Tracking Operations:
Purpose: Maintain version history for skills
Process:
Format:
## Version History
### v1.1 (2025-11-07)
- Added Quick Reference section
- Enhanced examples in Operations
- Fixed validation criteria
### v1.0 (2025-10-15)
- Initial release
Purpose: Record what changed, why, and impact
Process:
Format:
### Change: Added Quick Reference
**Rationale**: User experience improvement, easier memory refresh
**Changes**: Added Quick Reference section (96 lines)
**Impact**: Improved usability, 100% Quick Ref coverage
**Validation**: Passed structure validation, Quick Ref detected
Purpose: Quantify effectiveness of improvements
Metrics:
Example:
Impact Measurement: Quick Reference Addition
Before:
- Quick Reference: 4 of 7 skills (57%)
- User feedback: "Hard to refresh memory"
After:
- Quick Reference: 7 of 7 skills (100%)
- Validation: All pass Quick Ref check
- Impact: Improved UX, consistency
Quantified:
- Coverage: 57% → 100% (+43%)
- Time to refresh: ~30min → ~5min (-83%)
Purpose: Identify patterns in skill evolution
Process:
Example Patterns:
| Operation | Focus | Output | |-----------|-------|--------| | Version Tracking | Version numbers, changelog | Version history | | Change Documentation | What/why/impact of changes | Change log | | Impact Measurement | Quantify improvements | Metrics, evidence | | Evolution Analysis | Patterns across skills | Meta-learnings |
Integration: best-practices-learner (uses evolution insights for learnings)
skill-evolution-tracker provides visibility into how skills improve over time, enabling data-driven understanding of what makes skills better.
development
Setup secure web-based terminal access to WSL2 from mobile/tablet via ttyd + ngrok/Cloudflare/Tailscale. One-command install, start, stop, status. Use when you need remote terminal access, web terminal, browser-based shell, or mobile access to WSL2 environment.
development
Complete development workflows where Claude writes the code while Gemini and Codex provide research, planning, reviews, and different perspectives. Claude remains the main developer. Use for complex projects requiring expert planning and multi-perspective reviews.
development
Systematic progress tracking for skill development. Manages task states (pending/in_progress/completed), updates in real-time, reports progress, identifies blockers, and maintains momentum. Use when tracking skill development, coordinating work, or reporting progress.
testing
Comprehensive testing workflow orchestrating functional testing, example validation, integration testing, and usability assessment. Sequential workflow for complete skill testing from examples through scenarios to integration validation. Use when conducting thorough testing, pre-deployment validation, ensuring skill functionality, or comprehensive quality checks.