claude:sync-skills

To share local Claude Code skills to a GitHub repository, you can automatically discover, select, and commit skills from your `.claude/skills/` directory to a designated remote repository, updating the central `README.md` index for cross-project reusability.

Generating an index of available skills in a remote Git repository involves automatically updating the `README.md` file with a catalog of all available skills during the synchronization process, creating a centralized reference for all pushed local skills.

Yes, you need the GitHub CLI installed to sync skills to a remote repository because it handles the required authentication, and Git is also necessary for the version control operations like cloning, copying, and pushing selected skills.

Yes, you can interactively select which local skills to push to your shared GitHub repository. The synchronization process automatically finds skills in your `.claude/skills/` directory and allows interactive selection before committing them.

Skill synchronization handles existing files by cloning the target GitHub repository locally first, then copying and committing the selected skills, and finally updating the `README.md` index before pushing the changes back to the remote.

A limitation of using Git version control to sync local skills is that it strictly requires both Git and GitHub CLI environments, meaning any authentication failures or repository access issues will block the synchronization process.