code-owners

Identify who owns, maintains, or has expertise in a specific code area — use when asked who to talk to about a system, who to request a code review from, or who has been actively working in a codebase area.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable workflow that leads Claude from contributor search through vetting to a formatted ownership map. It is concise, executable, and appropriately self-contained.

Dimension	Reasoning	Score
Conciseness	Lean and free of concepts Claude already knows; the output templates are deliverable formats rather than padding, with only minor trimmable detail.	4 / 5
Actionability	Provides concrete, copy-ready search commands (code_search, search, employee_search) and a vetting criteria table; minor gaps around tool availability/parameter semantics.	4 / 5
Workflow Clarity	Six phases are clearly sequenced with a vetting checkpoint in Phase 5 and a fallback 'If No Clear Owners Found' path; no explicit validate-fix-retry loop, but the task is read-only so it is not required.	4 / 5
Progressive Disclosure	Self-contained skill with no bundle files; content is well-organized into phases and sections with no inlined material that belongs in a separate file.	4 / 5
	Total	16 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-crafted description that pairs a clear capability statement with an explicit, naturally-worded trigger clause. It is specific, complete, and largely distinct from sibling skills.

Dimension	Reasoning	Score
Specificity	Names the core action ('Identify') across three concrete target variants ('owns, maintains, or has expertise'), giving several specific capabilities with only minor coverage gaps.	4 / 5
Completeness	Explicitly states both what it does (identify owners/maintainers/experts) and when to use it via a concrete 'use when...' clause with multiple trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user phrases ('who to talk to about a system', 'who to request a code review from', 'actively working in a codebase area'); a few synonyms (e.g. 'who owns this code') are not covered.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (code ownership identification) with distinct triggers; only minor overlap risk with generic code-search or review skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: gleanwork/claude-plugins
Path: plugins/glean/skills/code-owners/SKILL.md
Commit: a549de6

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.