skills.rest
gujiachun-rainbow
gujiachun-rainbowCOMMUNITY
Explore all skills by this author →
GitHub

Sharing Skills

Share local branch skills to an upstream repository via pull request.

8|1|Updated Apr 15, 2026
Search Tags:#git#workflow#skills#branching#pull-request#upstream#share
One-click install
npx skills add https://github.com/gujiachun-rainbow/RainClaw --skill sharing-skills-gujiachun-rainbow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Sharing Skills
Source: https://github.com/gujiachun-rainbow/RainClaw/tree/main/.trae/skills/sharing-skills
Command: npx skills add https://github.com/gujiachun-rainbow/RainClaw --skill sharing-skills-gujiachun-rainbow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Share skills from your local branch back to the upstream repository, enabling community-driven improvement.

Core Features & Use Cases

  • Branch → Edit/Create skill → Commit → Push → PR to upstream to propose changes to the skill library.
  • Enforces a clear path for contributions and ensures code review and governance.
  • Works with skills that are broadly useful and well-documented, not project-specific.

Quick Start

Create a feature branch, edit or add skills/your-skill/SKILL.md, commit, push, and open a PR to upstream.

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 broadly useful skill back to an upstream repository?▼

Contributing a skill upstream requires creating a local branch, editing or adding the skill file, committing, pushing, and opening a pull request. This PR-based workflow enforces prerequisites, branch naming, and code review for controlled integration.

When should I share skills upstream instead of keeping them project-specific?▼

You should share skills upstream when a skill is broadly useful, well-tested, well-documented, and ready for adoption across teams. Avoid sharing project-specific skills that lack general applicability for community-driven improvement.

What git workflow is enforced for sharing skills to the upstream library?▼

The git workflow enforces prerequisites, branch naming, and PR-based integration. You must use a local feature branch, push your commits, and propose changes via a pull request to ensure reviewable and controlled contributions to the skill library.

Can I push a skill directly to the upstream repository without a pull request?▼

No, you cannot push directly. The Sharing Skills process enforces PR-based integration to ensure controlled and reviewable contributions. You must open a pull request from your local branch to propose changes to the upstream skill library.

What files do I need to edit before opening a pull request to share a skill?▼

You need to edit or create the skills/your-skill/SKILL.md file on a feature branch. After committing this file, push the branch and open a pull request to the upstream repository to propose your skill for adoption.

Related Skills

Explore More Software Engineering Skills→
beemanbeeman
3

gh-commit

Prepare a clean local commit on the correct feature branch from repository changes.

Community
Advanced
spencerpaulyspencerpauly
672

babysitting-pr

Monitor open pull requests and resolve CI failures, review comments, and merge conflicts.

Community
Advanced
robertphyattrobertphyatt
7

writing-skills

Draft and validate IronClaude skills using the RED-GREEN-REFACTOR workflow.

Community
Intermediate
pv-udpvpv-udpv
4

Sharing Skills

Contribute skills to upstream repositories via branch-and-PR workflow.

Community
Advanced