CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

antithesis-launch

Launch an Antithesis run with snouty by discovering the harness layout, building the right Docker Compose config, running `snouty validate`, bailing on validation failure, and then submitting `snouty launch` with sane metadata. Use when the user wants to send, submit, or launch an Antithesis run. This skill takes duration in minutes as input.

Quality

95%

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

88%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 content is a strong operational skill: fully executable commands with all launch flags, an explicitly ordered workflow with validation gates and stop conditions, ambiguity-handling rules, and a self-review checklist. Its only weaknesses are mild redundancy of the validation rule across four sections, time-sensitive version info outside a deprecated section, and slightly long inline Discovery heuristics that keep it from the top conciseness/progressive-disclosure marks.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no concept explanations, just tool-specific knowledge — but the validate-before-launch rule is repeated across Goal, Execution, Output, and Self-Review ('if validation fails, stop and report the error', 'Do not run `snouty launch` unless...'), and time-sensitive version info ('older than 0.8.0', '2026-10-30 d5d7b3b') is not placed in an old-patterns/deprecated section. This fits 'efficient; minor instances that could be trimmed' rather than the lean anchor 5.

4 / 5

Actionability

The sh block is copy-paste ready with every flag set explicitly (--launcher, --config, --duration, --source, --test-name, --description), and guidance includes concrete commands and env vars for real edge cases: 'SNOUTY_CONTAINER_ENGINE=docker', "podman compose version must print Docker Compose version", and named launcher defaults (basic_test, basic_k8s_test). This matches 'fully executable; copy-paste ready commands covering common cases'.

5 / 5

Workflow Clarity

'Launch an Antithesis run in this order only' gives an explicit sequence with hard validation gates at each step, error handling ('If validation fails, stop immediately and show the failing command plus the key error'), ambiguity resolution ('ask the user instead of guessing', 'stop and ask the user for it'), and a Self-Review checklist. This matches the anchor-5 pattern of explicit validation steps plus checklists; stopping on failure is the correct recovery behavior for a submission-type operation.

5 / 5

Progressive Disclosure

Sections are well-organized (Prerequisites, Goal, Required Input, Discovery, Run Arguments, Execution, Output, Self-Review) and everything is appropriately placed inline with no content that clearly belongs in a separate file. However, at ~82 lines it exceeds the under-50-line simple-skill exception, and the Discovery heuristics section is the kind of peripheral detail that could live in a reference file, so it sits at 'good structure; minor organization gaps' rather than 5.

4 / 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.

This is an exemplary description: it states the complete workflow in third person with concrete tool-specific actions, gives an explicit 'Use when' trigger clause with natural synonyms, and occupies a distinct niche with no realistic conflict risk. It closely matches the good_overall_examples pattern in both structure and quality.

DimensionReasoningScore

Specificity

Lists five concrete, named actions — 'discovering the harness layout', 'building the right Docker Compose config', 'running `snouty validate`', 'bailing on validation failure', and 'submitting `snouty launch` with sane metadata' — which comprehensively covers the skill's workflow. Only 'sane metadata' is slightly vague, but the anchor-4 'minor gaps' level is for descriptions with fewer or less specific actions than this.

5 / 5

Completeness

Both 'what' (the full discover → build → validate → launch workflow) and 'when' ('Use when the user wants to send, submit, or launch an Antithesis run') are explicitly stated with concrete trigger phrases. It also adds input requirements ('This skill takes duration in minutes as input'), going beyond the clear-and-explicit anchor.

5 / 5

Trigger Term Quality

'Use when the user wants to send, submit, or launch an Antithesis run' covers three natural verb synonyms users would say, plus the domain keywords 'Antithesis' and 'snouty'. File extensions don't apply to this domain, and no natural phrasing is missing, so it fits the comprehensive-coverage anchor rather than the 'a few natural terms missing' level.

5 / 5

Distinctiveness Conflict Risk

The description is anchored to a clear niche — Antithesis runs via the snouty tool — with triggers ('send, submit, or launch an Antithesis run') that no other plausible skill would match. It has minimal conflict risk, fitting the 'clear niche with distinct triggers' anchor.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

antithesishq/antithesis-skills

Path

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