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

85%

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 delivers highly actionable, executable guidance with a clear investigation workflow, strong validation checkpoints, and well-integrated one-level references. Its main weakness is the verbose, tangled runtime-update policy section, which hurts token efficiency and would be better split into a reference file.

Suggestions

Move the runtime-update policy (QODO_UPDATE_BASE_URL handling, 1.x-to-2.x migration routes, latest-2 recovery) into a reference file like references/runtime-updates.md, keeping only the unadorned version probe and the 2.0.0 minimum requirement inline.

Tighten the repeated version/identity/catalog-check instructions spread across 'Runtime compatibility gate', 'Preflight', and 'Configuration' into one consolidated readiness section to reduce duplicated conditions.

Clarify the runtime-update branch by presenting the upgrade routes as a short decision list (route → precondition → command) instead of nested conditional prose.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no basic-concept padding), but the ~25-line runtime-update policy block (1.x-to-2.x routes, QODO_UPDATE_BASE_URL, channel recovery) repeats conditions across sections and embeds time-sensitive version numbers inline rather than in a reference or deprecation section. It is mostly efficient but could be meaningfully tightened, fitting the middle anchor rather than the noticeably-verbose one.

3 / 5

Actionability

Guidance is fully executable: a copy-paste Quick start with exact commands and flags, a precise fallback invocation ("${QODO_HOME:-$HOME/.qodo}/bin/qodo"), a tool-group routing table, a catalog-verification command, and three worked examples showing commands plus expected cited outputs. The illustrative tool names are explicitly handled by instructing verification via `qodo read tools`.

5 / 5

Workflow Clarity

The mainline workflow is clearly sequenced (choose path → version gate → preflight auth and repo resolution → route to tool group → narrow then fetch → deliver) with explicit validation checkpoints (unadorned `--version` probe, `whoami`, catalog check) and feedback loops (empty/truncated → narrow once and retry; MT-TOOL-LOOP → stop and change approach). It falls short of the top anchor because the runtime-update branch's nested conditionals create minor gaps in the overall sequence.

4 / 5

Progressive Disclosure

All three bundle references (skill-updates.md, windows-shells.md, windows-launcher.md) exist, are one level deep, clearly signaled, and conditionally loaded ("launcher recovery only if invocation fails"), matching the actual bundle structure. The gap from the top anchor is the inline runtime-update policy block, which is content that belongs in a reference file like the others rather than in SKILL.md.

4 / 5

Total

16

/

20

Passed

Description

91%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 strong description: it explicitly states both capability and usage triggers, with an unusually thorough set of natural trigger phrases spanning question-answering, planning, debugging, and impact analysis. Its only weaknesses are capability-level lead verbs instead of concrete operations and some overlap with generic code-exploration triggers.

DimensionReasoningScore

Specificity

The description names the domain and several concrete task actions ("answer a question, plan a code change, debug a regression, or scope a fix, using Qodo managed tools through MCP or the CLI"), with only minor coverage gaps. It falls just below the comprehensive anchor because lead verbs like "Understand how code works" describe capabilities rather than fully concrete operations.

4 / 5

Completeness

It explicitly answers both "what" (understand how code works, prior changes, and repo coupling via Qodo managed tools) and "when" ("Use when a task needs to understand a codebase, its history, or how its repos relate") with concrete trigger phrases, matching the top anchor rather than the merely-adequate one.

5 / 5

Trigger Term Quality

It includes a comprehensive list of 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" — covering synonyms and variations across question, planning, debugging, and impact scenarios.

5 / 5

Distinctiveness Conflict Risk

The Qodo tooling framing and "especially for a repo you don't have checked out or work spanning repos" carve out a clear niche, but generic triggers like "where is X defined" and "explain this service" overlap with local code-exploration skills, leaving minor conflict risk.

4 / 5

Total

18

/

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

packages/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.