Sharing Skills
Use when contributing skills back to the community. Follow git workflow: sync upstream → create branch → develop skill → test with writing-skills → commit → push → PR. One skill per PR.
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill sharing-skillsgit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/sharing-skills ~/.claude/skills/sharing-skillsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Sharing Skills ## Core Principle Skills that work for you can work for others. Share them upstream so the whole community benefits. ## When to Use This Skill - You've created a skill that works well - The skill applies broadly (not project-specific) - The skill has been tested and validated - You want to contribute to the community - You've refined an existing pattern - You've discovered a valuable technique ## The Iron Law **ONE SKILL PER PULL REQUEST.** Multiple skills in one PR are hard to review, harder to discuss, and harder to merge. ## Prerequisites Before sharing a skill upstream: ### 1. Skill Quality Requirements ``` ✅ Skill is tested and validated ✅ Skill applies broadly (not company/project specific) ✅ Skill follows the writing-skills pattern ✅ Skill has been tested with testing-skills-with-subagents ✅ Documentation is complete and clear ✅ Examples are realistic and helpful ✅ No proprietary or sensitive information ``` ### 2. Repository Setup ```bash # Add upstream remote (if not already added) git remote add upstream https://github.com/superpowers/superpowers.git # Verify remotes git remote -v # Should show: # origin https://github.com/yourusername/superpowers.git (fetch) # origin https://github.com/yourusername/superpowers.git (push) # upstream https://github.com/superpowers/superpowers.git (fetch) # upstream https://github.com/superpowers/superpowers.git (push) ``` ## The Contribution Workflow ### Step 1: Sync with Upstream
Details
- Skill name
sharing-skills- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/sharing-skills/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the Sharing Skills skill do?
Use when contributing skills back to the community. Follow git workflow: sync upstream → create branch → develop skill → test with writing-skills → commit → push → PR. One skill per PR.
How do I install the Sharing Skills skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Sharing Skills popular?
It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
Edu Lesson Plan
5eshmith7/claude-skills-library
Plan a lesson backwards from the check, with misconceptions named, whole-class checks that each carry a branch, and what to cut decided in advance. Use for lesson or unit plans.
Retro Points
5vnovakovits/claude-skills
Turn a discussion into retrospective points for a team's daily retro. Called on the current conversation, a pasted thread, a file, or a ticket or PR, it finds what slowed the team down, traces each item from event to pattern to the structure and belief behind it, names the system archetype, runs the systems-thinking iceberg on recurring points, proposes one structural experiment per pattern, scores it for impact, and recommends what the retro should open with. Built on Kerth's Prime Directive, Derby & Larsen's phases, Toyota Kata's daily improvement cycle, a multi-branch 5 Whys repaired with A
Canon PR Review
5npow/claude-skills
Review a PR against the top 20 Tier 2 LLM-enforceable best practices from 35 seminal software engineering books (Code Complete, Clean Code, A Philosophy of Software Design, Refactoring, Release It!, Designing Data-Intensive Applications, etc.). Produces a structured PR comment with four dimension scores (0-5 each), specific violations with line numbers, and an APPROVE / REQUEST_CHANGES / BLOCK decision. Auto-invoke when the user asks to: - "review PR", "canon review", "best practices review", "engineering standards review" - "score this PR", "check this PR against best practices" - Asks about
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.