Skills: Skill Sharing & Marketplace
Last updated: 2026-08-31
One person's best practice is experience; a group's best practice is a standard — sharing turns Skills from personal tools into team assets.
1. Sharing Methods
(1) Git Repository Sharing
The most basic sharing method, version-managed through Git:
TEXT
📖 Display only
Team Skills Repository Structure
├── skills/
│ ├── code-review.md
│ ├── auto-test.md
│ ├── deploy.md
│ └── security-scan.md
├── README.md (index and usage instructions)
└── CHANGELOG.md (version change records)
(2) Project-Embedded
Place Skills directly in the project directory:
| Platform | Directory | Scope |
|---|---|---|
| Claude Code | .claude/skills/ |
Current project |
| Cursor | .cursor/rules/ |
Current project |
| OpenCode | skills/ |
Current project |
(3) Global Install
Effective for all projects:
BASH
# Claude Code global Skills
~/.claude/skills/
# User-level configuration
~/.config/opencode/skills/
2. Publishing Process
(1) Skill Quality Checklist
Must check before publishing:
TEXT
📖 Display only
Pre-Publish Checks
├── [ ] Prompt is complete and specific
├── [ ] Frontmatter info is accurate (name, description, triggers)
├── [ ] Includes usage examples
├── [ ] Tested on at least 2 projects
├── [ ] Does not contain project-sensitive information
├── [ ] Required tools are documented
└── [ ] Includes README documentation
(2) Skill Package Structure
TEXT
📖 Display only
Publish Package Structure
├── skill-name.md # Main Skill file
├── README.md # Usage instructions
├── examples/ # Usage examples
│ └── example-1.md
└── CHANGELOG.md # Change records
(3) Version Number Standards
TEXT
📖 Display only
Semantic Versioning: MAJOR.MINOR.PATCH
MAJOR: Incompatible prompt changes (output format changes)
MINOR: Backward-compatible additions (new review dimension)
PATCH: Backward-compatible fixes (fix prompt ambiguity)
Example:
1.0.0 → First official release
1.1.0 → Added security review dimension
1.1.1 → Fixed review output format issue
2.0.0 → Restructured output format (incompatible with old version)
3. Discovery & Installation
(1) Discovery Channels
| Channel | Features | Best For |
|---|---|---|
| GitHub repos | Version-managed, traceable | Internal team sharing |
| Community forums | Discussion + feedback | Generic Skills |
| Official marketplace | Quality reviewed | High-quality Skills |
| Colleague recommendations | High trust | Industry-specific Skills |
(2) Installation Process
BASH
# Method 1: Direct copy
cp community/code-review.md .claude/skills/
# Method 2: Git submodule
git submodule add https://github.com/team/skills.git .claude/skills-external
# Method 3: Symlink (for development)
ln -s ~/shared-skills/code-review.md .claude/skills/code-review.md
(3) Dependency Management
YAML
# Skill dependency declaration
dependencies:
tools:
- Read
- Bash
skills:
- name: base-review
version: ">=1.0.0"
mcp_servers:
- database
4. Team Skill Library Practice
▶ Example: Building a Team Skills Library
Alice established a standardized skill library for the team:
TEXT
📖 Display only
Team Skills Library
├── 01-execution/ # Skills that directly execute tasks
│ ├── deploy.md
│ ├── test-runner.md
│ └── lint-fix.md
├── 02-review/ # Skills for analysis and evaluation
│ ├── code-review.md
│ ├── security-scan.md
│ └── performance-check.md
├── 03-assistant/ # Skills that provide suggestions
│ ├── doc-generator.md
│ └── refactor-advisor.md
└── README.md # Index and usage guide
Bob said: "A Skills library isn't just throwing files together — it needs categorization, indexing, and version management, otherwise it's no different from a pile of random files."
❓ FAQ
Q Can community Skills be trusted directly?
A No. You must review prompt content before installing to confirm it doesn't contain malicious instructions (like reading secret files, executing dangerous commands).
Q How to handle conflicts between team and personal Skills?
A Team Skills have higher priority than personal Skills. Personal customizations go in the global directory; team standards go in the project directory.
Q What if a Skill update breaks compatibility with old projects?
A Use semantic versioning. Major version changes indicate incompatibility; old projects pin to the major version number.
📖 Summary
- Three sharing methods: Git repository, project-embedded, global install
- Publishing process: Quality check → package → version number → publish
- Discovery & installation: GitHub, community, marketplace + dependency management
- Team skill library: Categorized management, index maintenance, version pinning
📝 Exercises
- Basic (⭐): Organize your created Skills into a Git repository with a README index.
- Intermediate (⭐⭐): Create a categorized team skill library with at least 1 Skill each for execution, review, and assistant categories.
- Advanced (⭐⭐⭐): Design a Skill dependency management system supporting version declarations, compatibility checks, and auto-update notifications.
