Distribute a Skill Across All Agents

When to Use

• Use when a skill should be made available across multiple local agent skill folders.
• Use when the user asks to sync or distribute skill updates to other agents.

Discover actual host locations

The upstream author used ~/.agents/skills, ~/.claude/skills, ~/.pi/agent/skills and ~/.hermes/skills. These are candidate paths, not facts about this user’s machine or discovery precedence. Inspect only authorized configured hosts and their documented skill paths; do not create an absent host or replace a real directory with a symlink merely to match the upstream layout.

Workflow

1. Identify the canonical reviewed source and exact target hosts from the user’s request. Read the entire skill tree and preserve bundled files, attribution and license.
2. Inspect each destination with ls -ld and resolve links. Record source and destination real paths; skip aliases of the same tree and reject unexpected links outside the authorized location.
3. Back up an existing independent target privately. Preview a file-level diff, including deletions and modes; resolve local divergence before overwriting. Validate the skill ID as one directory name and quote paths.
4. Copy only the selected tree to the authorized independent destination. When removal of obsolete files is necessary, preview deletion with a dry run before applying; never use a broad global rsync --delete target.
5. Compare relative file lists and cryptographic content hashes for every file, plus relevant modes and links. Equal SKILL.md byte counts do not prove tree equality or a correct symlink.
6. Verify discovery through each host’s actual mechanism. Report installed bytes separately from a running session reload; reload only the authorized host when required and preserve unrelated sessions.