What tools are required to use the sharing-skills workflow?

You must have the GitHub (gh) CLI installed and authenticated, and your working directory must be a local clone of the skills repository.

When should I keep a skill personal instead of sharing it?

You should keep skills personal if they are project-specific, contain sensitive information, are experimental/unstable, or are too niche for general community use.

Can I submit multiple skills in a single pull request?

No, each skill should have its own feature branch and its own PR to ensure they can be reviewed, iterated, and merged independently.

What do I do after my pull request is merged?

Once merged, you should sync your local main branch with the upstream repository and delete your local and remote feature branches to keep your environment clean.

How should I test my skill before contributing it?

Skills must be tested using the writing-skills TDD (Test Driven Development) process, including pressure scenarios and baseline tests, to ensure reliability.

Upstream Skill Sharing

Name: Upstream Skill Sharing
Author: franroa

byfranroa

Herramientas de Colaboración

Streamlines the process of contributing custom Claude Code skills to upstream repositories using standardized Git and GitHub CLI workflows.

Acerca de

Upstream Skill Sharing provides a robust framework for developers to contribute their locally developed Claude Code skills back to community or organization repositories. It guides users through the entire contribution lifecycle—from syncing local branches and creating feature-specific environments to formatting standardized commit messages and opening pull requests via the GitHub CLI. By enforcing best practices such as single-skill PRs and TDD verification, it ensures that contributions are high-quality, maintainable, and easy for repository owners to review.

Características Principales

Standardized commit message templates for skill metadata
0 GitHub stars
Upstream synchronization and merge conflict resolution guides
Automated branch creation and naming conventions
GitHub CLI integration for streamlined pull request creation
Strict validation for single-skill contribution patterns

Casos de Uso

Proposing improvements or bug fixes to existing community-driven skills
Contributing a production-tested coding pattern to a shared organizational skill library
Maintaining a synchronized local development environment with upstream superpower repositories

Acerca de

Características Principales

Standardized commit message templates for skill metadata
0 GitHub stars
Upstream synchronization and merge conflict resolution guides
Automated branch creation and naming conventions
GitHub CLI integration for streamlined pull request creation
Strict validation for single-skill contribution patterns

Casos de Uso

Proposing improvements or bug fixes to existing community-driven skills
Contributing a production-tested coding pattern to a shared organizational skill library
Maintaining a synchronized local development environment with upstream superpower repositories