CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qodo-codebase-wisdom

Understand how code works, how a change was done before, and which repos are coupled — to answer a question, plan a code change, debug a regression, or scope a fix, using Qodo managed tools through MCP or the CLI. Use when a task needs to understand a codebase, its history, or how its repos relate — especially for a repo you don't have checked out or work spanning repos — "how does X work", "where is X defined", "who changed X", "explain this service", "plan the change for X", "what would changing X affect", "which repos depend on X", "why did X regress / when did it break", "has this been fixed before", "how did we solve X".

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

The body is highly actionable — concrete commands, exact fallbacks, a routing table, and worked examples with validation checkpoints and retry loops — and its reference files are well structured with conditional one-level-deep loading. The main weaknesses are conciseness and organization: ~25 lines of runtime-update policy and repeated authorization/stop rules are inlined in the main file rather than delegated to references, which also blurs the core workflow sequence.

Suggestions

Move the runtime-update route detail (latest-2 recovery, checksum-pinned installers, per-route update policy) into a reference file like the existing references/skill-updates.md, keeping only the minimum-version probe result and stop conditions in SKILL.md — this would improve both conciseness and progressive_disclosure.

Consolidate the stop/authorization rules currently restated across 'Runtime compatibility gate', 'Preflight', 'Sandbox auth diagnostic', and 'Error Handling' into a single guardrails-adjacent section to remove repetition.

Reorder sections so the core investigation workflow (gate → preflight → route to tool group → narrow-then-fetch → deliver) is contiguous, relocating 'Handle a skill update notice' and other policy asides after it to sharpen the main sequence.

DimensionReasoningScore

Conciseness

The body avoids explaining known concepts and is operationally dense, but the "Runtime compatibility gate" section (~25 lines of update-route, latest-2 recovery, and checksum-pinned-installer policy) and the "Handle a skill update notice" section are inlined policy far removed from the core investigation task, and stop/authorization rules are restated across the Runtime gate, Preflight, Sandbox diagnostic, and Error Handling sections. It is not 2 because there is no basic-concept padding and most sentences carry operational content; it is not 4 because these policy blocks and repetitions are genuinely trimmable or movable to references.

3 / 5

Actionability

The Quick start block gives nine copy-paste-ready commands with flags, the fallback invocation `"${QODO_HOME:-$HOME/.qodo}/bin/qodo"` is exact, preflight specifies exact commands ("qodo read whoami", "qodo tools --refresh", "qodo read codebase search-repos"), and three worked examples show full command sequences with expected results. The honesty caveat that tool names are "illustrative" is paired with a concrete verification command (`qodo read tools <group>`), so the guidance remains fully executable — matching the 5 anchor.

5 / 5

Workflow Clarity

The canonical sequence (compatibility probe → preflight auth/repo resolution → route to tool group → narrow-then-fetch → deliver) is present with explicit validation checkpoints (unadorned `--version` first, whoami coverage check, `isError` before `structuredContent`, "empty or truncated → narrow once and retry") and feedback loops. It is not 5 because the top-level flow is interleaved with policy digressions (update notices, MCP/CLI dual paths, launcher recovery) that make the main sequence harder to follow linearly; it is above 3 because checkpoints are explicit and pervasive rather than implicit.

4 / 5

Progressive Disclosure

The three reference files (references/skill-updates.md, references/windows-shells.md, references/windows-launcher.md) all exist, are one level deep (they link back to SKILL.md, not to further files), and are well signaled with conditional read triggers ("read only if invocation fails", "Read only for CLI commands in PowerShell or Git Bash on Windows"). It is not 5 because substantial self-contained policy content (the runtime-update routes and skill-update handling) is inlined in SKILL.md when it could be split out the way the Windows and update guides already are, diluting the overview.

4 / 5

Total

16

/

20

Passed

Description

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

This is a strong description: it states concrete capabilities, names its mechanism (Qodo managed tools via MCP/CLI), gives an explicit "Use when" clause, and supplies an unusually rich set of natural trigger phrases. Its only weakness is that several trigger phrases (e.g., "where is X defined") are generic enough to overlap with local code-search skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — "Understand how code works, how a change was done before, and which repos are coupled" plus four task actions ("answer a question, plan a code change, debug a regression, or scope a fix") and the mechanism ("using Qodo managed tools through MCP or the CLI"), giving comprehensive coverage. It is not a 4 because the actions cover the full task space (questions, planning, debugging, scoping) rather than leaving minor gaps.

5 / 5

Completeness

Both parts are explicit: the "what" ("Understand how code works... using Qodo managed tools through MCP or the CLI") and a literal "Use when" clause ("Use when a task needs to understand a codebase, its history, or how its repos relate") followed by concrete trigger phrases. This is a direct match to the 5 anchor example's structure; the "when" is not merely present but concrete and multi-phrased, ruling out 4.

5 / 5

Trigger Term Quality

It includes ten natural phrases users would actually say — "how does X work", "where is X defined", "who changed X", "why did X regress / when did it break", "has this been fixed before", "how did we solve X" — plus situational triggers ("a repo you don't have checked out or work spanning repos"). This matches the comprehensive synonym-and-variation coverage of the 5 anchor (e.g., "PDF files, PDFs, forms, .pdf"); the 4 anchor requires that natural terms be missing, and none are.

5 / 5

Distinctiveness Conflict Risk

The Qodo managed-tools niche and the "repo you don't have checked out" / cross-repo scope are distinct, but very common phrases like "where is X defined" and "how does X work" would also naturally trigger local code-exploration or code-review skills, creating minor overlap risk with closely related skills. It is not 5 because those generic code-comprehension triggers lack a qualifier tying them uniquely to this skill; it is well above 3 because the tooling and cross-repo framing carve out a clear niche.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

qodo-ai/qodo-skills

Path

antigravity-plugins/qodo/skills/qodo-codebase-wisdom/SKILL.md

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.