gcp-custom-skills-sync

Mirror the custom skill directories from the active skills folder into the local git clone using rsync, then run git add, commit, and push from the clone directory. This uploads the skills to the private GitHub repository for versioned backup.

Create a new directory under the active skills folder, add a SKILL.md file with YAML frontmatter containing name and description, then mirror it to the local git clone and push the changes to GitHub following the standard sync workflow.

No, the git tracking model only covers custom, unique, non-bundled skills. Standard system or bundled skills that exist as symlinks are automatically ignored and never copied into the repository.

Symlinked skills point to standard system or bundled resources that already exist elsewhere, so copying them would duplicate content and pollute the repository. Only real custom skill directories are mirrored with rsync.

The workflow uses hardcoded local paths and a single private repository, so it only works on the configured machine. It also requires manual execution of rsync and git commands rather than running automatically on every skill change.