daBongo LMS AI Training Courses

Lesson Content

Distribution levels.

Skills in Claude Code can operate at different scopes (verify current scope configuration at docs.anthropic.com):

Personal Skills: Stored in a user-level directory, available in all of the user's Claude Code sessions. For personal workflow preferences.

Project Skills: Stored in the project repository (committed to version control), available for all team members using Claude Code in that project. For team-shared workflows and standards.

Organization Skills (if supported by your Claude Code version): Shared across all projects in an organization. For organization-wide standards. Verify current organization-level Skill support at docs.anthropic.com.

Project-level Skills in version control.

Committing Skills to the project repository:

• Skills are visible to the whole team via code review
• Changes to Skills go through the same PR review process as code changes
• Skills are versioned with the codebase – the team is always on the same Skill version
• New team members get Skills automatically when they clone the repository

For a team, project-level Skills in version control are the standard distribution method.

Skills review in PRs.

When a Skill is committed or updated via PR, reviewers should:

• Test the trigger conditions: does the Skill activate when it should?
• Review the instruction content: are the instructions accurate, actionable, and complete?
• Identify potential false activations: could these triggers cause the Skill to activate in unintended contexts?
• Check for outdated instructions: do the instructions reflect current team practices?

Version control practices for Skills.

• Name Skills clearly and descriptively (not skill1.md)
• Include a "last reviewed" note in the Skill frontmatter
• Create a SKILLS.md index file listing all project Skills with their purpose
• Tag Skill updates in release notes so team members know to verify their Claude Code picks them up