sharing-skills

Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository

Stars 163

Forks 31

Install this agent skill to your Project

npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/sharing-skills

SKILL.md

Sharing Skills

Core Principles

Test before share - Only share skills validated via writing-skills TDD process
One skill per PR - Each skill independently reviewable
Broadly useful - Not project-specific or experimental

Quick Reference

bash

# 1. Sync
git checkout main && git pull upstream main

# 2. Branch
git checkout -b "add-${skill_name}-skill"

# 3. Work
# Edit skills/your-skill-name/SKILL.md

# 4. Commit
git add skills/your-skill-name/
git commit -m "Add ${skill_name} skill"

# 5. Push + PR
git push -u origin "add-${skill_name}-skill"
gh pr create --repo <UPSTREAM_ORG>/<UPSTREAM_REPO> \
  --title "Add ${skill_name} skill" \
  --body "## Summary\n...\n## Testing\n..."

When to Share vs Keep Personal

Share	Keep Personal
Applies broadly	Project-specific
Well-tested	Experimental/unstable
Others benefit	Contains sensitive info
Documented	Too narrow/niche

Prerequisites

gh CLI installed and authenticated
Working directory is your local skills clone
Skill tested using writing-skills TDD process

Anti-Patterns

❌ Batching - Multiple skills in one PR
❌ Untested - Sharing without baseline testing
❌ Project-specific - Personal conventions as universal skills
❌ Incomplete docs - Missing Overview, Quick Reference, Common Mistakes

References

Workflow Example - Complete async-patterns example

writing-skills - REQUIRED: Create well-tested skills before sharing
maestro-core - Workflow routing and skill hierarchy

Search AI Tools