Sharing Skills FAQs

Question 1

When should I share a skill versus keeping it personal?

Accepted Answer

You should share a skill when it is broadly useful, well-tested, and doesn't contain sensitive information. Keep skills personal if they are specific to a single organization, experimental, or too niche for the general community.

Question 2

How does this skill improve my development workflow?

Accepted Answer

It eliminates manual errors in the Git process by providing a step-by-step workflow. It ensures your contributions meet project standards by providing automated templates for commit messages and PR descriptions, making merge approval more likely.

Question 3

Can I contribute multiple skills at once?

Accepted Answer

The skill enforces a 'one skill per PR' rule. Each skill should have its own feature branch and pull request so that maintainers can review, test, and merge them independently without causing conflicts.

Question 4

What does the Sharing Skills capability do?

Accepted Answer

Sharing Skills automates and guides the technical process of contributing your custom Claude Code skills to upstream repositories. It handles the complexities of branching, syncing with upstream, and using the GitHub CLI to generate standardized pull requests.

Question 5

What are the prerequisites for using this skill?

Accepted Answer

You must have the GitHub CLI (gh) installed and authenticated. Additionally, your local skill should be stored in the standard directory (~/.config/superpowers/skills/) and must have been verified using the writing-skills TDD process.

Sharing Skills

Sharing Skills

Key Features

Use Cases

Key Features

Use Cases