Should I share project-specific skills?

No, you should only share skills that apply broadly and follow the writing-skills guidelines; project-specific or sensitive skills should remain local.

What tools are required to use this skill?

You must have the GitHub CLI (gh) installed and authenticated, and your local environment must be set up with a fork of the skills repository.

Can I contribute multiple skills in one pull request?

No, the workflow recommends creating a separate feature branch and pull request for each individual skill to ensure they can be reviewed independently.

What is the primary purpose of the sharing-skills skill?

It provides a standardized workflow for developers to contribute their locally created Claude skills back to the main upstream repository via GitHub.

How does it handle pull requests?

The skill uses the gh pr create command with pre-formatted templates for titles and bodies to ensure clear communication with repository maintainers.

Skill Contribution Workflow

Name: Skill Contribution Workflow
Author: franroa

byfranroa

Developer Tools

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

About

The Skill Contribution Workflow provides a structured framework for developers to share their locally developed Claude skills with the wider community. It guides users through the entire lifecycle of a contribution—from syncing local forks and creating dedicated feature branches to crafting standardized commit messages and opening professional pull requests using the GitHub CLI. By enforcing best practices like testing requirements and branch isolation, this skill ensures that contributions are maintainable, well-documented, and ready for upstream integration.

Key Features

Automated Git branch management for feature isolation
Seamless GitHub CLI integration for automated PR creation
0 GitHub stars
Upstream synchronization logic to prevent merge conflicts
Pre-formatted commit message templates for skill metadata
Clear decision criteria for public vs. private skill sharing

Use Cases

Managing the lifecycle of multiple independent skill contributions
Contributing a broadly useful, well-tested skill to a public repository
Updating existing upstream skills with bug fixes or new patterns

About

Key Features

Automated Git branch management for feature isolation
Seamless GitHub CLI integration for automated PR creation
0 GitHub stars
Upstream synchronization logic to prevent merge conflicts
Pre-formatted commit message templates for skill metadata
Clear decision criteria for public vs. private skill sharing

Use Cases

Managing the lifecycle of multiple independent skill contributions
Contributing a broadly useful, well-tested skill to a public repository
Updating existing upstream skills with bug fixes or new patterns