CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/litmus-chaos

Configures LitmusChaos for Kubernetes-native chaos engineering - installs via Helm, picks ChaosExperiments from the ChaosHub (`pod-delete`, `network-latency`, `node-cpu-hog`, etc.), authors a ChaosEngine CR scoping the experiment + steady-state probes, runs as part of the cluster, exports Prometheus metrics for the verdict. Use when the platform is Kubernetes (CNCF-hosted; cloud-native). Prefer over chaos-mesh when the team wants a ChaosCenter web UI for workflow scheduling and ChaosHub catalog browsing; use chaos-mesh for fine-grained network-fault policies via its own CRD family.

80

Quality

100%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body: lean sequenced steps with executable code, explicit verdict validation feedback loops, and clean section organization. It earns the top anchor on every content dimension.

DimensionReasoningScore

Conciseness

The body is lean and action-oriented — steps are dominated by executable helm/kubectl commands, a full ChaosEngine YAML, and compact tables; it assumes competence (no basic explanations of Kubernetes, Helm, Prometheus, or CRDs) and the brief source-attributed quotes add tool-specific context rather than concept padding.

3 / 3

Actionability

Fully executable, copy-paste-ready guidance throughout: 'helm repo add... helm install...', 'kubectl apply -f...', a complete ChaosEngine CR, jsonpath verdict extraction, and a CI yaml snippet — matching the 'fully executable code/commands' anchor.

3 / 3

Workflow Clarity

Steps 1–8 are clearly sequenced with explicit validation checkpoints — Step 5 reads the Pass/Fail verdict, and the CI block adds 'kubectl wait --for=condition=Complete' plus '[ "$VERDICT" = "Pass" ]' as a feedback loop; probe-based steady-state validation is present for the destructive chaos operations, so no workflow_clarity cap applies.

3 / 3

Progressive Disclosure

No bundle files exist, so scoring falls to organization: the skill is self-contained with well-organized sections (Overview, When to use, Steps 1–8, Anti-patterns, Limitations, References), one-level-deep external references (the litmuschaos.io link and sibling skill names), and no nested reference chains.

3 / 3

Total

12

/

12

Passed

Description

100%

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 description that names concrete actions, gives an explicit 'Use when' trigger in third person, and actively differentiates the skill from chaos-mesh. It satisfies every dimension at the top anchor without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'installs via Helm', 'picks ChaosExperiments from the ChaosHub', 'authors a ChaosEngine CR scoping the experiment + steady-state probes', 'exports Prometheus metrics for the verdict' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers what (configure LitmusChaos: install, pick experiments, author ChaosEngine, export metrics) and when ('Use when the platform is Kubernetes (CNCF-hosted; cloud-native)'), satisfying the explicit-trigger anchor; third-person voice throughout.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'Kubernetes-native chaos engineering', 'Kubernetes', 'chaos', 'Prometheus metrics', 'ChaosHub' — with good coverage of common variations; not merely technical jargon.

3 / 3

Distinctiveness Conflict Risk

Clear niche with explicit sibling differentiation — 'Prefer over chaos-mesh when the team wants a ChaosCenter web UI... use chaos-mesh for fine-grained network-fault policies via its own CRD family' — making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents