CtrlK
BlogDocsLog inGet started
Tessl Logo

chaos-engineering

Use when planning, running, or learning from chaos engineering experiments. Triggers on "chaos experiment", "fault injection", "gameday", "resilience test", "blast radius", "steady state", "abort criteria", "Chaos Toolkit", "Chaos Mesh", "Litmus", "Gremlin", "AWS FIS", or any deliberate failure-injection question. Ships experiment designer, blast-radius calculator, and postmortem generator (all stdlib Python), 4 references on chaos principles + experiment design + attack taxonomy + tooling landscape, and a /chaos-experiment slash command. Composes with feature-flags-architect (kill switches as abort triggers) and kubernetes-operator (common chaos targets).

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

The canonical home for this skill is chaos-engineering in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

92%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-structured, highly actionable skill body with executable commands, validated workflows, and clean progressive disclosure to verified reference files. The only weakness is mild over-explanation of concepts Claude already knows.

Suggestions

Trim the '4 Principles of Chaos Engineering' section to the skill's own fifth principle (abort criteria) and link the rest to references/chaos_principles.md instead of re-explaining well-known material.

Cut the motivating intro paragraph ('Most chaos engineering attempts skip steady-state measurement...') and lead directly with 'When to use'.

Move the fuller attack-type and tooling detail into the existing references, keeping only the decision-rule summaries inline to reduce duplication.

DimensionReasoningScore

Conciseness

Mostly efficient with tables and tight bullets, but re-explains the well-known '4 Principles of Chaos Engineering (Netflix, 2016)' and opens with a motivating paragraph ('Most chaos engineering attempts skip...') that Claude does not need.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with complete flags for all three tools (e.g. 'python scripts/experiment_designer.py --target ... --abort-if ...') plus concrete decision rules in the tooling chooser.

5 / 5

Workflow Clarity

Three numbered workflows with explicit validation checkpoints — 'confirm GREEN before proceeding', 'confirm abort criteria are concrete', 'If abort criteria are hit, abort immediately' — so the destructive-operation validation cap does not apply.

5 / 5

Progressive Disclosure

Clear overview body with well-signaled one-level-deep references ('See references/attack_taxonomy.md for full detail'); all four references, three scripts, and two assets referenced are real files, and bulk detail is appropriately split out.

5 / 5

Total

19

/

20

Passed

Description

100%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, information-dense description that explicitly states capabilities, trigger terms, bundled assets, and composition boundaries. It is long but every listed item is concrete rather than padded fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'experiment designer, blast-radius calculator, and postmortem generator', '4 references', a '/chaos-experiment slash command', and composition with two named skills — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both what ('Ships experiment designer, blast-radius calculator, and postmortem generator...') and when ('Use when planning, running, or learning from chaos engineering experiments' plus an explicit 'Triggers on...' list) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and named tools: 'chaos experiment', 'fault injection', 'gameday', 'resilience test', 'blast radius', 'steady state', 'abort criteria', 'Chaos Toolkit', 'Chaos Mesh', 'Litmus', 'Gremlin', 'AWS FIS'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear chaos-engineering niche with distinct triggers and explicitly delineates boundaries via composition with 'feature-flags-architect' and 'kubernetes-operator', minimizing overlap with adjacent skills.

5 / 5

Total

20

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
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.