CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review

Comprehensive security and correctness audit. Use for review, deep review, thermo nuclear, or thermonuclear requests and branch or PR diff audits.

Quality

79%

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 ./packages/eve-code/extension/skills/review/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A lean, well-structured instruction-only skill: every token is actionable guidance, the workflow is ordered with evidence-based validation checkpoints, and the size and organization need no external references. The only meaningful improvement would be an example of the audit instruction given to the worker subagent.

DimensionReasoningScore

Conciseness

Every sentence is directive instruction ("Give the worker subagent a self-contained audit instruction naming the repository and target ref or worktree") with zero concept explanation and no padding — 'Lean and efficient; assumes Claude's competence; every token earns its place'.

5 / 5

Actionability

Concrete, executable directives throughout ("Cite repository evidence for every finding", "Run the independent audit before reading PR discussion", "Name the exact missing file or ref") plus a specific checks list. Minor gap: no example or template of the audit instruction to hand the worker, keeping it just below fully executable.

4 / 5

Workflow Clarity

The sequence is explicit and ordered (dispatch worker → independent audit before reading PR discussion → root agent evaluates → compare and verify afterward) with validation checkpoints ("Never present a finding with unfinished evidence", "verify each against the workspace"). Not a 5 because steps are prose-embedded rather than explicitly enumerated and there is no error-recovery loop (e.g., what to do when the worker returns weak evidence).

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, references no bundle files (and none exist in the bundle), and is well-organized into a scope statement, a 'Required checks' checklist, and reporting rules — meeting the rubric's simple-skill exception for a top score.

5 / 5

Total

18

/

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 has a clear, explicit 'Use for...' trigger clause with good natural keyword coverage including spelling variants, but the capability statement is a single generic action padded with 'Comprehensive'. Adding one or two concrete actions and more specific trigger synonyms would lift specificity and distinctiveness.

Suggestions

Replace the generic 'Comprehensive security and correctness audit' with concrete actions, e.g. 'Dispatches a worker subagent to audit changed code for bugs, security vulnerabilities, and feature-gate leaks, and verifies findings against repository evidence.'

Add natural trigger synonyms users would actually say, such as 'code review', 'security review', 'audit this diff', or 'PR review', to the 'Use for' clause.

Narrow the bare 'review' trigger (e.g. 'deep review or thermonuclear code review requests') to reduce conflict with generic review skills.

DimensionReasoningScore

Specificity

The description names the domain ("security and correctness audit") but the only action is the generic verb "audit" with the padding adjective "Comprehensive" — matching the anchor 'Names the domain but actions are minimal or generic'. It is not a 3 because no second concrete action (e.g., dispatching a worker, tracing side effects, citing evidence) is enumerated.

2 / 5

Completeness

Both parts are present: a what ("Comprehensive security and correctness audit") and an explicit 'Use for...' when-clause with concrete triggers. It falls short of the 5 anchor because the 'what' is a single abstract noun phrase rather than multiple concrete, enumerated actions.

4 / 5

Trigger Term Quality

"review, deep review, thermo nuclear, or thermonuclear requests and branch or PR diff audits" gives good natural coverage, even anticipating the 'thermo nuclear' misspelling. It is not a 5 because common phrasings users would actually say — 'code review', 'security review', 'audit' — are absent.

4 / 5

Distinctiveness Conflict Risk

Distinctive triggers like "thermonuclear" and "branch or PR diff audits" help, but the bare trigger "review" is extremely high-frequency and would overlap with generic code-review skills — 'Somewhat specific but could still overlap with similar skills'. Not a 4 because 'review' alone is a major conflict term.

3 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

vercel/eve

Path

packages/eve-code/extension/skills/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.