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

82%

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

67%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 a well-sequenced, highly actionable investigation workflow with strong validation checkpoints and clean one-level-deep references. Its main cost is density: procedural edge-case text (runtime updates, sandbox diagnostics, attribution rules) is inlined where it could be trimmed or split into references, taxing the token budget without aiding the common path.

Suggestions

Move the runtime-update recovery details (QODO_UPDATE_BASE_URL handling, 1.x-to-2.x migration routes, checksum-pinned installer procedure) into a reference file such as references/runtime-updates.md, keeping only the unadorned version probe and stop conditions inline in SKILL.md.

Consolidate the read-only/write-tool guardrail — currently repeated in Prerequisites, Instructions (Choose the execution path), Execution, and Guardrails — into a single authoritative section.

Trim the Deliver section's sentence-pattern list and formatting directives to two or three concrete examples, trusting Claude to adapt the attribution style from those.

DimensionReasoningScore

Conciseness

The body is operational rather than padded with concepts Claude already knows, but it is noticeably long (~240 lines) with tightening opportunities: the runtime-update gate's edge cases (QODO_UPDATE_BASE_URL, 1.x migration routes, checksum-pinned installers), the sandbox auth diagnostic, and the Deliver section's attribution rules are denser than needed, and the read-only emphasis repeats across Prerequisites, Instructions, Execution, and Guardrails. This fits "mostly efficient but could be tightened" rather than the padded anchor 2.

3 / 5

Actionability

The Quick start gives copy-paste-ready CLI commands, the routing table maps tasks to tool groups, and the Examples walk concrete query sequences. Minor gaps remain — placeholder repo slugs and the caveat that "the tool names below are illustrative, not guaranteed current" reduce copy-paste stability — so it sits at "mostly executable" rather than the fully-ready anchor 5, and well above the pseudocode anchor 3.

4 / 5

Workflow Clarity

There is a clear sequence (compatibility probe → preflight auth and repo resolution → route to tool group → narrow-then-fetch → deliver) with explicit validation checkpoints (unadorned `--version` first, `whoami`, `isError` check before `structuredContent`, verifying tool names before calls) and feedback loops ("narrow once and retry", "refresh once... and retry the check"). The tangled runtime-update conditionals and scattered section ordering are minor gaps, fitting anchor 4 rather than the fully checklisted anchor 5. The skill is read-only, so the destructive/batch validation cap does not apply.

4 / 5

Progressive Disclosure

The three references (skill-updates.md, windows-shells.md, windows-launcher.md) are real files, one level deep, and clearly signaled with conditional read triggers ("before the first call", "only if invocation fails"). However, the ~25-line runtime-update recovery block is content that belongs in a reference file and is inlined in SKILL.md, which matches "good structure; most content appropriately placed; minor organization gaps" rather than the cleanly split anchor 5.

4 / 5

Total

15

/

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 that clearly states what the skill does and when to use it, backed by an unusually thorough catalog of natural trigger phrases. Its only weaknesses are capability descriptions that stay one level above the concrete tool operations, and generic code-comprehension triggers that slightly overlap with local code skills.

DimensionReasoningScore

Specificity

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") with only minor gaps. It stays at the capability level rather than naming the concrete retrieval operations (grep, blame, PR search), so it does not reach the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both "what" ("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" ("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") with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Covers a comprehensive set of natural phrases users would actually say — "how does X work", "where is X defined", "who changed X", "explain this service", "what would changing X affect", "why did X regress / when did it break", "has this been fixed before" — including synonym variations. This matches the comprehensive-coverage anchor and is clearly above the good-but-missing-a-few anchor 4.

5 / 5

Distinctiveness Conflict Risk

The Qodo/remote-repo/cross-repo coupling niche is mostly distinct with clearly signaled tooling, but generic triggers like "how does X work" and "where is X defined" overlap with ordinary local code-exploration skills. This fits "mostly distinct; minor overlap risk with closely related skills" rather than the minimal-conflict anchor 5.

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

codex-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.