CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

linear-walkthrough

Produces a structured, end-to-end linear walkthrough of an unfamiliar codebase by orchestrating parallel subagents across four phases — discovery, tracing, validation, and synthesis. Use when onboarding to a new repository, understanding execution paths from entry points, generating navigable codebase documentation, or needing fact-checked coverage of architecture, deployment, testing, and operations.

Quality

86%

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

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.

A well-engineered orchestration skill: the authoritative Mermaid procedure, explicit budgets, and verified one-level-deep references make it highly executable. The two fixable weaknesses are the duplicated procedure-authority directive and the unspecified validator count M.

Suggestions

State the procedure-authority directive once — either in the IMPORTANT callout or the Workflow paragraph — instead of repeating "execute steps in the exact order... including branches, decision points, and stop conditions" nearly verbatim in both places.

Define M in Phase 3 (e.g., "M equals N by default" or give the rule for choosing fewer validators), since the rotation and wrap-around logic depend on a value the diagram never supplies.

Trim the longest Mermaid node labels (e.g., SpawnValidators) by moving the per-agent input list into a shared "agent inputs" note or the referenced agent-instructions.md, which already enumerates these details.

DimensionReasoningScore

Conciseness

The body is dense and operational with zero concept explanations; the Mermaid diagram carries the procedure efficiently. Not a 5 because the "authoritative procedure / execute in exact order including branches, decision points, and stop conditions" directive is stated nearly verbatim twice (IMPORTANT callout and Workflow paragraph), and several node labels are verbose.

4 / 5

Actionability

Concrete throughout: exact artifact paths (walkthrough/coverage-plan.md, sections/walkthrough-section-{id}.md, validation/validation-report-{id}.md), numeric budgets (50k token read budget, 25k char file limit, 5k skeleton), and pointers to verified reference sections. Not a 5 because M (the validator count) is never assigned a value or derivation rule, leaving the rotation logic underspecified for an executor.

4 / 5

Workflow Clarity

The flowchart specifies exact sequencing, decision gates, a budget-recheck loop, a per-section correction loop, missing-section gap handling, and terminal states. Validation checkpoints are explicit (section existence, critical corrections, 25k size check, PENDING marker verification), satisfying the feedback-loop requirement for this batch operation.

5 / 5

Progressive Disclosure

The SKILL.md body holds the orchestration overview while detailed agent prompts (references/agent-instructions.md) and format templates (references/output-format.md) are one level deep and clearly signaled in the Resources section. Every section the body cites (Discovery/Tracing/Validation/Synthesis Agent Instructions, Coverage Plan Format, Entry Point Index Format, Walkthrough Section Format, Validation Report Format, Unified Walkthrough Format) was verified to exist in the referenced files.

5 / 5

Total

18

/

20

Passed

Description

83%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 with an explicit what/when pairing, third-person voice, and specific named phases. Trigger coverage is good but could add a few natural synonyms users say when asking for codebase comprehension.

DimensionReasoningScore

Specificity

"Produces a structured, end-to-end linear walkthrough" and "orchestrating parallel subagents across four phases — discovery, tracing, validation, and synthesis" list several specific actions and named phases. Not a 5 because it describes one core deliverable rather than enumerating multiple distinct concrete actions (cf. the PDF skill's extract/fill/merge/convert).

4 / 5

Completeness

The "what" is explicit ("Produces a structured, end-to-end linear walkthrough... orchestrating parallel subagents across four phases") and the "when" is an explicit "Use when" clause with four concrete trigger scenarios (onboarding, execution paths, documentation, fact-checked coverage).

5 / 5

Trigger Term Quality

Natural phrases like "onboarding to a new repository", "understanding execution paths from entry points", and "navigable codebase documentation" are present. Not a 5 because common user phrasings such as "explain this codebase" or "give me a tour of this repo" are missing.

4 / 5

Distinctiveness Conflict Risk

The linear-walkthrough/onboarding-documentation niche is distinct from related skills. Not a 5 because "understanding execution paths from entry points" could fire for a narrow single-function question where a full walkthrough is overkill, creating minor overlap with general code-exploration skills.

4 / 5

Total

17

/

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

Jamie-BitFlight/claude_skills

Path

.claude/skills/linear-walkthrough/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.