codebase-context

Gather architectural context about an internal system from code and documentation across the organization — use when asked to understand a system's architecture, find its repos, or get an overview before working on it.

Quality

85%

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

81%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.

The body is a well-structured, actionable five-phase workflow with explicit vetting checkpoints and error-recovery branches. It is concise and avoids over-explanation; the main improvement would be moving the large report templates into a reference file for cleaner progressive disclosure.

Suggestions

Move the two report templates (vetted context report and limited-context report) into a references/ template file and link to it from SKILL.md, keeping the main body as a lean process overview.

Add a concrete employee_search example alongside the Phase 3 code_search query so the contributor-identification step is fully executable end-to-end.

Trim the inline freshness/vetting tables to their decision criteria only, or cross-reference them from a single canonical table to reduce duplicated scaffolding.

Dimension	Reasoning	Score
Conciseness	The body is efficient — it does not explain concepts Claude already knows (what a repo or RFC is) and uses compact tables and templates that earn their tokens; not a 5 because the large inline report template and freshness tables could be marginally trimmed or externalized.	4 / 5
Actionability	Provides concrete, copy-paste-ready queries ('code_search "[system] main OR core updated:past_month"', 'search "[system] architecture OR design doc"') and a full report template covering common cases; not a 5 because employee_search is only mentioned ('Cross-reference with employee_search') without an example, leaving a minor gap.	4 / 5
Workflow Clarity	Five phases are clearly sequenced with Phase 4 acting as an explicit validation/vetting checkpoint (the Include/Note/Reject table is a checklist), and the 'If Limited Context Found' and 'Troubleshooting' sections provide error-recovery feedback loops, matching the top anchor.	5 / 5
Progressive Disclosure	Sections are well-organized with no nested references and no bundle files to navigate; not a 5 because the sizable report templates and freshness/vetting tables are inlined when a references file could keep SKILL.md as a leaner overview, leaving a minor organization gap.	4 / 5
	Total	17 / 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.

The description is well-crafted: third-person voice, explicit 'use when' trigger clause, and concrete actions tied to a distinct internal-systems niche. Minor room to add synonym triggers and sharpen the action list for maximal specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('architectural context about an internal system from code and documentation across the organization') and lists several concrete actions ('understand a system's architecture', 'find its repos', 'get an overview before working on it'), with only minor granularity gaps; not a 5 because the actions are somewhat high-level rather than fully enumerated.	4 / 5
Completeness	Clearly answers both what ('Gather architectural context about an internal system from code and documentation across the organization') and when ('use when asked to understand a system's architecture, find its repos, or get an overview before working on it') with concrete trigger phrases, matching the anchor exactly.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('understand a system's architecture', 'find its repos', 'get an overview') with good keyword coverage; not a 5 because it lacks synonyms/file-extension variants and could include more common phrasings like 'onboard to a codebase'.	4 / 5
Distinctiveness Conflict Risk	Targets a specific niche (internal-system architectural context across the org) with distinct triggers, but has minor overlap risk with general code-search or repo-discovery skills; not a 5 because 'find its repos' could collide with broad search 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/codebase-context/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.