manage-skills-drift-triage

Audit and triage content drift across hardlinked skill copies in multiple repositories.

12|5|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/Getty/manage-skills --skill manage-skills-drift-triage-getty
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manage-skills-drift-triage
Source: https://github.com/Getty/manage-skills/tree/main/.claude/skills/manage-skills-drift-triage
Command: npx skills add https://github.com/Getty/manage-skills --skill manage-skills-drift-triage-getty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When the same skill name exists in many projects, copies drift apart: hardlinked files get rewritten into new inodes, one-time copies never sync, and priority shadowing hides stale versions. This Skill provides the audit commands and decision tree to find that drift across repos and decide what to do with each diverged copy. ## Core Features & Use Cases - Cross-repo drift detection: Group every .claude/skills/*/SKILL.md by name, inode, and content hash using find, stat, diff, and a Perl whole-tree sweep to locate identical-but-unlinked or genuinely diverged copies. - Triage decision tree: Distinguish harmless inode splits, pure staleness, upstream-worthy improvements, project-specific customizations, and shadowed sources, with the correct fix for each (relink, fold upstream, rename to a project-prefixed skill, or reorder sources). - Systemic gap repair: Register missing source directories with manage-skills sources add and verify winners with manage-skills locations so drift does not reappear. - Use Case: After noticing a project's skill copy never updates, run the inode/hash audit across ~/dev, discover a one-time copy that diverged, diff it against the master, and relink it after confirming the differences are pure staleness. ## Quick Start Ask the AI to audit all projects under ~/dev for drifted copies of a given skill name and triage any differing versions using the decision tree.

Frequently Asked Questions about manage-skills-drift-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find drifted skill copies across multiple git repositories?▼

Find every .claude/skills directory, then group SKILL.md files by skill name, inode, and content hash. Same hash with different inodes means relink them; different hashes mean real drift requiring the triage decision tree.

Why does my hardlinked SKILL.md stop syncing after editing it?▼

Edit and Write tools rewrite-and-replace the file, creating a new inode for the edited path while other paths keep the old inode and stale content. Use cat > file to edit in place, then relink the split copies.

What should I do when a local skill copy has different content than the master?▼

Diff first. If the local copy is a strict subset of the master, relink directly. If it contains generally useful changes, fold them into the master first. If differences are project-specific, rename it to a project-prefixed skill and leave it unlinked.

Can I hardlink any two identical files like LICENSE or .gitignore?▼

No. Only link files meant to be one file, such as .claude/skills, agents, or rules governed by a source of truth. Linking coincidentally identical files means a later single-project edit silently changes every other project.

Why does manage-skills check exit 1 with no findings?▼

That indicates a stale copy of the tool, not a broken project. Older versions aborted on the first project-owned original skill due to a pipefail and grep interaction; update the tool and rerun check.