sharing-skills

Create branches, edit skills, and submit PRs to upstream repositories.

60|4|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/dsifry/goodtogo --skill sharing-skills-dsifry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/dsifry/goodtogo/tree/main/.claude/plugins/superpowers/skills/sharing-skills
Command: npx skills add https://github.com/dsifry/goodtogo --skill sharing-skills-dsifry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers contribute broadly useful skills from their local branch back to the upstream repository, enabling reuse and collaboration across projects.

Core Features & Use Cases

  • Guided sharing workflow: Branch, edit/create skill, commit, push, and open a PR to upstream.
  • Prerequisites and best practices: Install the gh CLI, ensure your local skills directory is set up, and test skills using the writing-skills TDD process.
  • Use Case: If you build a general-purpose skill (not project-specific), share it upstream to help others reuse and contribute back.

Quick Start

Use the sharing-skills workflow to contribute a new skill: create/edit the skill under skills/, commit with a descriptive message, push to your fork, and open a PR against the upstream repository.

Frequently Asked Questions about sharing-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share a useful skill upstream via a pull request?

To share a skill upstream, create a local branch, edit or add the skill under your skills directory, commit changes, push to your fork, and open a pull request against the upstream repository using the gh CLI.

What do I need to contribute a skill back to the upstream repository?

Contributing a skill requires installing the gh CLI and configuring your local skills directory at ~/.config/superpowers/skills/ before branching and submitting a pull request to the upstream repository.

When should I share a local skill upstream for collaboration?

Share a skill upstream when it is broadly useful and general-purpose rather than project-specific, enabling reuse and collaboration across projects through the upstream pull request workflow.

Do I need to test skills before opening a pull request upstream?

Yes, skills must be tested using the writing-skills TDD process before opening an upstream pull request to ensure they function correctly and meet repository collaboration standards.

What is the git workflow for contributing skills to an upstream repository?

The git workflow involves creating a branch, editing the skill in the local skills directory, committing with a descriptive message, pushing to your fork, and opening a pull request to upstream via the gh CLI.