AI Skills
Sharing AI Skills Across Teams: Collaboration Guide
Learn strategies for sharing AI skills across teams and organizations. Build a culture of skill contribution and maintain quality at scale.
Learn strategies for sharing AI skills across teams and organizations. Build a culture of skill contribution and maintain quality at scale.
Individual skills are valuable. Shared skills are transformative. When a team member develops an effective skill for code review, security audits, or API documentation, that knowledge multiplies across everyone who uses it.
But sharing is not just copying files. Effective skill sharing requires governance, quality control, documentation, and culture. This guide covers how to build skill-sharing practices that scale across teams and organizations.
One developer creates a TypeScript code review skill. It takes 4 hours to refine.
Without sharing:
With sharing:
Shared skills mean:
When experts leave, their skills remain:
One authoritative source for skills:
org/claude-skills/
├── core/ # Organization-wide
│ ├── code-review.md
│ ├── security-basics.md
│ └── documentation.md
├── teams/
│ ├── frontend/
│ │ ├── react-patterns.md
│ │ └── css-standards.md
│ └── backend/
│ ├── api-design.md
│ └── database-patterns.md
├── archived/
└── README.md
Governance:
Pros:
Cons:
Teams maintain their own skills, with cross-team visibility:
org/
├── frontend-skills/ # Owned by frontend team
├── backend-skills/ # Owned by backend team
├── platform-skills/ # Owned by platform team
└── shared-skills/ # Cross-team collaboration
Governance:
Pros:
Cons:
Internal skill marketplace with ratings and reviews:
internal-skill-market/
├── listings/
│ ├── python-review/
│ │ ├── skill.md
│ │ ├── metadata.json
│ │ └── reviews/
│ └── api-documentation/
├── featured/
└── categories/
Governance:
Pros:
Cons:
# Skill Review Checklist
## Purpose (Pass/Fail)
- [ ] Clear, focused purpose statement
- [ ] Scope boundaries defined
- [ ] No overlap with existing skills
## Content Quality (1-5)
- [ ] Accurate, tested guidance
- [ ] Specific, actionable instructions
- [ ] Appropriate examples
## Structure (1-5)
- [ ] Logical organization
- [ ] Proper markdown formatting
- [ ] Complete metadata
## Testing (Pass/Fail)
- [ ] Tested with representative inputs
- [ ] Outputs match expectations
- [ ] Edge cases considered
## Documentation (1-5)
- [ ] Usage instructions clear
- [ ] Examples provided
- [ ] Limitations documented
graph LR
A[Submit Skill] --> B[Automated Checks]
B --> C{Passes?}
C -->|No| D[Return for Fixes]
C -->|Yes| E[Peer Review]
E --> F{Approved?}
F -->|No| D
F -->|Yes| G[Publish]
# .github/workflows/skill-lint.yml
name: Skill Quality
on:
pull_request:
paths:
- 'skills/**/*.md'
jobs:
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Check metadata
run: |
for file in skills/**/*.md; do
grep -q "^version:" "$file" || echo "Missing version: $file"
grep -q "^author:" "$file" || echo "Missing author: $file"
done
- name: Check structure
run: |
# Verify required sections exist
for file in skills/**/*.md; do
grep -q "## Purpose\|## Objective" "$file" || echo "Missing purpose: $file"
done
- name: Lint markdown
uses: markdownlint/markdownlint-action@v1
# Skill Quality Tiers
## Tier 1: Verified
- Reviewed by 2+ maintainers
- Tested with production workloads
- Actively maintained
- Recommended for critical use
## Tier 2: Community
- Peer reviewed
- Basic testing completed
- Maintained by author
- Good for general use
## Tier 3: Experimental
- Minimal review
- Limited testing
- May have rough edges
- Use with caution
## Archived
- No longer maintained
- May contain outdated guidance
- Preserved for reference
Recognition:
# Skill Contributors
## Hall of Fame
- Jane Smith: 15 skills, 100+ users
- John Doe: 8 skills, security specialist
- Alice Chen: 12 skills, frontend expert
## Recent Contributors
- @developer1: typescript-v5.md
- @developer2: api-versioning.md
Gamification:
Integration:
Templates:
---
version: 1.0.0
author: [Your Name]
created: [Date]
last_updated: [Date]
---
# [Skill Name]
## Purpose
[What this skill does]
## When to Use
[Situations where this skill applies]
## Core Guidance
[Main instructions]
## Examples
[Demonstration of usage]
## Limitations
[What this skill does not cover]
Quick start:
# Scaffold a new skill
./scripts/new-skill.sh "My New Skill"
# Creates skills/my-new-skill.md from template
Clear guidelines:
# Contributing Skills
## 1. Check for Existing Skills
Search the repository before creating new skills.
## 2. Start Small
Begin with a focused skill. Expand later if needed.
## 3. Use the Template
Fill in all template sections.
## 4. Test Locally
Use the skill yourself before submitting.
## 5. Submit PR
Include description, examples, and test results.
# First Skill Contribution Guide
## Step 1: Identify a Need
- What do you repeat often?
- What advice do you give teammates?
- What would help your daily work?
## Step 2: Draft Your Skill
- Start with the template
- Focus on one specific task
- Include examples
## Step 3: Test It
- Use the skill for a week
- Note what works and what doesn't
- Refine based on experience
## Step 4: Get Feedback
- Share with 1-2 colleagues
- Incorporate their suggestions
- Refine further
## Step 5: Submit
- Create a pull request
- Describe purpose and usage
- Respond to review feedback
## Step 6: Maintain
- Monitor for issues
- Update for new patterns
- Respond to questions
# [Skill Name]
## Overview
Brief description of what this skill does.
## When to Use
- Situation 1
- Situation 2
- Situation 3
## When NOT to Use
- Situation 1 (use [other-skill] instead)
- Situation 2
## Usage
### Loading
/load-skill skill-name
### Example Interactions
**Input:**
[Example request]
**Output:**
[Example response]
## Configuration
### Options
- option1: Description (default: value)
- option2: Description (default: value)
### Customization
How to modify for specific needs.
## FAQ
**Q: Common question?**
A: Answer.
## Related Skills
- [Related Skill 1](./related-skill-1.md)
- [Related Skill 2](./related-skill-2.md)
## Changelog
- 1.2.0: Added feature X
- 1.1.0: Fixed issue Y
- 1.0.0: Initial release
## Maintainer
@username - Contact for questions
# Organization Claude Skills
## Quick Start
1. Clone: `git clone git@github.com:org/claude-skills.git ~/.claude/skills`
2. Start Claude: `claude`
3. Skills auto-load based on context
## Popular Skills
| Skill | Purpose | Tier |
|-------|---------|------|
| [code-review](./core/code-review.md) | Standard code review | Verified |
| [api-design](./backend/api-design.md) | API design patterns | Verified |
| [react-patterns](./frontend/react-patterns.md) | React best practices | Community |
## Categories
- [Core](./core/) - Organization-wide standards
- [Frontend](./frontend/) - Frontend development
- [Backend](./backend/) - Backend development
- [Security](./security/) - Security practices
## Contributing
See [CONTRIBUTING.md](./CONTRIBUTING.md)
## Support
- Slack: #claude-skills
- Issues: GitHub Issues
- Wiki: Internal Wiki
## Skill Adoption Dashboard
### Usage (Last 30 Days)
| Skill | Active Users | Sessions | Trend |
|-------|--------------|----------|-------|
| code-review | 45 | 892 | +12% |
| api-design | 32 | 456 | +8% |
| typescript | 28 | 334 | +15% |
### Adoption Rate
- Total skills: 47
- Skills with 10+ users: 23 (49%)
- Skills with 50+ users: 8 (17%)
### New Skill Adoption
- Average time to 10 users: 2.3 weeks
- Skills reaching 50 users: 35%
## Quality Dashboard
### Rating Distribution
- 5 stars: 12 skills
- 4 stars: 18 skills
- 3 stars: 10 skills
- 2 stars: 5 skills
- 1 star: 2 skills
### Issue Rate
- Issues per 100 uses: 0.8
- Resolved within 1 week: 78%
### Update Frequency
- Skills updated last 30 days: 15
- Skills stale (>6 months): 8
## Contribution Dashboard
### Contributor Stats
- Total contributors: 34
- Active this quarter: 18
- New contributors: 5
### Contribution Flow
- Skills submitted: 12
- Skills approved: 9
- Average review time: 2.1 days
### Coverage
- Teams with skills: 8/10
- Domains covered: API, Frontend, Backend, Security, Testing, Docs
- Gaps identified: Mobile, ML/AI
Skill Maintainers:
Team Leads:
Individual Contributors:
# Skill Governance
## Adding Skills
- Any contributor can submit
- 2 maintainer approvals required
- No overlapping skills allowed
## Modifying Skills
- Minor changes: Author can merge
- Major changes: Maintainer approval
- Breaking changes: Announce 2 weeks ahead
## Deprecating Skills
- Propose with reason
- 30-day notice period
- Provide migration path
- Archive, do not delete
## Disputes
- Escalate to skill committee
- Committee decision is final
- Document for future reference
Sharing skills across teams transforms individual productivity gains into organizational capabilities. Effective sharing requires:
Start simple. Begin with a shared repository and basic review process. Add sophistication as the skill library grows and contribution patterns emerge.
The goal is a living library of organizational knowledge that makes everyone more effective with AI tools.
Ready to design skills with clear purpose? Continue to Designing Skills with Clear Purpose for focused skill creation.