.claude/skills/auto-updater/SKILL.md
Automatically apply improvements to skills and the ecosystem based on system-reviewer findings and best-practices-learner insights. Workflow for automated improvement identification, priority assessment, safe application, validation, and rollback capability. Use when applying systematic improvements, automating enhancement cycles, bulk updating multiple skills, or implementing ecosystem-wide improvements.
npx skillsauth add adaptationio/skrillz auto-updaterInstall 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.
auto-updater automatically applies improvements to skills and ecosystem components based on identified patterns and learnings.
Purpose: Automated application of validated improvements across ecosystem
The 5-Step Auto-Update Workflow:
Safety: Always validates before finalizing, can rollback
Sources:
Output: List of potential improvements
Time: 15-30 minutes
Safe to Automate:
NOT Safe to Automate:
Output: Classified improvements (auto-safe vs manual-only)
Time: 20-40 minutes
Process:
Approach: One skill at a time, validate each before moving to next
Time: Varies by improvement and skill count
For Each Updated Skill:
Output: Validation results per skill
Time: 10-15 minutes per skill
If Validation Fails:
Output: Rolled back skill, failure analysis
Auto-Update: Add Quick Reference to All Skills Missing It
Step 1: Identify
- Improvements: Add Quick Reference section
- Target Skills: planning-architect, task-development, todo-management
- Count: 3 skills to update
Step 2: Assess Safety
- ✅ Safe: Adding new section (doesn't modify existing content)
- ✅ Safe: Standard format (use template)
- ✅ Safe: Low risk (can validate easily)
- Decision: Auto-update approved
Step 3: Apply
- Backup: Git commit all 3 skills
- Apply to planning-architect: ✅ Success
- Apply to task-development: ✅ Success
- Apply to todo-management: ✅ Success
- Changes: 3/3 skills updated
Step 4: Validate
- planning-architect: 5/5 structure (maintained)
- task-development: 5/5 structure (maintained)
- todo-management: 5/5 structure (maintained)
- All validations: ✅ PASS
Step 5: Rollback
- Not needed (all validations passed)
Result: ✅ 3 skills successfully auto-updated
Time: 90 minutes (vs 3-4 hours manual)
Impact: 100% Quick Reference coverage achieved
Quality: All skills maintained 5/5 scores
| Step | Focus | Time | Safety | |------|-------|------|--------| | Identify | Gather improvements | 15-30m | N/A | | Assess Safety | Classify auto-safe | 20-40m | Critical | | Apply | Implement changes | Varies | Backup first | | Validate | Check quality maintained | 10-15m/skill | Essential | | Rollback | Revert if fails | 5m/skill | Safety net |
Safe to Automate:
NOT Safe:
Rule: If requires judgment or understanding → Manual only
auto-updater enables safe, validated, automated improvement application across multiple skills simultaneously.
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.