sharing-skills

Packaging a skill for sharing involves structuring it in your local skills directory, creating clear SKILL.md documentation, testing it using the TDD process, and creating a pull request to the upstream repository. The sharing-skills workflow guides you through branching, documentation, testing notes, and PR submission via the gh CLI.

You need a local clone at ~/.config/superpowers/skills/, an authenticated gh CLI, a synced main branch with the upstream repository, and completed testing per the writing-skills TDD process. Your skill must be generally useful, well-tested, and well-documented, not project-specific.

Edit the SKILL.md file placed under skills/category/skill-name/ with clear instructions, use cases, and implementation details. The sharing-skills workflow enforces structured documentation placement and PR rendering with a consistent body format for discovery and usability.

Shared skills should be generally useful and applicable across your organization, not tied to a single project. The sharing-skills process filters for broadly beneficial, well-tested skills that standardize practices and accelerate development across teams.

You must test your skill following the writing-skills TDD process and include testing notes in your commit. The sharing-skills workflow enforces per-skill branch testing and structured commit messages to ensure quality before PR submission.

Create a feature branch, edit and test your SKILL.md, commit with testing notes, push to your fork, and use the gh CLI to create a pull request. The sharing-skills workflow automates this per-skill branch process with structured PR rendering for team review.