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

78%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 with exact commands, worked examples, explicit stop conditions, and a clean bundle structure of well-signaled one-level references. Its main cost is density: the runtime-update policy and delivery-style sections are longer than needed and some instructions repeat across sections. Tightening those would raise token efficiency without losing guidance.

Suggestions

Consolidate the version-probe and provenance instructions, which currently appear in 'Runtime compatibility gate', 'Quick start', and 'Configuration', into one place and cross-reference it.

Compress the ~25-line runtime-update policy paragraph into a short decision table (observed version → approved route → stop conditions); the prose restates the same constraints multiple times.

Trim the 'Deliver' section: keep the answer→context→implication structure and citation rules, but cut the sentence-pattern list and the repeated 'do not overclaim' reminders to one line each.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and the routing table and examples are tight, but it is ~240 lines with clear tightening opportunities: the ~25-line "Runtime compatibility gate" update-policy prose ("Choose one deployment-approved upgrade route... Propose `qodo update --channel latest-2` only for that verified recovery route"), the long "Deliver" section with sentence patterns, and version-probe/provenance instructions repeated across "Runtime compatibility gate", "Quick start", and "Configuration". This matches 'mostly efficient but could be tightened' rather than the minor-trims level of anchor 4, and is far from the padded-explanations level of anchor 2.

3 / 5

Actionability

Commands are copy-paste ready with exact flags: the Quick start block (`qodo read codebase grep --repo owner/repo --pattern "chargeCard" --json`), the launcher fallback `"${QODO_HOME:-$HOME/.qodo}/bin/qodo"`, `--args-file`/`--context-file` conventions, and worked examples that resolve real questions (grep → read-file with `--start-line 120 --limit-lines 40`). A built-in verification command (`qodo read tools <group> --json`) covers the common cases, matching the fully-executable anchor rather than anchor 4's 'minor gaps'.

5 / 5

Workflow Clarity

There is a real sequence with explicit checkpoints: version probe first ("run `<qodo> --version`... exactly as shown"), numbered Preflight steps (auth/catalog, resolve repo with never-guess-a-slug rules), and feedback loops ("Empty or `truncated: true` → narrow once and retry", "refresh once with `qodo tools --refresh` and retry", "rerun the unadorned version probe"). It stays at anchor 4 rather than 5 because the workflow is scattered across many sections (Choose execution path → Runtime gate → Quick start → Preflight → Route → Narrow → Deliver) with no single ordered checklist, leaving some checkpoint ordering implicit.

4 / 5

Progressive Disclosure

SKILL.md is an overview with three small, conditionally-signaled, one-level-deep references that all exist in the bundle: "[manual-update procedure](references/skill-updates.md)", "[shell guidance](references/windows-shells.md)" (before the first call), and "[launcher recovery](references/windows-launcher.md)" (only if invocation fails); none of the reference files nest further references. This matches the clear-overview anchor with content appropriately split.

5 / 5

Total

17

/

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: concrete capabilities, an explicit 'Use when' clause with ten natural trigger phrases, and a well-scoped niche around codebase/history/cross-repo understanding via Qodo tools. It uses third-person imperative voice and avoids padding. The only weakness is mild overlap risk with generic code-exploration skills on the broadest trigger phrases.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — "Understand how code works", "how a change was done before", "which repos are coupled", "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 stops short of anchor 5 because the actions are stated at a capability level rather than a comprehensive set of concrete operations, but it clearly exceeds the 1–2-actions level of anchor 3.

4 / 5

Completeness

Both halves are explicit: 'what' is stated up front ("Understand how code works, how a change was done before, and which repos are coupled... using Qodo managed tools through MCP or the CLI") and 'when' is stated with a dedicated "Use when a task needs to understand a codebase, its history, or how its repos relate" clause plus concrete trigger phrases and scope qualifiers ("a repo you don't have checked out or work spanning repos"). This mirrors the anchor-5 example structure exactly, so it is not the 4 anchor where 'when' is present but less explicit.

5 / 5

Trigger Term Quality

It quotes ten natural trigger phrases users would actually say — "how does X work", "where is X defined", "who changed X", "plan the change for X", "why did X regress / when did it break", "has this been fixed before", "how did we solve X" — plus keyword-style variants ("explain this service", "which repos depend on X"). This matches the comprehensive anchor including synonyms and rephrasings; nothing natural is missing for this domain.

5 / 5

Distinctiveness Conflict Risk

The niche (Qodo-managed codebase/history/cross-repo retrieval) is distinct and most triggers ("who changed X", "which repos depend on X", "has this been fixed before") are unlikely to fire the wrong skill. Broad phrases like "how does X work" and "explain this service" do overlap with generic local code-exploration skills, keeping it at anchor 4 rather than the minimal-conflict anchor 5; it is clearly above anchor 3's 'could still overlap with similar skills' since the coupling/history/cross-repo framing and tool attribution disambiguate it.

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

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.