CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

learn-codebase

Prime a codebase by reading every source file in full. Use when starting work on a new or unfamiliar project, or when the user asks to "learn the codebase", "read the codebase", "prime", or "get up to speed".

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugin/skills/learn-codebase/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A short, single-purpose skill whose core instruction is concrete and executable, with good structure for its size. It loses points on padded motivational/meta text and on the absence of any coverage-verification step for what is inherently a batch operation across every file.

Suggestions

Trim non-actionable padding — 'This will help us build a deep understanding of the codebase we can work off of', 'This is critical and non negotiable', and the 'Note for Reviewers' section — so every remaining sentence is executable guidance.

Add a coverage verification step for the batch read (e.g., first enumerate the project's source files, then read them in order and confirm none were skipped), which would raise workflow clarity above the batch-operation cap of 3.

Define the scope of 'source file' concretely — including how to treat vendored, generated, or minified files and binary assets — so the instruction is unambiguous on real-world projects.

DimensionReasoningScore

Conciseness

The body is short and mostly instruction, but carries padding: "This will help us build a deep understanding of the codebase we can work off of", "This is critical and non negotiable", and the entire "Note for Reviewers" section add no executable guidance. Not 4 because the padding is more than minor trimmable instances; not 2 because the core directive and tool mechanics are still efficient and real.

3 / 5

Actionability

Gives concrete, executable guidance — "use the `Read` tool's `offset` and `limit` parameters to page through the file in chunks (e.g. `offset: 1, limit: 500`, then `offset: 501, limit: 500`)" — which is directly actionable without code. Not 5 because common cases are uncovered (what counts as a 'source file', how to treat vendored/generated/minified files); not 3 because the guidance given is concrete and executable, not pseudocode or high-level hints.

4 / 5

Workflow Clarity

The directive is stated as a single unambiguous action, but reading every source file is a batch operation and there is no verification checkpoint (e.g., enumerate files first, track coverage) confirming exhaustive completion, which caps this dimension at 3 per the rubric. Not 4 because a coverage checkpoint is entirely absent; not 2 because the instruction and paging mechanics are clearly and coherently stated.

3 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle), and is organized into a short main instruction plus a labeled section. Meets the simple-skill exception: well-organized sections with nothing inlined that belongs in a separate file.

5 / 5

Total

15

/

20

Passed

Description

78%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 well-formed description with an explicit what, an explicit when, and multiple natural quoted trigger phrases. Its only weakness is that the capability statement rests on a single action, leaving it less comprehensive than the strongest examples.

DimensionReasoningScore

Specificity

"Prime a codebase by reading every source file in full" names the domain and one concrete action, but offers nothing beyond that single action. It lists several specific actions (4) nor is it purely generic (2); it sits exactly at 'domain plus 1-2 concrete actions, not comprehensive'.

3 / 5

Completeness

Explicitly answers both: what ("Prime a codebase by reading every source file in full") and when ("Use when starting work on a new or unfamiliar project, or when the user asks to 'learn the codebase'...") with concrete trigger phrases. This matches the anchor-5 example structure; not 4 because the when-clause is already fully explicit rather than 'could be more specific'.

5 / 5

Trigger Term Quality

Includes natural quoted phrases users would say — "learn the codebase", "read the codebase", "prime", "get up to speed" — plus the scenario "starting work on a new or unfamiliar project". Not 5 because common variations like "explore the codebase", "onboarding", or "familiarize yourself with the codebase" are missing; not 3 because it goes well beyond 'some relevant keywords' by including multiple synonyms.

4 / 5

Distinctiveness Conflict Risk

The whole-codebase priming niche with distinct quoted triggers ("learn the codebase", "read the codebase", "prime") is mostly distinct from other skills. Not 5 because phrases like "get up to speed" and the new-project scenario could overlap with general onboarding or exploration skills; not 3 because the triggers are far more specific than the 'Works with document files' level of overlap.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

thedotmack/claude-mem

Path

plugin/skills/learn-codebase/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.