Question 1
Domain 1Situation: Your team uses a /commit skill in .claude/skills/commit/SKILL.md. A developer wants to customize it for their personal workflow (different commit message format, extra checks) without affecting teammates. What do you recommend?
Correct answer: C
Explanation
Claude skills can be customized per user by placing a skill in the personal skills directory, which overrides team-shared behavior for that user. Using "~/.claude/skills/commit/SKILL.md" with the same name lets the developer change commit format and checks without changing ".claude/skills/commit/SKILL.md" for teammates.
Why each option is right or wrong
A. Create a personal version under ~/.claude/skills/ with a different name, e.g., /my-commit.
Different name creates a new command, not a personal override of `/commit`.
B. Add conditional logic based on username in the project skill frontmatter.
Username-based logic changes shared project code and adds team-visible complexity.
C. Create a personal version at ~/.claude/skills/commit/SKILL.md with the same name.
Claude resolves skills by location, and a user-level skill stored under ~/.claude/skills/ takes precedence over the team-shared copy in .claude/skills/. Because the personal file uses the same skill name/path segment (commit/SKILL.md), the developer can alter the commit-message format and add extra checks for their own account without modifying the shared repository version that teammates load.
D. Set override: true in the personal skill frontmatter to prioritize it over the project version.
Override behavior comes from same-name precedence, not a special frontmatter flag here.