MCPInstall

antithesis-setup-k8s

by antithesishq OfficialDevOps & Cloud

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.

Installs
300
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/antithesishq/antithesis-skills --skill antithesis-setup-k8s
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads antithesis-setup-k8s automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Antithesis K8s Setup

Skill version: 2026-10-21 4f8d80b

Purpose and Goal

Scaffold the antithesis/ harness needed to bring the system up in Antithesis in a mostly idle, ready state.

Success means:

  • The deployment definition exists in antithesis/config/manifests/ and references the required SUT images. This is a collection of raw Kubernetes manifests (no helm, no kustomize)
  • antithesis/config/manifests/ is a minimized setup of the k8s-based SUT that is required for the Antithesis run
  • snouty validate on antithesis/config/ succeeds
  • The harness is ready for the antithesis-workload skill to add or iterate on test templates, assertions, and workload code
  • If the user asks to submit or launch a run, use the antithesis-launch skill — do not run snouty launch directly

Prerequisites

  • The user must have a collection of Kubernetes artifacts. This can be a helm chart, kustomize templates, or Kubernetes manifests.

    • If the user has a helm chart, they must provide a values file that can be templated into the helm chart. This can be in the form of a standard values.yaml, an ArgoCD Application with a values field, or a FluxCD HelmRelease with a values field.
    • If the user has a collection of helm charts, determine what subset (ideally a single one or a couple to make one standalone application) of helm charts will be the system under test in Antithesis. You may have to ask the user which one they want. Do not infer what the single target SUT is.

  • The user must have already pushed up images to the antithesis registry or is using public images. The images that should be pushed up are all the images that are required to run the templatized helm chart. There are instructions for this in references/manifests.md

  • DO NOT PROCEED if snouty is not installed. See https://raw.githubusercontent.com/antithesishq/snouty/refs/heads/main/README.md for installation options.

  • DO NOT PROCEED if snouty is older than 0.8.0. Use snouty --version to find the version. Use snouty update to update.

  • This skill runs kubectl, kind, k3s, kapp to touch an active Kubernetes cluster to validate that the manifests are able to come up in a Kubernetes environment. Ask the user before running any of these commands. The skill should only touch Kubernetes resources that it has created and should clean up all resources it creates before exiting.

  • This skill may have to run helm or kustomize commands to template out manifests.

Documentation Grounding

Use the antithesis-documentation skill to access these pages. Prefer snouty docs.

  • Kubernetes setup guide: https://antithesis.com/docs/getting_started/setup_guide/setup_k8s.md
  • Kubernetes best practices: https://antithesis.com/docs/best_practices/k8s_best_practices.md
  • Handling external dependencies: https://antithesis.com/docs/reference/dependencies.md
  • Fault injection: https://antithesis.com/docs/product/fault_injection.md

Workflow

This skill is broken out into multiple steps, each in a different reference file. Read and implement each reference file listed below one at a time to fully set up a project. After implementing each step, check whether what you learned invalidates any decisions from earlier steps - if it does, return to that step and redo it before proceeding. The horizontal-classification and vertical-classifications require a working file that will be applied to the manifests during the apply-findings stage. Keep these findings in case analysis is required of what changed when using the setup in Antithesis.

At the beginning of running the skill, ask the user if they would like to start from scratch or continue from a past iteration.

Pipeline (run in order, but reopen an earlier pass when a later one contradicts it)

  • references/directory-init.md: initialize the antithesis/ directory. This will contain a collection of Kubernetes manifests that will run in Antithesis
  • references/manifests.md: constructs antithesis/config/manifests/ as a collection of raw kubernetes manifests generated from the customers Kubernetes templates
  • references/horizontal-classification.md: attempts to figure out which parts of the system are necessary to test
  • references/vertical-classification.md: drops certain manifests that do not enhance the Antithesis Kubernetes experience
  • references/apply-findings.md: applies the findings from the classification steps to the manifests to simplify the setup
  • references/validate-snouty.md: runs snouty validate on the manifests and performs a static analysis
  • references/validate-local.md: deploys the Kubernetes manifests to a local k3s cluster to ensure SUT is functional
  • references/submit.md: test locally and submit the first run

