How to Share Claude Code Skills With Your Team

Personal skills in ~/.claude/skills/ only work for you. To standardize AI-assisted workflows across a team, you need project-level skills.

Quick Answer: To share Claude code skills with your team, place skills in a .claude/skills/ directory at the repository's root, then commit and push to Git. This ensures all team members automatically get these skills for standardized AI-assisted workflows.

Project-level skills via git

Put skills in .claude/skills/ at the root of your repository:

mkdir -p .claude/skills/our-code-review/
# Create or copy the SKILL.md
git add .claude/skills/
git commit -m "Add team code review skill"
git push

Everyone who clones or pulls the repo gets the skills automatically. No individual setup. No instructions to follow. It just works.

What to standardize

The highest-value team skills encode decisions that are otherwise communicated through code reviews and Slack messages:

Code review standards. What does your team actually check for? Security requirements, error handling patterns, naming conventions, test coverage expectations. Put it in a skill instead of repeating it in PR comments.

Testing patterns. Which framework, what file naming convention, which assertion style, how thorough the edge case coverage should be. A skill ensures every developer's AI-generated tests fit the existing suite.

Architecture decisions. Where to put new files, how to structure modules, which patterns to use for data access, how to handle errors. These decisions live in ADRs that nobody reads — a skill enforces them automatically.

Git workflow. Commit message format, branch naming, PR template content. A git skill ensures consistency across every contributor.

Managing team skills

Update team skills through pull requests like any other code change:

git checkout -b update-review-skill
# Edit .claude/skills/our-code-review/SKILL.md
git commit -m "Add TypeScript strict mode to review checklist"
git push && create PR

This means skills go through the same review process as code. Someone proposes a change, the team reviews it, and it merges when approved.

Personal vs team skills

Both can coexist. Claude Code loads personal skills from ~/.claude/skills/ and project skills from .claude/skills/. If two skills cover the same task, both are available.

Use personal skills for individual preferences (your editor style, your personal shortcuts). Use project skills for team standards (code review, testing, architecture).

Sharing across multiple projects

If your team uses the same standards across multiple repos, you have two options:

Git submodule. Create a separate repo for your team skills and include it as a submodule in each project:

git submodule add https://github.com/your-org/team-skills.git .claude/skills

Manual copy. Copy the skills folder into each project. Simpler but requires manual updates.

Sharing via marketplace

If your team skills are valuable beyond your organization, publish them on Agensi. Set any price including free. You earn 80% of sales, and your skills get security-scanned and reviewed before listing.

---

Browse team-ready skills at Agensi.