sharing-skills

Contribute locally developed skills to an upstream repository via pull requests.

3|Updated Nov 19, 2025
One-click install
npx skills add https://github.com/seanGSISG/crispy-claude --skill sharing-skills-seangsisg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/seanGSISG/crispy-claude/tree/main/.claude/skills/sharing-skills
Command: npx skills add https://github.com/seanGSISG/crispy-claude --skill sharing-skills-seangsisg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Contributing valuable, broadly applicable skills back to a central repository can be complex, involving specific Git workflows and PR creation steps. This skill simplifies the process, ensuring proper contribution.

Core Features & Use Cases

  • Streamlined Contribution: Guides through the entire workflow: branching, creating/editing skills, committing, pushing to a fork, and creating a pull request.
  • Quality Assurance: Emphasizes prerequisites like skill testing using TDD, ensuring high-quality contributions.
  • Troubleshooting: Provides common solutions for Git and GitHub CLI issues during the contribution process.

Quick Start

Use the sharing-skills skill to contribute my new 'code-refactoring' skill to 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 contribute a skill to the upstream repository using Git and GitHub?

Contributing a skill involves creating a branch, writing or editing your skill under skills/<category>/<skill-name>/SKILL.md, committing changes, pushing to a fork, and opening a pull request via GitHub CLI. The process ensures your contribution follows community guidelines and quality standards.

What prerequisites do I need before sharing a skill back to the repository?

You need the GitHub CLI (gh) installed, a locally configured skills repository at ~/.config/superpowers/skills/, and a tested, documented skill that follows writing guidelines. Your skill must be well-tested using TDD and broadly useful to the community.

How do I ensure my skill contribution meets quality standards?

Test your skill thoroughly using test-driven development (TDD) before submission, document it comprehensively, follow the branch naming and PR formatting steps outlined in the guidelines, and ensure it solves a broadly applicable problem that benefits other users.

Can I use this workflow for any type of skill contribution?

Yes, this workflow applies to any skill that is broadly useful, represents a reusable pattern or technique, is well-tested and documented, and aligns with community writing standards. Skills must solve problems that extend beyond a single use case.

What should I do if I encounter Git or GitHub CLI errors during contribution?

The skill provides troubleshooting guidance for common Git and GitHub CLI issues that arise during the contribution workflow. Consult the documented solutions for push failures, PR creation problems, or branch management conflicts.