CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

differential-review

Security-focused code review for PRs, commits, and diffs.

Quality

69%

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

Quality

Content

63%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 well-structured with genuinely actionable triage tables, a clear phase workflow, and a validation checklist, but it is held back by substantial cross-section repetition and by referencing four supporting files that are absent from the bundle, breaking its progressive-disclosure design. Tightening the repeated directives and either shipping the referenced files or inlining their essential content would lift it significantly.

Suggestions

Ship the four referenced files (methodology.md, adversarial.md, reporting.md, patterns.md) in the bundle, or inline their essential content — currently every reference in the Decision Tree and Supporting Documentation sections is a dead end.

Consolidate the directives repeated across Core Principles, Rationalizations, Quality Checklist, and Tips (report generation, git blame, blast radius, attack scenarios) into a single authoritative section.

Add an explicit error-recovery checkpoint for incomplete coverage mid-review (e.g., 'if time-boxed, mark unanalyzed files as uncovered in the report and downgrade confidence'), and drop the generic Limitations boilerplate.

DimensionReasoningScore

Conciseness

The body avoids explaining known concepts, but key directives repeat across many sections: "always generate the report file" appears in Core Principles ("Always generate comprehensive markdown report file"), the Rationalizations table ("Always write report"), the Quality Checklist ("Report file generated"), Tips Do ("Always generate the output file"), and Tips Don't ("Output report only to chat (file required)"), and git blame / blast radius / attack-scenario guidance similarly recurs 3-4 times. This matches the mostly-efficient-but-needs-tightening anchor rather than the minor-trim level 4.

3 / 5

Actionability

Concrete, executable guidance dominates: risk-trigger tables with named criteria ("Auth, crypto, external calls, value transfer, validation removal"), size thresholds ("<20", "20-200", "200+"), a specific command (`issue-writer --input DIFFERENTIAL_REVIEW_REPORT.md --format audit-report`), red-flag patterns, and three worked examples with strategy selection. It is not level 5 because the actual mechanics of blast-radius calculation, adversarial modeling, and report structure are only delegated, not specified on the page.

4 / 5

Workflow Clarity

The multi-step process is clearly sequenced via the workflow diagram ("Pre-Analysis → Phase 0: Triage → ... → Phase 6: Report"), a decision tree for routing, and an explicit pre-delivery Quality Checklist ("Before delivering: [ ] All changed files analyzed...") serving as a validation checkpoint. It falls short of level 5 because there are no error-recovery feedback loops (e.g., what to do when coverage is incomplete mid-review) and per-phase steps are deferred to external files.

4 / 5

Progressive Disclosure

The on-paper structure is strong — a decision tree routing to four one-level-deep, clearly signaled references (methodology.md, adversarial.md, reporting.md, patterns.md) each with inline descriptions, plus a Supporting Documentation section — but none of these four files exist in the bundle (no references/, scripts/, or assets/ directories), so every disclosure path dead-ends in practice. Missing referenced files are a greater-than-minor organization gap, placing this below the level-4 anchor.

3 / 5

Total

14

/

20

Passed

Description

61%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, mostly distinct niche with natural trigger keywords, but it is incomplete: it states only the 'what' with a single action and no 'Use when...' trigger clause. Adding explicit usage triggers and one or two more concrete actions would materially improve it.

Suggestions

Add an explicit trigger clause, e.g., "Use when reviewing pull requests, commits, or diffs for security issues such as auth, crypto, or access-control changes."

Enumerate 1-2 more concrete actions to raise specificity, e.g., "...identifies vulnerabilities, rates severity, and generates an evidence-backed report."

Include common synonyms such as "pull request" (spelled out), "vulnerability", and "audit" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action with explicit targets ("Security-focused code review for PRs, commits, and diffs"), matching the anchor for domain plus 1-2 concrete actions. It does not list several specific actions (e.g., finding vulnerabilities, rating severity, generating a report), so it falls short of the level-4 anchor.

3 / 5

Completeness

It clearly answers 'what' ("Security-focused code review for PRs, commits, and diffs") but contains no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3. The 'when' is only weakly implied by the target list, which is the exact level-3 anchor; it is not level 4 because no explicit 'when' is present at all.

3 / 5

Trigger Term Quality

"code review", "security", "PRs", "commits", and "diffs" are all natural terms a user would say when needing this skill, giving good keyword coverage. A few natural terms and synonyms are missing ("pull request" spelled out, "vulnerability", "audit", "patch"), so it does not reach the comprehensive-synonym level 5.

4 / 5

Distinctiveness Conflict Risk

The "Security-focused" qualifier plus the PR/commit/diff scope carves a mostly distinct niche versus general code-review skills, with only minor overlap risk when a user's security intent is unstated. It does not reach level 5 because the absence of distinct trigger phrases leaves ambiguity against a general 'review this PR' request.

4 / 5

Total

14

/

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

BigSimmo/Communication

Path

.agents/skills/differential-review/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.