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

82%

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

Quality

Content

86%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 body is a tight, fully executable reference of editor-specific show-file commands with a clear one-by-one walkthrough flow and good structure; only minor tightening and error-handling detail are lacking.

Dimension	Reasoning	Score
Conciseness	Lean body with no over-explanation of concepts Claude already knows; only minor redundancy in the opening paragraph ("as in examples below") that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready, executable CLI commands for five editors with exact syntax, plus a concrete failure fallback ('tell the user to install the corresponding CLI tool').	5 / 5
Workflow Clarity	Clear sequence (ask editor if unspecified -> use the matching show-file command -> proceed one by one, waiting for the user each time) with an explicit 'wait for user' checkpoint; not a 5 because error-recovery beyond the install hint is left implicit.	4 / 5
Progressive Disclosure	Under 50 lines with no external references needed; content is well-organized into per-editor subsections, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	18 / 20 Passed

Description

78%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 clearly states both purpose and trigger conditions with concrete, user-natural phrasing, but leans on second-person voice and repeats a small set of actions rather than giving comprehensive coverage.

Suggestions

Rewrite in third person ('Walks through code or text files in an editor to explain code or show changes') to remove the second-person voice that lowers specificity.

Consolidate the repeated 'walk through / point at / show' phrasing into a single crisp action list to avoid padding.

Add a couple of trigger synonyms (e.g., 'review changes', 'navigate to line') to broaden natural-term coverage.

Dimension	Reasoning	Score
Specificity	Names several concrete actions ("walk through files", "explain how some code works", "show the user what changes you made", "point at various files... at specific line numbers"), but they are repetitive rather than comprehensive; reduced by 1 for pervasive second-person voice ("you", "you would typically").	3 / 5
Completeness	Explicitly answers both what (walk through files in an editor at line numbers to explain code or show changes) and when ("Use this when user wants you to walk through...") with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Good coverage of natural phrases users would say ("walk through", "explain how some code works", "show... changes", "follow along"), though a few synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The editor-navigation-with-line-numbers niche is mostly distinct, with only minor overlap risk against generic code-explanation skills.	4 / 5
	Total	16 / 20 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: c35a135

Reviewed: about 13 hours 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.