These stages of the pipeline are NOT one-way gates. If any parts reveal a classification decision earlier was wrong, go back and re-run the affected earlier pass and update working.md.

Additionally, the validate-local.md step may be skipped by the user. If the user skips a step, make sure to record that the step is skipped and continue with the skill. Do not exit early and say that the task is complete until all parts have been completed.

Reference catalogs (from the steps above)

  • references/landmines.md: identifies classes of manifests that are detrimental to the Antithesis Kubernetes experience
  • references/operator-recipes.md: recipes for expanding operator managed custom resources into primitives - used during vertical-classification.

Reference

SUT System under test.

snouty validate Use this command to quickly validate changes to the Antithesis scaffolding. See snouty validate --help for details.

working file Live, growing artifact across passes (antithesis/scratchbook/k8s-minimization/working.md)

landmine A platform-layer construct that is commonly minimized away, with a known recipe (Istio, cert-manager, external-secrets, etc.)

FAQ

What does the antithesis-setup-k8s skill do?

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.

How do I install antithesis-setup-k8s?

Run npx skills add https://github.com/antithesishq/antithesis-skills --skill antithesis-setup-k8s in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/antithesis-setup-k8s/ (personal) or .claude/skills/antithesis-setup-k8s/ (project).

Which AI agents can use antithesis-setup-k8s?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is antithesis-setup-k8s safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains antithesis-setup-k8s?

It is published by antithesishq in antithesishq/antithesis-skills, and it is an official skill from the maker of the technology it covers. It has 300 recorded installs.

More from antithesishq/antithesis-skills

View all →

antithesis-research

antithesishq/antithesis-skills

Analyze a codebase to figure out how it should be tested with Antithesis: map the system, identify failure-prone areas and testable properties, and produce the research artifacts needed for workload and environment planning.

OfficialProductivity & Automation630 installs

antithesis-documentation

antithesishq/antithesis-skills

Use Antithesis documentation efficiently for product, workflow, and integration questions. Prefer the snouty docs CLI when available, and otherwise request markdown versions of documentation pages directly.

OfficialDocs & Writing601 installs

antithesis-triage

antithesishq/antithesis-skills

Triage Antithesis test reports to understand what happened in a run: look up runs, check status, investigate failed properties (assertions), view metadata, download logs, search events across all timelines, inspect findings, and examine environmental details. Load after a run completes or when investigating a failure.

OfficialTesting & QA599 installs

antithesis-workload

antithesishq/antithesis-skills

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

OfficialTesting & QA589 installs

antithesis-setup

antithesishq/antithesis-skills

Scaffold the Antithesis harness with docker-compose: initialize the working directory, write Dockerfiles and docker-compose.yaml with build directives, and prepare to submit your first Antithesis test run. If the desired setup is Kubernetes, defer to the antithesis-setup-k8s skill.

OfficialDevOps & Cloud574 installs

antithesis-debug

antithesishq/antithesis-skills

Run a bash script inside an Antithesis run at a chosen moment with snouty runs exec, from the terminal and without a browser. Use it for scripted forensics on a run: process and container inspection, on-disk evidence, gdb attach, and general debugging. Covers command usage, the live-session requirement, common workflows and errors, and how virtual time and perturbation limit what a debugger can see.

OfficialCode Quality & Workflow567 installs

Popular devops & cloud skills

View category →

microsoft-foundry

microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure

OfficialDevOps & Cloud579.1K installs

azure-diagnostics

microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.

OfficialDevOps & Cloud569.8K installs

azure-prepare

microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

OfficialDevOps & Cloud569K installs

azure-ai

microsoft/azure-skills

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.

OfficialDevOps & Cloud568.8K installs

azure-deploy

microsoft/azure-skills

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.

OfficialDevOps & Cloud568.6K installs

azure-validate

microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.

OfficialDevOps & Cloud568K installs