Sharing Skills

To contribute a skill upstream, create a feature branch, edit the SKILL.md under skills/, commit changes, push to your fork, and open a PR. This enforces a standardized branch-and-PR workflow for safe and reviewable contributions.

The best way to synchronize a fork before opening a PR is to use GitHub CLI to fetch upstream changes, merge them into your local feature branch, resolve any conflicts, and push the updated branch before submitting the skill contribution.

PR metadata improves skill adoption by enforcing consistent documentation and small, well-documented contributions. Standardized metadata ensures contributions are reviewable, reusable, and easily understood by teams coordinating multiple contributors.

Yes, you can use GitHub CLI to open a pull request for a skill contribution directly. The process enforces standard GitHub CLI usage to push your feature branch to a fork and open a PR against the primary upstream repository.

You need to create a feature branch for contributing skills whenever you edit or add a SKILL.md file. This isolates your changes, ensures they are broadly useful, and maintains a safe, reviewable process before merging into the primary upstream repository.

To ensure safe upstream skill contributions, avoid large, undocumented changes. The structured branch-and-PR workflow encourages small, well-documented contributions with consistent PR metadata to improve reuse, adoption, and reviewability.