CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

antithesis-feature-workload

Design and build an Antithesis workload for a specific feature: analyze the feature, discover its testable properties, build a self-driving workload that runs locally and in Antithesis, and iterate until the feature's behaviors are exercised and its invariants are checked.

Quality

75%

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-feature-workload/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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, directive skill body with an excellent sequenced workflow, explicit validation feedback loops, and a self-review checklist, supported by a complete and clearly-signaled reference bundle. The main flaws are minor: a duplicated version string, a slightly redundant self-review section, one dangling reference path (references/live-runs.md), and a few high-level steps that defer all concreteness to reference files.

Suggestions

Fix the dangling reference in references/iteration.md ("references/live-runs.md" does not exist in the bundle) — point to the actual file or remove the pointer.

Drop the duplicated "Skill version: 2026-10-30 d5d7b3b" line from the body since it already lives in frontmatter metadata.

Trim the Self-Review checklist items that restate reference-file content (assertion types, value-menu guidance) by pointing to references/assertions.md and references/interesting-values.md instead of restating them.

DimensionReasoningScore

Conciseness

The body is almost entirely directive, skill-specific guidance that assumes competence — no paragraphs explaining what Antithesis or Docker Compose is. Minor trimmable instances: the version string "2026-10-30 d5d7b3b" is duplicated from the frontmatter into the body, and the long Self-Review checklist restates guidance already carried by references/assertions.md and references/interesting-values.md. Not 3 because padding is incidental, not structural; not 5 because those redundancies and the time-sensitive version/date line (penalized per guidelines) do cost tokens.

4 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: named reference files with when-to-read conditions, concrete output paths ("antithesis/feature-workloads/<feature-slug>/analysis.md"), specific assertion types ("Sometimes(true, ...) should be rewritten as Reachable(...)"), and environment-switching rules ("ANTITHESIS_OUTPUT_DIR is set"). Not 5 because some steps stay high-level ("Build docker-compose for local runs", "Run locally") without commands or minimal examples, deferring entirely to references.

4 / 5

Workflow Clarity

The main workflow is a clearly sequenced 16-step process with explicit validation checkpoints (run locally, check reach claims first), explicit feedback loops ("Reach claims not firing → adjust workload", "loop back to step 3"), conditional branches for Antithesis escalation, and a comprehensive self-review checklist — a direct match for anchor 5's "feedback loops for error recovery; checklists for complex processes".

5 / 5

Progressive Disclosure

Good structure: a reference table with a when-to-read column, all seven cited reference files present in references/, and one-level-deep cross-references between sibling reference files. Not 5 because iteration.md cites "references/live-runs.md" (line 41), which does not exist in the bundle — a dangling path that breaks navigation; the body itself is otherwise a clean overview with well-signaled references.

4 / 5

Total

17

/

20

Passed

Description

58%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 concrete, action-oriented description that clearly communicates what the skill does, weakened by the complete absence of 'when to use' trigger guidance and reliance on domain jargon over natural user phrasing. It is distinctive within the Antithesis skill family but would benefit from an explicit Use-when clause with synonyms.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to test a specific feature with Antithesis, build a feature-scoped or self-driving workload, or set up TDD-style assertions for an in-development feature."

Include natural synonyms users would actually say — "feature testing", "test a specific feature", "property-based testing", "invariant checking" — alongside the domain terms.

Briefly state the distinguishing marker versus the antithesis-workload skill (self-driving program vs. Test Composer) in the description to further reduce conflict risk.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "analyze the feature, discover its testable properties, build a self-driving workload that runs locally and in Antithesis, and iterate until the feature's behaviors are exercised and its invariants are checked" — which goes well beyond naming the domain. It stops short of anchor 5 because coverage is a single process chain with minor gaps (e.g., assertion writing, triage/verification are not mentioned as capabilities).

4 / 5

Completeness

The "what" is clear (design and build a feature-scoped Antithesis workload with analysis, property discovery, and iteration), but the "when" is entirely missing — there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the 'when' is not even weakly implied by any trigger phrasing.

3 / 5

Trigger Term Quality

Relevant domain keywords are present ("Antithesis workload", "feature", "testable properties", "invariants", "self-driving"), but there are no natural trigger phrases or synonyms a user would say (e.g., "test a specific feature", "property-based testing", "feature testing"). Not 4 because the keyword set is domain-jargon-only with no user-natural variations; not 2 because multiple relevant terms exist rather than one generic keyword.

3 / 5

Distinctiveness Conflict Risk

"Antithesis workload for a specific feature" plus "self-driving workload" carves a clear niche distinct from generic testing skills. Minor overlap risk remains with the sibling antithesis-workload skill (shared terms "workload" and "assertions"), keeping it below anchor 5; it is well above anchor 3 since the feature-scoped, self-driving framing is specific.

4 / 5

Total

14

/

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

antithesishq/antithesis-skills

Path

antithesis-feature-workload/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.