CtrlK
BlogDocsLog inGet started
Tessl Logo

code-tour

Use when the user asks to create a CodeTour .tour file — persona-targeted, step-by-step walkthroughs that link to real files and line numbers. Trigger for: create a tour, onboarding tour, architecture tour, PR review tour, explain how X works, vibe check, RCA tour, contributor guide, or any structured code walkthrough request.

76

Quality

95%

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

The canonical home for this skill is code-tour in alirezarezvani/claude-skills

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 exceptionally lean and actionable skill body: a numbered workflow with a real validation checklist, concrete JSON examples for every step type, and no filler or assumed-knowledge padding. The only structural criticism is that everything lives in one file, which is acceptable for a skill consumed in a single pass.

DimensionReasoningScore

Conciseness

The body is dense with compact tables and contains no explanation of concepts Claude already knows — it only adds genuinely novel information (schema URL, .tours/ location, SMIG formula, the blank-first-step VS Code gotcha). Every token earns its place.

5 / 5

Actionability

Fully actionable: a copy-paste JSON skeleton with $schema and ref fields, the exact '.tours/<persona>-<focus>.tour' filename convention, concrete JSON snippets for every step type, step-count ranges per depth, and the SMIG description formula. As an instruction-only skill, this guidance is fully executable.

5 / 5

Workflow Clarity

A clear five-step sequence (Discover -> Infer intent -> Read files -> Write -> Validate) with an explicit validation checklist ('Every file confirmed to exist', 'Every line verified by reading') and error-recovery guidance in the anti-pattern table ('Hallucinated files — If it doesn't exist, skip the step'). The skill is read-only, so no destructive-operation cap applies.

5 / 5

Progressive Disclosure

Sections are well-organized with clear headers and easy navigation, and the skill is appropriately self-contained (no bundle files exist). At ~135 lines with the 10-persona table, step types, and anti-patterns all inlined, there are minor organization gaps versus the ideal overview-plus-references split, matching the good-structure anchor.

4 / 5

Total

19

/

20

Passed

Description

91%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 that clearly states what the skill produces and when to use it, with an unusually rich set of natural trigger phrases. Its only weaknesses are the single-action scope of the 'what' statement and a couple of broad triggers that could overlap with adjacent code-explanation skills.

DimensionReasoningScore

Specificity

The description concretely names the deliverable ('create a CodeTour .tour file') and its specific properties ('persona-targeted, step-by-step walkthroughs that link to real files and line numbers'), but it lists a single action rather than several specific actions, so it falls between the comprehensive (5) and 1-2-action (3) anchors.

4 / 5

Completeness

It explicitly answers both 'what' (create persona-targeted, step-by-step .tour walkthroughs with file/line anchors) and 'when' ('Use when the user asks to create a CodeTour .tour file... Trigger for: ...') with concrete trigger phrases, mirroring the anchor-5 example structure.

5 / 5

Trigger Term Quality

The trigger list covers comprehensive natural phrases users would say — 'create a tour, onboarding tour, architecture tour, PR review tour, explain how X works, vibe check, RCA tour, contributor guide' — plus the '.tour' file extension, matching the synonym-inclusive top anchor.

5 / 5

Distinctiveness Conflict Risk

CodeTour is a distinct niche with a named artifact, but broad triggers like 'explain how X works' and 'contributor guide' could overlap with general code-explanation or onboarding skills, giving minor overlap risk per the anchor-4 description.

4 / 5

Total

18

/

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