Stats
Actions
Tags
How this skill is triggered — by the user, by Claude, or both
Slash command
/skills-sync:sync-guidanceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When the user asks about syncing, backing up, transferring, or sharing Claude Code skills across devices, guide them through the skills-sync plugin commands:
When the user asks about syncing, backing up, transferring, or sharing Claude Code skills across devices, guide them through the skills-sync plugin commands:
/skills-sync:setup to configure a GitHub repo for storing skills/skills-sync:push --all to upload all local skills to GitHub/skills-sync:setup then /skills-sync:pull --all/skills-sync:setup [repo-name] - Configure the GitHub repository/skills-sync:list [local|remote|all] - See what skills exist where/skills-sync:status - Check configuration and sync status/skills-sync:diff [skill-name] - Compare local vs remote versions/skills-sync:push [skill-name|--all] - Upload skills to GitHub/skills-sync:pull [skill-name|--all] [--force] - Download skills from GitHubgh CLI installed and authenticated (gh auth login)Skills are stored in a GitHub repository using the GitHub Contents API via the gh CLI. Each skill is a directory containing a SKILL.md file and optional supporting files. The plugin tracks sync state locally to detect conflicts and show sync status.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub jialiangfan/skills-sync --plugin skills-sync