CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

antithesis-research

Analyze a codebase to figure out how it should be tested with Antithesis: map the system, identify failure-prone areas and testable properties, and produce the research artifacts needed for workload and environment planning.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./antithesis-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 well-orchestrated, highly actionable skill body with excellent workflow sequencing, validation checkpoints, and reference signaling. Its weakest points are token redundancy from repeating artifact lists across sections, a few explanations of concepts Claude already knows, and one orphaned bundle file that breaks navigation completeness.

Suggestions

Deduplicate the artifact list that currently appears in Purpose, Output, and Self-Review — state it once and have the Self-Review reference it, and trim standard definitions (safety/liveness properties) that Claude already knows.

Add 'references/scratchbook-artifacts.md' to the Reference Files table (or remove it from the bundle) so every bundle file is discoverable from SKILL.md.

Provide a concrete example search command for step 4 of the full research pass (e.g. a ready-to-run grep/ripgrep pattern for the Antithesis SDK imports and assertion macros) to move guidance from specific to copy-paste ready.

DimensionReasoningScore

Conciseness

Mostly efficient orchestration prose, but the artifact list is repeated three times (Purpose, Output, Self-Review) and the Definitions section explains standard concepts Claude already knows ('A bad thing never happens' for safety properties, 'A good thing eventually happens' for liveness). The redundancy is more than minor trimming, so it sits at anchor 3 rather than 4.

3 / 5

Actionability

Concrete, executable guidance throughout: exact artifact paths ('antithesis/scratchbook/properties/{slug}.md'), specific search terms ('assert_always!', 'assert_sometimes!', 'assert_reachable!', 'assert_unreachable!'), and named provenance fields. As an instruction-only skill the absence of code is not penalized, but no ready-to-run search commands are given and some steps defer detail to reference files, keeping it below the fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

Three clearly sequenced numbered workflows with reference reads at the right points, explicit feedback loops ('apply refinements, fill gaps, escalate biases to the user'), a conditional evaluation trigger in the expansion workflow, and a Self-Review checklist with a fresh-context reviewer — matching the anchor-5 pattern of explicit validation steps, feedback loops, and checklists for a complex process.

5 / 5

Progressive Disclosure

Good structure with a well-signaled reference table including a 'When to read' column and one-level-deep references. Two minor gaps keep it below anchor 5: 'references/scratchbook-artifacts.md' exists in the bundle but is not referenced anywhere (orphaned, undiscoverable), and the very long inline Self-Review criteria are content that could partly live in a reference file.

4 / 5

Total

16

/

20

Passed

Description

70%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, concrete description that clearly communicates a multi-step capability around a distinct named tool. Its main weakness is the absence of any explicit 'when to use this' trigger guidance, which both caps completeness and slightly weakens trigger discoverability.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to plan Antithesis testing, discover testable properties, or mentions Antithesis, fault injection, or reliability testing of a distributed system.'

Include a few natural synonym trigger terms such as 'invariants', 'assertions', 'chaos/reliability testing', and 'test properties' so users phrasing the need differently still surface the skill.

Name the key output artifacts (e.g. property catalog, deployment topology) in the description instead of the generic 'research artifacts' to sharpen specificity.

DimensionReasoningScore

Specificity

Lists several concrete actions ('map the system', 'identify failure-prone areas and testable properties', 'produce the research artifacts'), but the artifacts themselves are never named, leaving a minor gap in coverage that keeps it below the comprehensive anchor 5.

4 / 5

Completeness

The 'what' is clearly and specifically answered, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' half is concrete and multi-part, not vague.

3 / 5

Trigger Term Quality

Good keyword coverage with natural phrases users would say ('tested with Antithesis', 'codebase', 'workload', 'testable properties'), but common variations like 'fault injection', 'reliability testing', 'invariants', or 'assertions' are missing. Coverage is genuinely good rather than partial, so anchor 4 fits better than 3.

4 / 5

Distinctiveness Conflict Risk

'Antithesis' is a distinct named tool with a clear niche (property-based testing of distributed/concurrent systems); the description would not plausibly trigger for an unrelated skill, matching the clear-niche anchor 5.

5 / 5

Total

16

/

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

antithesishq/antithesis-skills

Path

antithesis-research/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.