CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

antithesis-setup-k8s

Scaffold the Antithesis harness for customers running Kubernetes: Convert helm charts, kustomize templates, or raw Kubernetes manifests into a minimized set of manifests for Antithesis. Verify the Kubernetes manifests are in the correct shape with snouty validate and a local cluster deploy. Hands it off to antithesis-launch if the user wants to submit a run. At the end, the user is ready to run antithesis-workload to build tests. If the desired setup is docker-compose, defer to the antithesis-setup skill.

Quality

85%

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

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-orchestrated skill body: lean prerequisites with executable checks, a clearly sequenced pipeline with genuine feedback loops and validation stages, and disciplined delegation to one-level-deep reference files. The only real defects are a dangling reference to a missing live-runs.md file and small amounts of duplicated metadata and convoluted prose.

Suggestions

Fix the broken reference in references/submit.md: it points to references/live-runs.md, which does not exist in the bundle — either add the file or point to the antithesis-triage skill's own materials.

Remove the duplicated 'Skill version: 2026-10-30 d5d7b3b' line from the body (it duplicates frontmatter metadata) and tighten the multi-clause workflow preamble paragraph into 2-3 short sentences.

Inline the one-line helm/kustomize templating commands users will need most often (e.g., 'helm template ... -f values.yaml' / 'kustomize build ...') so the first execution step does not require opening a reference file.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence — it never explains what Kubernetes, helm, or kustomize are, and each reference file gets a one-line role description rather than inlined detail. It sits at level 4 rather than 5 due to minor padding: the 'Skill version: 2026-10-30 d5d7b3b' line duplicates frontmatter metadata, and the workflow preamble paragraph ('The horizontal-classification and vertical-classifications require a working file...') is convoluted and could be tightened.

4 / 5

Actionability

Concrete, executable guidance is present: exact commands ('snouty --version', 'snouty update', 'snouty validate'), exact paths ('antithesis/config/manifests/', 'antithesis/scratchbook/k8s-minimization/working.md'), version thresholds, and doc URLs, with detailed per-step execution delegated to real reference files. It is not a 5 because the body itself contains no complete copy-paste command sequences — those live in the references — leaving minor gaps such as the exact helm/kustomize templating commands.

4 / 5

Workflow Clarity

The pipeline lists eight stages in explicit order with per-stage file pointers, includes a built-in feedback loop ('If any parts reveal a classification decision earlier was wrong, go back and re-run the affected earlier pass'), and has dedicated validation checkpoints (validate-snouty static analysis, validate-local cluster deploy) plus skip handling and cleanup/permission rules for cluster-touching commands. This matches the level-5 anchor: clear sequence, explicit validation, and error-recovery loops.

5 / 5

Progressive Disclosure

The SKILL.md is a clean overview with all ten reference files listed, one level deep, each with a one-line description, and a short glossary — close to the level-5 anchor. Scoring against the actual bundle per the guidelines reveals one defect: submit.md references 'references/live-runs.md', which does not exist in the bundle, a dangling navigation path that keeps this at level 4 ('minor organization gaps').

4 / 5

Total

17

/

20

Passed

Description

83%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 strong, specific, third-person description that covers the full workflow (convert, minimize, validate, hand off) and clearly boundaries itself against sibling Antithesis skills. Its main gap is trigger phrasing: the 'when' is expressed as an audience clause rather than an explicit 'Use when...' with natural synonyms like 'k8s'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Convert helm charts, kustomize templates, or raw Kubernetes manifests into a minimized set of manifests', 'Verify... with snouty validate and a local cluster deploy', 'Hands it off to antithesis-launch' — covering the workflow end to end. It uses third person throughout and matches the comprehensive-coverage anchor; the level-4 anchor ('several specific actions; minor gaps') is exceeded because both conversion and verification methods are named for every input variant.

5 / 5

Completeness

The 'what' is explicit (scaffold, convert, verify, hand off) and a 'when' is present ('for customers running Kubernetes', plus the docker-compose deferral boundary), so both boxes are checked per the level-4 anchor. It is not a 5 because the trigger guidance is audience phrasing rather than an explicit 'Use when...' clause with concrete trigger phrases, and it is not a 3 because the when is explicitly stated, not merely implied.

4 / 5

Trigger Term Quality

Good keyword coverage: 'Kubernetes', 'helm charts', 'kustomize', 'manifests', 'Antithesis', and 'docker-compose' for the contrast case — a user would naturally say most of these. It falls short of the level-5 anchor because common synonyms like 'k8s' and 'HelmRelease'/'values file' phrasings are absent, but it clearly exceeds level 3's 'missing common variations' since all three input formats are named.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche ('the Antithesis harness for customers running Kubernetes') and actively disambiguates against the closest siblings — 'If the desired setup is docker-compose, defer to the antithesis-setup skill' and the explicit handoff to antithesis-launch/antithesis-workload. This matches the level-5 anchor of distinct triggers with minimal conflict risk.

5 / 5

Total

18

/

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