sharing skills

Contribute skills from your local branch back to the upstream repository.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "sharing skills" with this command: npx skills add obra/superpowers-skills/obra-superpowers-skills-sharing-skills

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 skills/meta/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)

  • Skill has been tested (see skills/meta/writing-skills for TDD process)

Sharing Workflow

  1. Ensure You're on Main and Synced

cd ~/.config/superpowers/skills/ git checkout main git pull upstream main git push origin main # Push to your fork

  1. Create Feature Branch

Branch name: add-skillname-skill

skill_name="your-skill-name" git checkout -b "add-${skill_name}-skill"

  1. Create or Edit Skill

Work on your skill in skills/

Create new skill or edit existing one

Skill should be in skills/category/skill-name/SKILL.md

  1. Commit Changes

Add and commit

git add skills/your-skill-name/ git commit -m "Add ${skill_name} skill

$(cat <<'EOF' Brief description of what this skill does and why it's useful.

Tested with: [describe testing approach] EOF )"

  1. Push to Your Fork

git push -u origin "add-${skill_name}-skill"

  1. Create Pull Request

Create PR to upstream using gh CLI

gh pr create
--repo upstream-org/upstream-repo
--title "Add ${skill_name} skill"
--body "$(cat <<'EOF'

Summary

Brief description of the skill and what problem it solves.

Testing

Describe how you tested this skill (pressure scenarios, baseline tests, etc.).

Context

Any additional context about why this skill is needed and how it should be used. EOF )"

Complete Example

Here's a complete example of sharing a skill called "async-patterns":

1. Sync with upstream

cd ~/.config/superpowers/skills/ git checkout main git pull upstream main git push origin main

2. Create branch

git checkout -b "add-async-patterns-skill"

3. Create/edit the skill

(Work on skills/async-patterns/SKILL.md)

4. Commit

git add skills/async-patterns/ git commit -m "Add async-patterns skill

Patterns for handling asynchronous operations in tests and application code.

Tested with: Multiple pressure scenarios testing agent compliance."

5. Push

git push -u origin "add-async-patterns-skill"

6. Create PR

gh pr create
--repo upstream-org/upstream-repo
--title "Add async-patterns skill"
--body "## Summary Patterns for handling asynchronous operations correctly in tests and application code.

Testing

Tested with multiple application scenarios. Agents successfully apply patterns to new code.

Context

Addresses common async pitfalls like race conditions, improper error handling, and timing issues."

After PR is Merged

Once your PR is merged:

  • Sync your local main branch:

cd ~/.config/superpowers/skills/ git checkout main git pull upstream main git push origin main

  • Delete the feature branch:

git branch -d "add-${skill_name}-skill" git push origin --delete "add-${skill_name}-skill"

Troubleshooting

"gh: command not found"

"Permission denied (publickey)"

"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

  • skills/meta/writing-skills - How to create well-tested skills

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Repository SourceNeeds Review
85.6K31.1K
obra
General

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Repository SourceNeeds Review
85.6K24.3K
obra
General

verification-before-completion

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Repository SourceNeeds Review
85.6K18.7K
obra