skills.rest
Donaldshen27
Donaldshen27COMMUNITY
Explore all skills by this author →
GitHub

sharing-skills

Create a feature branch, update SKILL.md, and open a pull request.

Updated Nov 14, 2025
Search Tags:#workflow#collaboration#skills#sharing#pull-request
One-click install
npx skills add https://github.com/Donaldshen27/xtrend-vanilla --skill sharing-skills-donaldshen27
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/Donaldshen27/xtrend-vanilla/tree/main/.claude/skills/sharing-skills
Command: npx skills add https://github.com/Donaldshen27/xtrend-vanilla --skill sharing-skills-donaldshen27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide standardizes how individuals contribute broadly useful skills from their local work back to the upstream repository, enabling reuse, consistency, and collaborative improvement across teams.

Core Features & Use Cases

  • Clear branching workflow: create a feature branch for skill changes and keep main clean.
  • Structured SKILL.md: ensures each skill exposes metadata and guidance for use.
  • PR-driven contribution: promotes code review, discussion, and safe merging upstream.
  • Clear sharing criteria: guidance on when a skill should be shared publicly versus kept private.

Quick Start

Create a feature branch, add or update the SKILL.md in skills/sharing-skills/SKILL.md, commit and push, then open a PR 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 share broadly useful skills upstream with a pull request?▼

To share skills upstream with a pull request, create a feature branch, add or update the SKILL.md at the skill root, commit, push, and open a PR to the upstream repository for review and merging.

What metadata is required in SKILL.md for sharing skills?▼

Sharing skills requires a valid SKILL.md at the skill root with a name and description, plus descriptive metadata including category, keywords, and optional components to ensure proper contribution and reuse.

When should I share a skill publicly versus keeping it private?▼

Share a skill publicly when it is general, well-tested, and beneficial to others. Keep skills private if they are specific to local workflows or not fully tested for collaborative reuse.

What is the best workflow for contributing skills back to a repository?▼

The best workflow for contributing skills is PR-driven: create a feature branch to keep main clean, edit SKILL.md, commit and push changes, then open a PR to promote code review and safe merging upstream.

Why does contributing skills via PR require a feature branch?▼

Contributing skills via PR requires a feature branch to keep the main branch clean, standardizing the contribution workflow and enabling structured code review, discussion, and safe merging upstream.

Related Skills

Explore More Content & Communication Skills→
mattia2110mattia2110
21

Pop Types

Validate Skill Units and extract structured metadata from SKILL.md files.

Community
Intermediate
erclxerclx
2

git-followup

Stage, commit, and push follow-up edits to an open pull request branch.

Community
Advanced
thejordanleopoldthejordanleopold
4

git-workflow

Enforce trunk-based Git workflows with atomic commits and branch cleanup.

Community
Advanced
samChang72samChang72
1

address-github-comments

Manage GitHub PR review comments using GitHub CLI commands.

Community
Basic