CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

antithesis-workload

Implement Antithesis workloads by turning the property catalog into SDK assertions and test commands, then refine coverage after triage.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./antithesis-workload/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, highly actionable skill body with excellent workflow sequencing — explicit gates, user-confirmation checkpoints, feedback loops via unfired assertions, and a thorough self-review checklist. The main costs are token efficiency (the inlined 28-item review checklist, duplicated version stamp, and time-sensitive version pins) and a small navigation gap: one bundle file (multi-test-directories.md) is orphaned from the Reference Files table.

Suggestions

Add a row for references/multi-test-directories.md to the Reference Files table (or reference it from the test-commands guidance) so the bundle file is discoverable.

Move the ~28-item Self-Review criteria into a reference file (e.g., references/self-review.md) and keep a short pointer plus the most critical checks inline, cutting significant tokens from every skill load.

Remove the duplicated "Skill version" line from the body (frontmatter already records it) and consider grouping the snouty 0.8.0 version requirement into a clearly-labeled prerequisites/version note so time-sensitive details don't age the whole body.

DimensionReasoningScore

Conciseness

The body is mostly operational and avoids teaching concepts Claude already knows, but it could be tightened: a ~28-item Self-Review checklist is inlined that could live in a reference file, the version stamp "2026-10-30 d5d7b3b" is duplicated from frontmatter into the body, and time-sensitive version pins ("snouty is not older than 0.8.0") appear outside any deprecation/old-patterns context. This matches anchor 3 — mostly efficient with some content that could be trimmed or moved — rather than 4, where only minor instances of over-explanation would remain.

3 / 5

Actionability

The guidance is concrete and executable for an instruction-only skill: exact paths ("antithesis/scratchbook/properties/{slug}.md", "/opt/antithesis/test/v1/{name}/"), enumerated valid command prefixes, specific commands ("snouty --version", "snouty validate on antithesis/config"), and per-step reference reads. Not anchor 5 because a few key details are delegated without inline examples (e.g., no sample SDK assertion snippet anywhere in the body), leaving minor gaps if the references are unavailable.

4 / 5

Workflow Clarity

Both workflows ("Implement next property" and "Post-triage iteration") are clearly sequenced with explicit checkpoints: hard prerequisite gates ("DO NOT PROCEED"), user confirmation before implementation, a built-in feedback loop (run a test, check which assertions fired, treat unfired reach claims as the iteration signal), a `snouty validate` step, and an extensive Self-Review checklist. This matches anchor 5 — clear sequence, explicit validation, feedback loops, and a checklist — rather than 4, where checkpoints would be incomplete.

5 / 5

Progressive Disclosure

Good structure: a Reference Files table with a "when to read" column, one-level-deep references, and workflows that name which reference to read at each step; all five referenced files exist in the bundle. Not anchor 5 because references/multi-test-directories.md exists in the bundle but is never referenced in the body or table (an undiscoverable orphan), and the long inline Self-Review checklist is content that arguably belongs in a separate reference file.

4 / 5

Total

16

/

20

Passed

Description

66%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, domain-anchored description that clearly states what the skill does, with solid natural trigger keywords for the Antithesis domain. Its main weakness is the complete absence of a "Use when..." clause or equivalent trigger guidance, which caps completeness and slightly blurs the boundary with the sibling antithesis skills. Adding an explicit trigger sentence would lift this from good to excellent.

Suggestions

Add a "Use when..." clause naming the trigger moments, e.g., "Use when the user asks to implement or expand Antithesis workload properties, write test commands or SDK assertions, or improve coverage after a triage run."

Include a couple of natural trigger synonyms users might say, such as "write assertions", "add test commands", or "expand the workload", to broaden trigger matching.

Sharpen the distinction from sibling skills, e.g., "Use antithesis-triage to review runs and return here to act on findings" — making the handoff boundary explicit in the description.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "turning the property catalog into SDK assertions and test commands", "refine coverage after triage" — anchored in a named domain. It falls short of anchor 5 because the leading phrase "Implement Antithesis workloads" is a generic umbrella and the action list is not comprehensive of the skill's scope (scoping, detection, and recommendation work described in the body).

4 / 5

Completeness

The "what" is clear (map property catalog to assertions and test commands, then refine coverage post-triage), but there is no "Use when..." clause or equivalent explicit trigger guidance — nothing tells the user or Claude when to invoke this skill versus its siblings. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3; it is not a 2 because the "what" is specific rather than vague.

3 / 5

Trigger Term Quality

Good natural keyword coverage for the domain: "workloads", "property catalog", "SDK assertions", "test commands", "triage", "coverage" — phrases a user in this domain would plausibly say. Not anchor 5 because synonyms and variations are missing (e.g., "test templates", "properties", "fault injection", "run results"), so a few natural trigger phrasings would not match.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct — workload implementation with concrete artifacts (assertions, test commands) — and unlikely to trigger unrelated skills. It stays at 4 rather than 5 because "refine coverage after triage" overlaps with the closely related antithesis-triage skill's territory, and without a 'when' clause the boundary between this and sibling antithesis skills relies on inference.

4 / 5

Total

15

/

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