CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-tour

Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests. Use when the user asks for a code tour, onboarding walkthrough, PR tour, or an explanation of how a subsystem works.

Quality

92%

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

96%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 excellent single-file skill body: lean, concrete, and validated. The workflow has explicit verification checkpoints, every step type has executable JSON examples, and the `ref` section captures non-obvious failure modes. The only structural improvement would be moving the Step Types catalog to a reference file.

DimensionReasoningScore

Conciseness

Lean and dense throughout: no padding, no explaining concepts Claude already knows, compact tables for personas and anti-patterns, and the `ref` section teaches genuinely non-obvious failure behavior ('the editor could not be opened because the file was not found'). Only trivial repetition ('Never guess line numbers' vs. the validate checklist) — fits anchor 5 slightly better than 4.

5 / 5

Actionability

Fully executable: concrete JSON snippets for every step type (directory, file+line, selection, pattern, URI, content), a deterministic output path pattern (`.tours/<persona>-<focus>.tour`), persona/depth tables, and a complete copy-paste example tour with `$schema`. Matches anchor 5's 'copy-paste ready, covers the common cases'.

5 / 5

Workflow Clarity

Clear five-step sequence (Discover → Infer reader → Verify anchors → Write → Validate) with an explicit validation checklist in step 5 (paths exist, line/selection valid, first step anchored, `ref` revision contains every file) plus separate `ref` verification guidance. Validation checkpoints are present, so the destructive/batch cap does not apply; matches anchor 5.

5 / 5

Progressive Disclosure

Well-organized single file with clear section headers and no external references needed (no references/, scripts/, or assets/ exist). The ~60-line Step Types catalog is bulk reference-style material that could be split into a separate file, which keeps it at anchor 4 ('good structure, minor organization gaps') rather than 5.

4 / 5

Total

19

/

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: third-person voice, concrete artifact and qualifiers, explicit 'Use for' and 'Use when' trigger clauses with natural phrasing. Only minor gaps — a single dominant verb for specificity and a few missing colloquial trigger variants.

DimensionReasoningScore

Specificity

Names the concrete artifact ('Create CodeTour `.tour` files') with specific qualifiers ('persona-targeted, step-by-step walkthroughs with real file and line anchors'), but centers on a single verb rather than listing several distinct actions. Fits anchor 4 — specific with minor gaps — better than 5, and clearly above the 1-2-action coverage of anchor 3.

4 / 5

Completeness

Clearly answers 'what' (create persona-targeted .tour walkthroughs with real file and line anchors) and 'when' with two explicit trigger clauses: 'Use for onboarding tours, architecture walkthroughs, PR tours...' and 'Use when the user asks for a code tour, onboarding walkthrough, PR tour...'. This matches the anchor-5 example structure with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural coverage: 'onboarding tours, architecture walkthroughs, PR tours, RCA tours', "explain how this works", 'code tour', and 'onboarding walkthrough' are phrases users would actually say. A few natural variants ('walk me through the code', 'how does X work', '.tour files') are missing, matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (CodeTour `.tour` artifacts) with distinct triggers ('code tour', 'PR tour', '.tour'). The 'explain how this subsystem works' phrasing slightly overlaps general explanation requests, but the 'structured' / reusable-artifact framing in both trigger sentences keeps conflict risk minimal, matching anchor 5.

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

skills/code-tour/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.