skill-shipper

To share Claude Code skills across multiple GitHub repositories, you can publish project-local skills to a central hub using a generated manifest.yaml. This process abstracts repo-specific hardcoding into config-driven artifacts, enabling safe multi-repo propagation with version tracking.

You can install a hub-hosted skill into your current repository using an install mode that validates required configuration placeholders and resolves dependencies. This ensures all external CLI requirements and configuration dependencies are met during the central installation.

Reusable skills break across repositories due to missing dependency declarations, hardcoded project paths, or untracked version changes. You can prevent this by generating a manifest.yaml and applying abstraction checks before publishing the skill.

Yes, you can use Python, pyyaml, and the GitHub CLI to manage skill version updates. An update mode propagates new hub versions into existing local skills with preview and approval workflows, applying major-version caution to prevent breaking changes.

The best way to track skill versions across repos is to use a central hub with manifest.yaml validation and mode-based operations. This approach provides update propagation with safety gates and major-version caution to prevent breaking changes.

Yes, a manifest.yaml file is required to publish a skill to a central hub. The publishing process includes manifest generation and validation to ensure safe cross-repo propagation and proper dependency resolution.