pr-codeowners
Identify code owners for changed files and map them to Slack group handles. Use when the user asks who owns changed files, which teams to tag for review, or to find code owners for a PR.
95
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly communicates specific capabilities, includes natural trigger terms developers would use, and explicitly states both what the skill does and when to use it. The combination of code ownership identification and Slack handle mapping creates a distinct, unambiguous niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Identify code owners for changed files' and 'map them to Slack group handles'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Identify code owners for changed files and map them to Slack group handles') and when ('Use when the user asks who owns changed files, which teams to tag for review, or to find code owners for a PR'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'code owners', 'changed files', 'teams to tag', 'review', 'PR', 'Slack group handles'. Good coverage of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining code ownership with Slack handle mapping. The specific mention of CODEOWNERS, Slack groups, and PR review context makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that provides all the domain-specific knowledge Claude needs (the team-to-Slack mapping) without over-explaining. The workflow is clear and actionable with a concrete git command and explicit fallback behavior. The only weakness is the lack of validation steps for edge cases (missing CODEOWNERS file, no changed files, ambiguous pattern matches).
Suggestions
Add a brief validation step after step 1 to handle the case where there are no changed files or the CODEOWNERS file doesn't exist
Consider noting how to handle files that match multiple CODEOWNERS patterns (e.g., last match wins per CODEOWNERS spec)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every token earns its place. No unnecessary explanations of what CODEOWNERS is, how git works, or what Slack handles are. The lookup table is pure reference data that Claude genuinely needs. | 3 / 3 |
Actionability | Provides an executable git command, a concrete lookup table with exact mappings, a clear fallback rule, and a specified output format. Claude knows exactly what to do at each step. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (get files → match patterns → map owners → handle fallback), but there's no validation checkpoint—e.g., verifying CODEOWNERS file exists, confirming pattern matching correctness, or handling edge cases like no changed files. | 2 / 3 |
Progressive Disclosure | For a skill of this size and scope (single-purpose, under 50 lines of non-table content), the structure is well-organized with clear sections (Steps, Lookup table, Output) and no need for external references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- MetaMask/metamask-mobile
- Commit
bee9b14
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.