code-walk-thru

Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/workflow/skills/code-walk-thru/SKILL.md

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise, actionable, and well-organized for a simple editor-walkthrough skill, with copy-paste-ready commands and a clear behavioral sequence. The only gap is the lack of explicit validation checkpoints in the walk-through workflow.

Suggestions

Add an explicit checkpoint that confirms a file actually opened in the editor before moving on, rather than relying on the user's next message as the sole signal.

Optionally note how to verify the line-number argument was accepted (some editors ignore out-of-range line numbers silently) so mismatches are caught.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanations of concepts Claude already knows; every line (editor command listings, the one-by-one rule) earns its place.	3 / 3
Actionability	It provides concrete, copy-paste-ready commands per editor ('code --goto <file_path>:<line_number>', 'pycharm --line <line_number> <file_path>', 'vim +42 blah.py', etc.), which are fully executable.	3 / 3
Workflow Clarity	The one-by-one sequence and 'wait for the user to say something before moving on' rule are present, plus failure handling ('if any of these fail tell the user to install the corresponding CLI tool'), but explicit validation checkpoints for whether a file opened successfully before proceeding are only implicit.	2 / 3
Progressive Disclosure	This is a simple, under-50-line single-task skill with no external references needed, organized into clearly labeled per-editor sections, which meets the rubric's bar for a 3.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 has an explicit trigger clause and concrete actions, but its second-person voice and slightly niche, incomplete trigger coverage limit specificity and distinctiveness. It is functional but would benefit from tighter, more natural phrasing.

Suggestions

Rewrite in third person (e.g. 'Walks through code/text files in the user's editor to explain code or show changes') to recover the specificity point lost to the voice penalty.

Add common natural trigger variations users would actually say, such as 'explain this code', 'show me the changes', or 'open these files at specific lines'.

Tighten the redundant second sentence about pointing at files/line numbers, which repeats the first.

Dimension	Reasoning	Score
Specificity	Concrete actions are named ('walk through (code or text) files', 'explain how some code works', 'show the user what changes you made', 'point at various files possibly at specific line numbers'), which would normally warrant a 3, but the second-person voice ('You would typically use this') triggers the rubric's 1-point specificity penalty.	2 / 3
Completeness	It contains an explicit 'Use this when...' trigger clause and describes what the skill does, answering both 'what' and 'when' clearly.	3 / 3
Trigger Term Quality	Phrases like 'walk through files', 'explain how some code works', and 'follow along' are relevant, but coverage is not comprehensive and 'in a EDITOR' is awkward jargon rather than natural user phrasing.	2 / 3
Distinctiveness Conflict Risk	The editor walk-through with line numbers is fairly niche, but 'walk through code files to explain how code works' could still overlap with general code-reading or explanation skills.	2 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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: pchalasani/claude-code-tools
Path: plugins/workflow/skills/code-walk-thru/SKILL.md
Commit: 45ee0e2

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.