CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-delta

Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/review-delta/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 content is a tight, highly actionable workflow with concrete tool calls and exact arguments, well-organized into Steps and Report sections. Its only gap is the absence of an explicit error-recovery feedback loop, which keeps workflow clarity at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is lean and efficient: every line is an actionable tool call or report field, with no padding or explanation of concepts Claude already knows, matching the lean-and-efficient anchor.

5 / 5

Actionability

Steps are fully executable with concrete tool names and exact arguments (e.g. detect_changes_tool(detail_level="minimal"), query_graph_tool(pattern="tests_for", target="<function>")), copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

A clear 5-step sequence with a conditional checkpoint in step 1 (status: not_ready -> build_or_update_graph_tool and continue), but there is no explicit validate->fix->retry feedback loop for cases where a tool call fails or returns unexpected results.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, organized into clear ## Steps and ## Report sections; per the simple-skill exception this warrants a 5 with just well-organized sections.

5 / 5

Total

19

/

20

Passed

Description

53%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 is concise and names a clear, distinct capability, but it lacks an explicit 'Use when...' trigger clause and only offers a couple of concrete actions, leaving the 'when to use' question implied rather than stated.

Suggestions

Add an explicit 'Use when ...' clause naming natural trigger phrases (e.g. 'Use when reviewing only recent changes, a git diff, or what changed since the last commit').

List one or two more concrete actions to lift specificity from a couple of actions toward comprehensive coverage.

Include common synonyms users actually say ('diff', 'what changed') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (delta review) and a couple concrete actions ('impact analysis', 'automatic blast-radius detection') but the coverage is not comprehensive, matching the 1-2 concrete actions anchor rather than the multi-action anchor at 5.

3 / 5

Completeness

It clearly answers 'what' (review only changes since last commit with blast-radius detection) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Has relevant natural phrases like 'review changes since last commit' and 'delta review', but misses common synonyms and variations a user might say (e.g. 'diff', 'what changed', 'recently changed'), fitting the some-keywords-but-missing-variations anchor.

3 / 5

Distinctiveness Conflict Risk

The delta/blast-radius framing carves a fairly distinct niche from a general review skill, with only minor overlap risk against closely related review skills; not a 5 because 'review changes' could still collide with a generic review skill's triggers.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

tirth8205/code-review-graph

Path

skills/review-delta/SKILL.md

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.