CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reading-source-code

Workflow for reading repository code with `exploreRepo` and `discoverRepos`, covering when to ask which repositories to search and how to report findings and errors. Load it before answering from repository code.

Quality

94%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary instruction-only skill body: lean, non-obvious guidance with concrete examples, explicit checkpoints, and error-recovery loops throughout. There is nothing meaningful to trim or restructure.

DimensionReasoningScore

Conciseness

Lean and efficient with zero padding: every paragraph delivers non-obvious, environment-specific guidance ('Each repository is searched separately, so covering the whole set is slow and rarely needed') and nothing explains concepts Claude already knows.

5 / 5

Actionability

Fully actionable for an instruction-only skill: quoted request patterns ('which repos mention X'), sample reports ('Three files reference `OrderStatus`'), concrete error classes ('a missing path, a read-only error, a per-command limit'), and specific fallbacks ('try `grep` before saying nothing matched') cover the common cases.

5 / 5

Workflow Clarity

Each rule is unambiguous and includes checkpoints and feedback loops: user confirmation before batch repository scanning, a `grep` fallback before reporting no-match, and fix-and-retry on command failure ('fix it and retry: the error says how').

5 / 5

Progressive Disclosure

Under 50 lines with well-organized bold-headed sections and no bundle files; command mechanics are cleanly delegated in one clearly signaled step ('The `exploreRepo` description covers the mounts, the commands and the `search` locator').

5 / 5

Total

20

/

20

Passed

Description

87%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: it names both tools, states what the workflow covers, and gives an explicit load trigger in third-person voice. Its only weakness is keyword coverage lacking common synonyms such as 'codebase' or 'source code'.

DimensionReasoningScore

Specificity

Lists several concrete action areas — 'reading repository code with `exploreRepo` and `discoverRepos`', 'when to ask which repositories to search', 'how to report findings and errors' — with two named tools, but stops short of enumerating the sub-actions each covers, so not comprehensive.

4 / 5

Completeness

Explicitly answers both what ('Workflow for reading repository code with `exploreRepo` and `discoverRepos`, covering when to ask which repositories to search and how to report findings and errors') and when ('Load it before answering from repository code'), so the missing-trigger cap does not apply.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('repository code', 'repositories to search', 'findings'), but common variations users would say — 'codebase', 'source code', 'find/locate' — are missing, so it falls just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear niche tied to the two named tools (`exploreRepo` and `discoverRepos`) and repository-reading behavior; distinct triggers make overlap with other skills minimal.

5 / 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

lightdash/lightdash

Path

packages/backend/src/ee/services/ai/skills/builtInSkills/reading-source-code/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.