mcpbeat

Skill Sync

jdrhyne/skill-sync

Sync skills between local installation and the GitHub source-of-truth repository. Use when asked to install, update, list, or push skills.

2k tokens
context cost
the whole folder, loaded on every use
2
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
239
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/jdrhyne/agent-skills --skill skill-sync

The instruction itself

9 sections, as written by the author

Skill Sync

Manage skills from the shared GitHub repository with GitHub as canonical source of truth.

> Never commit secrets. Keep keys/tokens out of SKILL.md and scripts.

Quick Reference

# List available skills in the repo
skill-sync list

# Install one skill
skill-sync install <skill-name>

# Install/update all skills from repo
skill-sync install --all

# Push a local skill update to repo via PR
skill-sync push <skill-name>

# Refresh local repo cache
skill-sync update

Commands

skill-sync list

Shows all skills available in the remote repository.

skill-sync install <name>

Installs/updates a skill from repo into local skills directory.

skill-sync install --all

Installs/updates all skills from repo.

skill-sync push <name>

Pushes local skill changes via branch + PR (gh CLI).

skill-sync update

Pulls latest repo changes without installing.

Configuration

Default paths:

  • Repo clone: ~/.agent-skills-repo
  • Local skills: ~/clawd/skills (or $CLAWD_SKILLS_DIR)
  • Remote: https://github.com/jdrhyne/agent-skills.git

How to use it

Copy the folder

Take jdrhyne/skill-sync from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.