CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

antithesis-setup

Scaffold the Antithesis harness with docker-compose: initialize the working directory, write Dockerfiles and docker-compose.yaml with build directives, and prepare to submit your first Antithesis test run. If the desired setup is Kubernetes, defer to the antithesis-setup-k8s skill.

Quality

76%

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-setup/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-structured orchestrating skill: the body stays at the decision-and-criteria level, delegates step detail to six real reference files, sequences the workflow with explicit validation and a re-check feedback loop, and closes with a thorough self-review checklist. The main costs are redundancy between the success criteria and the Self-Review list, some scripted verbosity in the prerequisites, and a dangling live-runs.md reference.

Suggestions

Deduplicate the Self-Review checklist against the "Success means" bullets (e.g. reference the criteria once and have the reviewer check that list) to reclaim a meaningful share of the body's tokens.

Fix or remove the dangling references/live-runs.md citation in references/submit-and-test.md, or add the file to the bundle.

Trim the four example provenance phrasings to one or two, and move the snouty 0.8.0 minimum-version note next to the compatibility frontmatter so version-sensitive details live in one place.

DimensionReasoningScore

Conciseness

The body is directive-driven and free of basic-concept explanations, but it could be tightened: the Self-Review checklist heavily restates the "Success means" criteria and General Guidance, the provenance section includes four example phrasings of findings, and unpinned version references ("snouty is older than 0.8.0", the dated version string) are time-sensitive content outside any 'old patterns' section. Not a 4 because the duplication and scripted blockquotes are more than minor instances of over-explanation; not a 2 because there is no padding that explains things Claude already knows.

3 / 5

Actionability

Concrete, executable guidance throughout — exact commands ("snouty validate", "snouty --version", "snouty update", "compose build"), exact paths ("antithesis/config/docker-compose.yaml", "/opt/antithesis/catalog/"), and exact config keys ("platform: linux/amd64", "init: true", "depends_on" with "condition: service_healthy", "NO_COLOR=1"). Not a 5 because a few commands are under-specified in the body (e.g. which compose CLI invocation and working directory for "compose build", "image inspect" without the full command) and the actual file contents are delegated to reference files rather than shown.

4 / 5

Workflow Clarity

The multi-step process is clearly sequenced: six reference files listed in implementation order, each with a one-line scope, plus "Read and implement each reference file listed below one at a time". Validation is explicit ("snouty validate on antithesis/config/ succeeds", "Treat local testing as required before the first submission") and there is a genuine feedback loop — "After implementing each step, check whether what you learned invalidates any decisions from earlier steps" — plus a comprehensive Self-Review checklist. Not a 4 because checkpoints, error-recovery loops, and a checklist are all present, matching the top anchor.

5 / 5

Progressive Disclosure

Scored against the actual bundle: SKILL.md is a clean overview pointing to six clearly signaled, one-line-described reference files that all exist, with assets under assets/antithesis/ — good structure overall. Not a 5 because references nest two levels deep (references/instrumentation.md → references/language/*.md) rather than one level, and submit-and-test.md cites references/live-runs.md which does not exist in the bundle; not a 3 because references are clearly signaled and no reference-worthy content is inlined.

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 specific, well-disambiguated description with concrete named deliverables and natural domain keywords. Its main weakness is the absence of explicit "when to use" trigger guidance, which both caps completeness and slightly limits trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to set up, initialize, or scaffold Antithesis testing for a project with Docker Compose."

Mention instrumentation/bootstrap-assertion preparation in the action list so the description covers the full scope of what the skill does.

Include one or two everyday synonyms (e.g. "containerize the SUT", "Antithesis onboarding") to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Concrete actions are named — "initialize the working directory", "write Dockerfiles", "docker-compose.yaml with build directives", "prepare to submit your first Antithesis test run" — which is several specific actions rather than generic language. Not a 5 because instrumentation and the bootstrap-assertion work (a substantial part of the skill body) are absent, leaving minor gaps in coverage; not a 3 because far more than 1–2 concrete actions are listed.

4 / 5

Completeness

The "what" is clear (scaffold the harness, init the directory, write Dockerfiles and compose file, prepare the first run), but there is no "Use when..." clause or equivalent explicit trigger guidance — the Kubernetes deferral sentence only says when NOT to use it, so "when" is at best weakly implied. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3; not a 4 because the "when" is absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural user phrasing is present — "Antithesis", "docker-compose", "Dockerfiles", "test run", "Kubernetes" — terms a user would plausibly say when asking for this setup. Not a 5 because synonyms and variations (e.g. "scaffolding", "containerize", "configure the harness") are not covered; not a 3 because coverage goes beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (Antithesis harness scaffolding with docker-compose) with distinct tool-specific triggers, and the explicit "If the desired setup is Kubernetes, defer to the antithesis-setup-k8s skill" clause actively disambiguates from the closest sibling skill. Not a 4 because overlap risk is minimal, not minor.

5 / 5

Total

16

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

antithesishq/antithesis-skills

Path

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