antithesis-workload

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

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./antithesis-workload/SKILL.md

Quality

Content

85%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-organized, actionable skill body with clear workflows, validation feedback loops, and proper progressive disclosure via a reference table. Only minor conciseness trims and a few actionability gaps keep it from perfect.

Dimension	Reasoning	Score
Conciseness	Dense, operational prose that mostly assumes Claude's competence; a few sections (provenance display rationale, short-hash explanation) could be trimmed, so just below the leanest anchor.	4 / 5
Actionability	Provides concrete paths, enumerated command prefixes, specific file references, and a validation command; minor gaps keep it just below fully copy-paste-ready given it is instruction-oriented.	4 / 5
Workflow Clarity	Two clearly sequenced numbered workflows with explicit validation checkpoints and a feedback loop (unfired reach claims driving iteration) plus a thorough self-review checklist.	5 / 5
Progressive Disclosure	Well-structured overview with a reference table mapping each file to 'When to read', one-level-deep references, and all referenced files confirmed present.	5 / 5
	Total	18 / 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, domain-distinct description with concrete actions, but it omits an explicit 'Use when...' trigger clause, which caps completeness. Adding trigger guidance would raise the score.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke this skill (e.g., when the user asks to implement or expand Antithesis workloads/properties).

Include a couple of natural user phrasings or synonyms in the description to improve trigger-term coverage.

Consider listing one or two more concrete actions to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions ('turning the property catalog into SDK assertions and test commands', 'refine coverage after triage'); falls just short of a fully comprehensive action list, so between anchors 3 and 5.	4 / 5
Completeness	Clearly states what the skill does but lacks any explicit 'Use when...' trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural domain terms a user would say ('Antithesis workloads', 'property catalog', 'SDK assertions', 'test commands', 'triage') with good coverage, though a few natural synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Antithesis workloads) with domain-specific triggers, making conflict with unrelated skills minimal.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: antithesishq/antithesis-skills
Path: antithesis-workload/SKILL.md
Commit: 6a6b566

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.