CtrlK
BlogDocsLog inGet started
Tessl Logo

differential-review

Performs security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports. Automatically detects and prevents security regressions.

59

Quality

68%

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 ./plugins/differential-review/skills/differential-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%Weight 40%Scale 1-3

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

The body is well-organized, concise, and presents a clear phased workflow with checkpoints, but its progressive disclosure is undermined by four referenced markdown files that do not exist in the bundle, and actionable depth for the review steps themselves is largely deferred to those missing references.

Suggestions

Create the referenced bundle files (methodology.md, adversarial.md, reporting.md, patterns.md) or remove the links so navigation resolves.

Add a few concrete, executable examples or commands for the core review steps rather than only describing them.

Verify each in-body reference points to a real file in references/ or the skill directory.

DimensionReasoningScore

Conciseness

The body is lean: tables, a decision tree, and short lists carry the content with no padded explanation of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Guidance is concrete in places (size thresholds, risk triggers, delegation targets) but lacks executable commands or copy-paste-ready examples for the actual review steps, which are described rather than scripted.

2 / 3

Workflow Clarity

A clear phased sequence is laid out (Pre-Analysis through Phase 6) with explicit checkpoints, a quality checklist, and a 'Red Flags / Stop and Investigate' feedback loop for risky patterns.

3 / 3

Progressive Disclosure

The body references methodology.md, adversarial.md, reporting.md, and patterns.md, but none of these bundle files exist in the skill directory, so the referenced detail is unresolvable and navigation is broken.

1 / 3

Total

9

/

12

Passed

Description

67%Weight 40%Scale 1-3

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 specific and clearly occupies a distinct security-focused differential-review niche, but lacks an explicit 'Use when...' trigger clause and common user phrasings, which caps completeness and trigger term quality.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when reviewing PRs, commits, or diffs for security regressions.'

Include common user-facing phrasings like 'review my PR', 'check this diff', or 'security review' alongside the technical terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports') covering several distinct capabilities.

3 / 3

Completeness

It clearly answers 'what does this do' but has no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

Relevant terms (PRs, commits, diffs, security regressions) are present but it lacks common user-facing phrasings like 'review my PR' or 'check this diff for security issues'.

2 / 3

Distinctiveness Conflict Risk

The security-focused differential-review niche with specific triggers (PRs/commits/diffs, security regressions) is clearly distinct from general code-review skills.

3 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 missing

Warning

Total

15

/

16

Passed

Repository
trailofbits/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.