Agent skill · writing content · aiskillstore
sharing-skills
Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository
Why this skill is useful
Codifies the process of contributing skills to an upstream repository, which the AI could infer but now has a clear standard to follow.
What it needs
Requires gh installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Sharing Skills Overview Contribute skills from your local branch back to the upstream repository. Workflow: Branch → Edit/Create skill → Commit → Push → PR When to Share Share when: Skill applies broadly (not project-specific) Pattern/technique others would benefit from Well-tested and documented Follows writing-skills guidelines Keep personal when: Project-specific or organization-specific Experimental or unstable Contains sensitive information Too narrow/niche for general use Prerequisites gh CLI installed and authenticated Working directory is ~/.config/superpowers/skills/ (your local clone) REQUIRED: Skill has been tested using writing-skills TDD process Sharing Workflow 1. Ensure You're on Main and Synced 2. Create Feature Branch 3. Create or Edit Skill 4. Commit Changes 5. Push to Your Fork 6. Create Pull Request Complete Example Here's a complete example of sharing a skill called "async-patterns": After PR is Merged Once your PR is merged: 1. Sync your local main branch: 2. Delete the feature branch: Troubleshooting "gh: command not found" Install GitHub CLI: https://cli.github.com/ Authenticate: gh auth login "Permission denied (publickey)" Check SSH keys: gh auth status Set up SSH: https://docs.github.com/en/authentication "Skill already exists" You're creating a modified version Consider different skill name or coordinate with the skill's maintainer PR merge conflicts Rebase on latest upstream: git fetch upstream && git rebase upstream/main Resolve conflicts Force push: git push -f origin your-branch Multi-Skill Contributions Do NOT batch multiple skills in one PR. Each skill should: Have its own feature branch Have its own PR Be independently reviewable Why? Individual skills can be reviewed, iterated, and merged independently. Related Skills writing-skills - REQUIRED: How to create well-tested skills before sharing
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/sharing-skills