CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

83%

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

82%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 content is a well-structured, highly actionable guide with concrete JSON examples for every step type and a strong validation-oriented workflow. Minor tightening of the `ref` section and an explicit retry loop on validation failure would lift it further.

Suggestions

Add an explicit "if validation fails, fix the anchor and re-verify" retry loop to the Validate step to reach the 5 anchor for workflow clarity.

Tighten the `ref` field section — the core trap can be stated in fewer tokens without losing the gotcha.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but the `ref` field section is a fairly lengthy explanation; while justified by a non-obvious gotcha, it could be tightened slightly, placing it just below the lean 5 anchor.

4 / 5

Actionability

Every step type ships with a complete, copy-paste-ready JSON example, the path template `.tours/<persona>-<focus>.tour` is concrete, and the full example tour covers the common cases end to end.

5 / 5

Workflow Clarity

A clear five-step sequence (Discover → Infer reader → Verify anchors → Write → Validate) with explicit validation checklists in steps 3 and 5, but it lacks an explicit validate→fix→retry feedback loop, so it sits below the 5 anchor.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers and no nested references; content is appropriately self-contained, though the file is longer than the simple-skill threshold that would warrant a 5 on structure alone.

4 / 5

Total

17

/

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.

The description is strong: it clearly states the artifact produced, the distinguishing characteristics, and explicit trigger conditions with natural phrasing. Its only weakness is modest overlap risk with adjacent onboarding/explanation skills and a single-verb action set.

Suggestions

Add the `.tour` file extension as an explicit trigger term to round out keyword coverage.

Sharpen the boundary against `codebase-onboarding` by noting the tour-artifact requirement in the 'when' clause.

DimensionReasoningScore

Specificity

Names the domain (CodeTour `.tour` files) and a concrete action ("persona-targeted, step-by-step walkthroughs with real file and line anchors") plus several tour types, but the action set centers on one verb (create) with modifiers rather than multiple distinct operations, so it sits below the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers both what ("Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors") and when ("Use when the user asks for a code tour, onboarding walkthrough, PR tour, or an explanation of how a subsystem works") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ("code tour", "onboarding tour", "architecture walkthrough", "PR tour", "RCA tour", "explain how this works") with good synonym coverage, but omits the `.tour` extension and a few common variants, keeping it just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The CodeTour `.tour` artifact niche is distinct with clear triggers, but the "explain how this works" framing has minor overlap risk with related skills like `codebase-onboarding`.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.