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 genuinely actionable, well-validated read-only investigation guidance with excellent conditional references and concrete examples. Its main cost is density: a long inline runtime-update policy block, some repetition around version probing, and fragmented section ordering that makes the true execution sequence harder to follow than it needs to be.

Suggestions

Move the runtime-update contingency detail (upgrade routes, channel latest-2 recovery, checksum-pinned installer policy) into a reference file like references/runtime-updates.md, keeping only the unadorned version probe and minimum-version requirement inline — this would address both conciseness and progressive disclosure.

Consolidate the version-probe/update instructions that currently repeat across 'Runtime compatibility gate', 'Quick start', and 'Configuration' into a single authoritative location, and reorder so Preflight (auth, repo resolution) appears before the Quick start commands to make the true execution sequence linear.

Add one concrete `--args-file` example (writing complete UTF-8 JSON without a BOM) to the Quick start or Execution section so the structured-input guidance is as copy-paste ready as the other commands.

DimensionReasoningScore

Conciseness

Mostly efficient — the routing table, "Narrow, then fetch", Examples, and Deliver sections are tight and vendor-specific with no padding about concepts Claude already knows — but the ~25-line "Runtime compatibility gate" is dense conditional policy prose (update routes, channel recovery, checksum-pinned installers) that would be significantly tightened or moved to a reference, and version-probe/update instructions repeat across Runtime gate, Quick start, and Configuration. Not a 4 because the dense policy block is more than a minor trim; not a 2 because the bulk of the body earns its place.

3 / 5

Actionability

The Quick start block gives concrete executable commands with exact flags, the routing table maps task to tool group with representative tool names, and the worked Examples show full command sequences with realistic cited outputs. Not a 5 because the skill itself hedges that tool names are "illustrative, not guaranteed current" (requiring a verification step before use), and `--args-file` usage is directed but never shown; not a 3 because the commands and recovery paths are genuinely executable once verified.

4 / 5

Workflow Clarity

A clear sequence exists (choose execution path → version probe → preflight auth/catalog → resolve repo → route to tool group → narrow then fetch → deliver) with explicit validation checkpoints (unadorned `--version` first, check `isError` before `structuredContent`, numbered Preflight) and a real feedback loop ("Empty or truncated: true → narrow once and retry" before concluding; rerun the version probe after one update attempt). Not a 5 because the ordering must be assembled from scattered sections — Preflight appears after Quick start, the sandbox auth diagnostic is buried inside it, and the runtime gate's branch logic is hard to follow; not a 3 because checkpoints and error-recovery loops are explicit throughout.

4 / 5

Progressive Disclosure

The three bundle references (references/skill-updates.md, references/windows-shells.md, references/windows-launcher.md) all exist, are exactly one level deep, and are clearly signaled with load conditions ("before the first call", "only if invocation fails", "For user-requested updates") — exemplary conditional disclosure. Not a 5 because the runtime-update policy contingency sits inline in the main body rather than being split out the way the Windows and update-procedure content is, leaving the ~240-line body heavier than an overview.

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 and explicitly states both what the skill does and when to use it, backed by an unusually rich set of natural trigger phrases. The only weaknesses are minor: task-level rather than tool-level action specificity, and slight trigger overlap with local code-exploration workflows.

DimensionReasoningScore

Specificity

Lists several concrete task-level actions — "answer a question, plan a code change, debug a regression, or scope a fix" plus "how code works", "how a change was done before", and "which repos are coupled" — but stops short of enumerating the underlying tool capabilities (search, grep, read-file, blame, PR history, cross-repo relations), leaving minor coverage gaps. Not a 3 because well more than 1-2 concrete actions are named; not a 5 because the actions are task-level rather than a comprehensive list of specific operations.

4 / 5

Completeness

Explicitly answers both parts: the "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 the "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. This is a direct match for the score-5 anchor; a 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural phrases users would actually say: "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" — ten trigger variants spanning question, planning, debugging, and scoping scenarios. This matches the top anchor's standard of synonyms and variations; nothing obvious is missing.

5 / 5

Distinctiveness Conflict Risk

The Qodo-managed-tools framing and the "repo you don't have checked out or work spanning repos" scoping establish a clear niche, but generic triggers like "where is X defined" and "how does X work" would also fire for local repos where local exploration tools are more appropriate, creating minor overlap with closely related code-exploration skills. Not a 5 because of that overlap risk; not a 3 because the deployment context (MCP/CLI, cross-repo, not-checked-out) meaningfully narrows 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

kiro-power/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.