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.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

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.

A well-structured, highly actionable skill body with a clear workflow, concrete templates, and an explicit validation checklist. Weakest only in minor conciseness flavor and an implicit rather than spelled-out error-recovery loop.

Suggestions

Tighten the Overview/Narrative Arc framing prose (e.g. 'A great tour is a narrative...') to assume Claude's competence and earn back token budget.

Make the validate→fix→retry feedback loop explicit in step 5 (e.g. 'If a path or line fails verification, fix or skip the step, then re-run the checklist').

Consider moving the Personas and Anti-Patterns tables into a reference file referenced one level deep to further reduce inline weight.

DimensionReasoningScore

Conciseness

Mostly lean with tight tables and bullets and no padding of basic concepts, but carries light framing flavor ('A great tour is a narrative — a story told to a specific person...') that could be trimmed, placing it just below the fully-efficient anchor.

4 / 5

Actionability

Fully executable guidance: a complete copy-paste tour JSON template with $schema, concrete step-type examples ('{"file": "src/auth.ts", "line": 42, ...}'), plus step-count, SMIG formula, and validation checklist covering the common cases.

5 / 5

Workflow Clarity

Clear five-step sequence (Discover → Infer → Read files → Write → Validate) with an explicit validation checklist and the 'Every file path and line number must be verified' checkpoint, but the validate→fix→retry feedback loop is not spelled out as a loop.

4 / 5

Progressive Disclosure

No bundle files exist; the body is well-organized into clearly headed sections with one-level-deep, cleanly signaled cross-references and no nested references, though some larger tables (personas, anti-patterns) could plausibly live in separate reference files.

4 / 5

Total

17

/

20

Passed

Description

95%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, specific description that clearly states both the artifact produced and when to invoke the skill, with comprehensive natural trigger terms and a distinct niche. The only minor gap is that the 'what' is conveyed as one action with attributes rather than a list of multiple concrete actions.

DimensionReasoningScore

Specificity

Names the domain and several concrete qualities — 'persona-targeted, step-by-step walkthroughs that link to real files and line numbers' — but centers on a single action (create) with descriptive attributes rather than a list of distinct actions, so it sits just below the comprehensive-coverage anchor.

4 / 5

Completeness

Explicitly answers both what ('persona-targeted, step-by-step walkthroughs that link to real files and line numbers') and when ('Use when the user asks to create...', 'Trigger for: ...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms including synonyms and the file extension: 'create a tour, onboarding tour, architecture tour, PR review tour, explain how X works, vibe check, RCA tour, contributor guide' plus '.tour'.

5 / 5

Distinctiveness Conflict Risk

Clear niche around CodeTour .tour files with distinct, specific triggers; minimal conflict risk, though 'explain how X works' is mildly generic it is anchored to the tour context.

5 / 5

Total

19

/

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.

Validation16 / 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.