CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/chaos-mesh

Configures Chaos Mesh for Kubernetes-native chaos engineering - picks fault types (PodChaos, NetworkChaos, StressChaos, IOChaos, TimeChaos, DNSChaos, KernelChaos, HTTPChaos), targets via label selectors, controls blast radius via namespace whitelists + selector filters, schedules via CronJobs, observes via dashboard. Distinct from Litmus by architecture (Chaos Mesh has its own dashboard + workflow orchestration; Litmus uses ChaosCenter UI). Use when the target system runs on Kubernetes and fault experiments should be declared as CRDs in the cluster alongside the workloads they target.

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

82%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 dense, actionable runbook with copy-paste YAML/commands and a sensible nine-step sequence plus anti-patterns and limitations. Conciseness is slightly diluted by repeated homepage quote blocks, and the verdict step lacks an explicit failed-hypothesis feedback loop.

Suggestions

Trim or consolidate the repeated 'Per [chaos-mesh-home][cm]' quote blocks into a single attribution to reduce padding that Claude does not need.

Add an explicit feedback loop after Step 7: e.g. 'If the steady-state hypothesis is violated, scale blast radius down (mode: one / fixed-percent: 25), re-apply, and re-verify before widening scope.'

Consider moving the full fault-type CRD table or the Workflow template into a reference file so the SKILL.md overview stays lean, lifting progressive disclosure toward a 5.

DimensionReasoningScore

Conciseness

Mostly efficient with tight tables and lean code blocks, but the repeated 'Per [chaos-mesh-home][cm]' marketing quote blocks (Overview, Step 2, Step 5, Step 8) add tokens that Claude does not need and could be trimmed.

4 / 5

Actionability

Fully executable throughout — install/Helm commands, complete NetworkChaos/PodChaos/Workflow/PhysicalMachineChaos YAML, port-forward, kubectl apply/get/describe, and a CI integration snippet are all copy-paste ready.

5 / 5

Workflow Clarity

A clear numbered sequence (Steps 1–9) with a Step 7 'Run + verdict' checkpoint that watches state and verifies the steady-state hypothesis; the cap at 3 is avoided because validation is present, but there is no explicit validate→fix→retry feedback loop when the verdict fails.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections (Overview, When to use, Steps, Anti-patterns, Limitations, References) with one-level external links and no nested references; at ~250 lines it is longer than the simple-skill case, so it stops just short of a 5.

4 / 5

Total

17

/

20

Passed

Description

92%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, third-person description that pairs a comprehensive list of concrete capabilities with an explicit Kubernetes/CRD trigger clause and a distinctiveness statement against Litmus. The only gap is a few natural synonyms (fault/resilience testing) that would round out trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'picks fault types (PodChaos, NetworkChaos, ...)', 'targets via label selectors', 'controls blast radius via namespace whitelists', 'schedules via CronJobs', 'observes via dashboard' — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both what (configures fault types, targeting, blast radius, scheduling, observation) and when via the concrete 'Use when the target system runs on Kubernetes and fault experiments should be declared as CRDs' trigger clause.

5 / 5

Trigger Term Quality

Good keyword coverage with natural terms users say ('Chaos Mesh', 'Kubernetes', 'chaos engineering', 'CRDs'), but misses common synonyms a user might voice such as 'fault injection' or 'resilience testing'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Chaos Mesh on Kubernetes) and even states 'Distinct from Litmus by architecture', making overlap with sibling chaos skills minimal.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents