CtrlK
BlogDocsLog inGet started
Tessl Logo

codebase-walkthrough

Deep codebase walkthrough before implementation — trace the full flow, explain architecture, and build understanding.

61

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./devflow-plugin/skills/codebase-walkthrough/SKILL.md

The canonical home for this skill is codebase-walkthrough in AndreJorgeLopes/devflow

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 a well-structured, actionable walkthrough process with clear sequencing, a validation checklist, and explicit verification feedback loops. It is slightly verbose in the diagram-rendering instructions but otherwise efficient.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence, but a few explanatory passages — e.g. 'a markdown `![](x.png)` embed only shows clickable text in the Claude app' and the lengthy diagram-rendering instructions in Step 2 — could be trimmed; sits noticeably above anchor 3 but short of fully lean anchor 5.

4 / 5

Actionability

Concrete executable commands are present (`recall(...)`, `/devflow:render-diagram`, `devflow visualizations render <path>.excalidraw`, `retain(...)`) with a specific file path, but Steps 3-4 are descriptive guidance rather than commands, leaving minor gaps; not a 5 because common-case coverage is not fully copy-paste ready.

4 / 5

Workflow Clarity

An 8-step sequence is clearly laid out with an explicit 'Walkthrough Quality Checklist' validation gate, an assumption-verification feedback loop ('If you can't verify, say I need to verify this'), and an explicit checkpoint ('Ask the user if anything is unclear before proceeding'), matching the anchor for clear sequence with validation and checklists.

5 / 5

Progressive Disclosure

A single self-contained SKILL.md with well-organized section headers and a clearly signaled reference to the render-diagram skill; per the guideline, a skill with no need for external references can score 5 with well-organized sections, and no nested/deep references are present.

5 / 5

Total

18

/

20

Passed

Description

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

The description clearly states what the skill does but omits an explicit trigger/when clause, which limits its completeness score. Trigger terms are reasonably natural and the niche is fairly distinct.

Suggestions

Add an explicit 'Use when...' clause to the description, e.g. 'Use when the user wants to understand a codebase area before implementation or review.'

Concretize the actions beyond abstract verbs — name deliverables like 'a rendered end-to-end flow diagram and a prioritized files-to-read list'.

Add natural trigger synonyms such as 'orient me in the codebase' or 'explain how this works' to broaden discoverability.

DimensionReasoningScore

Specificity

The description names three actions ('trace the full flow, explain architecture, and build understanding') but they are abstract process actions rather than concrete capabilities, fitting the 'names domain and 1-2 concrete actions' anchor; not a 4 because coverage is not comprehensive.

3 / 5

Completeness

It gives a clear 'what' (deep walkthrough, trace flow, explain architecture) but the description lacks any explicit 'Use when...' trigger clause — that guidance lives only in the body, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

'codebase walkthrough', 'before implementation', and 'architecture' are natural phrases a user might say; good coverage though a few synonyms (e.g. 'understand the code', 'orient me') are missing, so it sits noticeably above anchor 3 but short of comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

'Deep codebase walkthrough before implementation' carves a clear niche distinct from implementation/debugging skills with minor overlap risk against general explain-code skills; not a 5 because 'explain architecture' could overlap with broader explanation skills.

4 / 5

Total

14

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
AndreJorgeLopes/devflow
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.