CtrlK
BlogDocsLog inGet started
Tessl Logo

adversarial-reviewer

Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart. Do not use for ordinary review, style feedback, or general improvement suggestions.

75

Quality

93%

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

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 tight, well-structured adversarial-review skill that is token-efficient and clearly sequenced. The only meaningful gap is the absence of a worked finding example, which keeps actionability and workflow_clarity just below the top anchor.

Suggestions

Add one short worked finding (title, file:line, failing scenario, impact, fix direction) to model the exact output format and lift actionability to the top anchor.

Include an explicit feedback loop in the Hunt section (e.g., 'reproduce -> confirm -> re-check related paths') to strengthen workflow_clarity for ambiguous cases.

DimensionReasoningScore

Conciseness

The body is lean (~50 lines), assumes Claude's competence, and avoids explaining concepts Claude already knows; every section delivers actionable directives with no padding, matching the lean-and-efficient anchor.

5 / 5

Actionability

Concrete guidance via a findings standard (five required elements), a four-level severity rubric, and specific check categories, but lacks a worked example of an actual finding — a minor gap keeping it below the fully-copy-paste-ready anchor at 5.

4 / 5

Workflow Clarity

Clear sequence (establish boundary, hunt for failures, findings standard, report) with numbered steps and a checklist-like findings standard; the read-only nature means no destructive validation cap applies, but there is no explicit feedback loop, so it sits at 4 rather than 5.

4 / 5

Progressive Disclosure

A single under-50-line file with no need for external references and well-organized section headers; per the simple-skills note this qualifies for the top anchor on structure alone.

5 / 5

Total

18

/

20

Passed

Description

100%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 description that concretely states what it does, gives natural user-facing trigger phrases, and explicitly distinguishes itself from ordinary review via negative triggers. All four dimensions land at the top anchor.

DimensionReasoningScore

Specificity

Names the domain (code-change review) and lists multiple concrete defect categories ('concrete correctness defects, unsafe assumptions, and failure modes'), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

Explicitly answers both what ('Stress-test a code change...') and when ('Use when the user explicitly asks for an adversarial review...') with concrete trigger phrases, plus a do-not-use boundary.

5 / 5

Trigger Term Quality

Includes several natural phrases a user would actually say ('adversarial review', 'deep bug hunt', 'tear a change apart') with synonyms, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Explicit negative triggers ('Do not use for ordinary review, style feedback, or general improvement suggestions') carve a clear niche with minimal conflict risk against ordinary review skills.

5 / 5

Total

20

/

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
emdash-cms/emdash
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.