sync-skill-installs

Reinstalls skills from source into global and project installs and verifies parity.

1|Updated Jul 22, 2026
One-click install
npx skills add https://github.com/thititongumpun/skills --skill sync-skill-installs-thititongumpun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-skill-installs
Source: https://github.com/thititongumpun/skills/tree/main/skills/sync-skill-installs
Command: npx skills add https://github.com/thititongumpun/skills --skill sync-skill-installs-thititongumpun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Skills in this repo live in three separate locations (skills/, ~/.agents/skills/, and .agents/skills/) that do not share files, so editing the source alone changes nothing that agents actually load. This Skill performs a complete, verified sync so installs never drift from the source of truth. ## Core Features & Use Cases - Full rsync-based sync: Copies every skill from skills/ into the global install and into project-local installs that already exist, using --delete so removed files disappear everywhere. - Lock file refresh: Recomputes SHA-256 hashes in skills-lock.json so the lock always matches the files on disk. - Drift verification: Diffs every installed copy against the source and reports any DRIFT lines, plus guidance for renames, stale symlinks, and session reloads. - Use Case: After editing a skill's SKILL.md or scripts under skills/, run this sync so both the global and project installs pick up the change, the lock hashes update, and you get confirmation that nothing drifted. ## Quick Start Reinstall the skills from this repo into the global and project installs and verify both match the source.

Frequently Asked Questions about sync-skill-installs

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

FAQPage Schema
How do I sync skill installs after editing a skill?

Run the full sync sequence: clean __pycache__ directories, rsync each skill from skills/ into ~/.agents/skills/ and existing .agents/skills/ copies with --delete, recompute hashes in skills-lock.json, then diff every install against the source to confirm no drift.

Why doesn't editing the skills source directory change what agents load?

Agents load skills from ~/.agents/skills/ (global) and .agents/skills/ (project), which are separate copies that do not share files with the source. Editing skills/ alone changes nothing until an rsync-based sync copies the changes into both installs.

How do I rename an installed skill without leaving stale copies?

A rename requires removing the old directory in every install location, including ~/.agents/skills/old and .agents/skills/old, and repointing the ~/.claude/skills symlink to the new name. Renaming only the source leaves the old skill still loading everywhere.

Why doesn't a new or renamed skill appear in the current session?

The skill registry is read at session start, so renamed or newly added skills are not visible mid-session. Tell the user to run /clear or restart the session for the change to take effect.

What files should not be kept in a skill's assets directory?

Avoid parking customer decks or test fixtures in skills/<name>/assets/, because the sync copies them into both installs and re-copies them on every run. Keep fixtures in a scratch directory outside the skill tree.