Skip to content

SOP 009: Share and Distribute Skills

Fresh
FieldValue
SOP ID009
Version1.0
StatusActive
Last Updated2026-02-14

Purpose

Share skills at different scopes: project (team), plugin (community), and managed (enterprise).

Distribution Channels

Procedure

Step 1: Choose Distribution Method

MethodScopeSetupUpdates
Project skillsTeam (repo-level)Commit .claude/skills/Git pull
Plugin skillsCommunityCreate plugin with skills/ dirPlugin update
Managed skillsEnterpriseAdmin managed settingsCentral 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 push

Team 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.md

Plugin 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-skills

Live 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

See Also

Built with VitePress + Claude Code Skills RAG Chat