manage-skills

Shares skill directories across projects via hardlinks with sync and integrity checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding tools load skills from per-project directories, so the same skill gets copied into dozens of projects, copies drift apart, and nobody knows which version is current. This Skill manages a single source of truth per skill and hardlinks the whole directory into every project that needs it. ## Core Features & Use Cases - Hardlink-based linking and syncing: link, unlink, sync, and check commands keep every project's skill directory on the same inode as its source, while Git still sees normal committable files. - Multi-source and remote sources: Register local directories or GitHub repos as prioritized sources, fetch updates with update, and inspect everything with locations and list. - Safe editing guidance and repair: Documents which editors break hardlink inodes, how to edit in place with shell redirects, and how to repair broken link chains. - Use Case: After cloning a project, run manage-skills sync to re-establish hardlinks, then manage-skills check to verify every linked skill matches its source of truth. ## Quick Start Ask the AI to run manage-skills list to show available skills, then link the ones this project needs and verify them with manage-skills check.

Frequently Asked Questions about manage-skills

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

FAQPage Schema
How do I share the same skill across multiple projects?▼

Register a source directory with manage-skills sources add, then run manage-skills link <skill> inside each project. The whole skill directory is hardlinked from the source, so edits in one place appear everywhere on your machine.

How do I sync skills after cloning a repository?▼

Run manage-skills sync in the cloned project. It re-establishes hardlinks for committed skill copies that match a source, while diverged copies are kept and reported unless you pass --force.

Why do hardlinked skill files break when I edit them?▼

Editors and AI Write/Edit tools that rewrite-and-replace create a new inode, silently detaching the file from every other linked copy. Edit with shell redirects like cat > file, which truncate and write in place, preserving the inode.

Does manage-skills work with Codex as well as Claude Code?▼

Yes. A second target codex:.agents/skills:SKILL.md is configured by default, and manage-skills link <skill> --target codex links the same source into the Codex skills directory. Under Codex the script is invoked by path since plugins cannot modify PATH.

Can I use a GitHub repository as a skill source?▼

Yes. Run manage-skills sources add github:owner/repo, or just the owner name to resolve their skills repo. manage-skills update fetches changes and writes them in place so existing hardlinks keep working.

How do I repair a broken hardlink chain?▼

Find paths sharing the old inode with find -inum, copy the new content into one old path to preserve that inode, then remove the new path and relink it with ln. Verify with stat that inode and link count match across all paths.