CtrlK
BlogDocsLog inGet started
Tessl Logo

hunk-review

Interacts with live Hunk diff review sessions via CLI. Inspects review focus, navigates files, hunks, and exact lines, reloads session contents, adds inline review comments, and paints attention marks on character ranges. Use when the user has a Hunk session running or wants to review diffs interactively.

73

Quality

90%

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

88%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 tight, executable CLI reference with strong command coverage, clear sequencing, and real validation/error-recovery guidance for its batch and destructive operations. Minor conciseness and progressive-disclosure refinements would round it out.

Suggestions

Tighten the prose in 'Guiding a review' and the attention-marks intro so the body stays lean.

Consider extracting the full command-signature reference into a references/ file, leaving SKILL.md as overview + worked examples.

DimensionReasoningScore

Conciseness

The body is dense, actionable reference material with no padding about concepts Claude already knows, though a few prose passages (e.g. the 'Guiding a review' narration guidance) could be trimmed slightly.

4 / 5

Actionability

Every command has a full signature plus copy-paste-ready examples covering the common cases — navigate to a line, add/apply comments, reload a diff, highlight a range — with concrete flags and values.

5 / 5

Workflow Clarity

A numbered 10-step Workflow and a 5-step 'Guiding a review' flow provide clear sequencing, with explicit validation ('comment apply validates the full batch before mutating', 'review --json' before '--include-patch') and an error-recovery feedback loop in the Common errors section.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections (Inspect, Navigate, Reload, Comments, Attention marks) with no nested references and no bundle files; a single self-contained CLI reference is appropriate, though the detailed command reference and STML section could optionally live in separate files.

4 / 5

Total

18

/

20

Passed

Description

92%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, third-person description that concretely enumerates the skill's actions and pairs them with an explicit 'Use when' trigger clause. The only minor gap is trigger-term coverage relying heavily on the Hunk brand rather than broader synonyms.

Suggestions

Add broader natural synonyms to the trigger clause (e.g., 'code review', 'walk through a diff', 'review a changeset') so users who don't name Hunk explicitly still surface this skill.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'Inspects review focus, navigates files, hunks, and exact lines, reloads session contents, adds inline review comments, and paints attention marks on character ranges' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what ('Interacts with live Hunk diff review sessions via CLI...') and when ('Use when the user has a Hunk session running or wants to review diffs interactively') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('Hunk session running', 'review diffs interactively', 'diff review sessions'), but coverage leans on the Hunk brand name and misses common synonyms like 'code review' or 'walk me through a diff'.

4 / 5

Distinctiveness Conflict Risk

The Hunk diff-review niche has distinct triggers tied to a specific running tool, so it is clearly distinguishable from other skills with minimal conflict risk.

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
modem-dev/hunk
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.