SOP 009: Share and Distribute Skills
Fresh| Field | Value |
|---|---|
| SOP ID | 009 |
| Version | 1.0 |
| Status | Active |
| Last Updated | 2026-02-14 |
Purpose
Share skills at different scopes: project (team), plugin (community), and managed (enterprise).
Distribution Channels
Procedure
Step 1: Choose Distribution Method
| Method | Scope | Setup | Updates |
|---|---|---|---|
| Project skills | Team (repo-level) | Commit .claude/skills/ | Git pull |
| Plugin skills | Community | Create plugin with skills/ dir | Plugin update |
| Managed skills | Enterprise | Admin managed settings | Central push |
Step 2: Project Skills (Team)
Commit your skills to the repository:
bash
# Add skills to version control
git add .claude/skills/
git commit -m "Add team skills for code review and deploy"
git pushTeam members get skills automatically when they pull the repo.
Step 3: Plugin Skills (Community)
Create a skills/ directory in your plugin:
my-plugin/
skills/
review/
SKILL.md
deploy/
SKILL.mdPlugin skills use plugin-name:skill-name namespace, so they cannot conflict with other levels.
Step 4: Managed Skills (Enterprise)
Deploy organization-wide through managed settings. See the managed settings documentation.
Additional Directories
Skills from --add-dir directories are loaded automatically with live change detection:
bash
claude --add-dir /path/to/shared-skillsLive Reload
Skills from --add-dir support live change detection, so you can edit them during a session without restarting.
Verification Checklist
- [ ] Skills work locally before sharing
- [ ] Correct distribution method chosen for the audience
- [ ] No sensitive data in skill files (API keys, secrets)
- [ ] Skills tested by another user after distribution
- [ ] Version control tracking for project skills