From communitytools
Identifies and removes orphaned, unreferenced, or redundant skill content after quarterly maintenance or linter flags. Inverse of /skill-update.
How this skill is triggered — by the user, by Claude, or both
Slash command
/communitytools:skill-pruneThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Inverse of `/skill-update`. Removes content rather than adding it. Run during quarterly maintenance, after engagements, or when `scripts/skill_linter.py` reports orphans / duplicates.
Inverse of /skill-update. Removes content rather than adding it. Run during quarterly maintenance, after engagements, or when scripts/skill_linter.py reports orphans / duplicates.
scripts/skill_linter.py --check-orphans reports orphan reference files.A reference / scenario / line is a prune candidate when it satisfies any of:
attack-chain.md of runs that ended status=BLOCKED, never in a successful chain.Removing content fails any of these → keep it.
<!-- KEEP: <reason> --> annotation.OUTPUT_DIR/attack-chain.md.scripts/skill_linter.py --check-orphans to surface orphans.scripts/skill_linter.py to confirm the change broke no other links and didn't reintroduce duplicates.Concise change report:
npx claudepluginhub transilienceai/communitytoolsMarks outdated grimoire skills for deprecation when the referenced tool no longer exists, a practice is superseded, or the skill fails review criteria.
Discovers all project skills via file search, analyzes for overlaps and weaknesses, classifies for refactor/merge/delete, executes refactoring plan, extracts conventions, validates, and reports.
Refines existing SKILL.md content: updates procedure steps, expands Common Pitfalls, synchronizes Related Skills, and bumps version. Use when procedures are vague, references are stale, or feedback indicates gaps.