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

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 dense, highly actionable skill body: executable CLI examples, attack-to-tooling mapping, a decision-rule tooling chooser, and three sequenced workflows with real validation gates. Only minor conciseness loss from re-explaining well-known chaos principles.

DimensionReasoningScore

Conciseness

Mostly lean, skill-specific content (CLI tables, decision rules, workflows), but the re-stated '4 Principles of Chaos Engineering (Netflix, 2016)' section and the motivational opener mildly over-explain concepts Claude already knows.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with complete flags for all three tools, plus a tooling chooser with concrete decision rules — e.g. 'python scripts/experiment_designer.py --target ... --attack latency --magnitude "+200ms" --abort-if ...'.

5 / 5

Workflow Clarity

Three clearly sequenced workflows; Workflow 1 has explicit validation checkpoints ("confirm GREEN before proceeding", "confirm abort criteria are concrete") and an abort feedback loop ("If abort criteria are hit, abort immediately"), satisfying the destructive-operation bar.

5 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references — 'See references/attack_taxonomy.md for full detail', 'See references/tooling_landscape.md for trade-offs' — and a References section; all referenced files (4 references, 3 scripts, 2 templates) verified to exist.

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.

An exemplary description: concrete capabilities, an explicit 'Use when' clause, a rich set of natural trigger terms and tool names, and clear distinctiveness. It fully satisfies every dimension without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "Ships experiment designer, blast-radius calculator, and postmortem generator (all stdlib Python), 4 references ... and a /chaos-experiment slash command" — with comprehensive, non-generic coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both: what ("Ships experiment designer, blast-radius calculator, and postmortem generator ... 4 references ... slash command ... Composes with feature-flags-architect and kubernetes-operator") and when ("Use when planning, running, or learning from chaos engineering experiments" + enumerated triggers).

5 / 5

Trigger Term Quality

Comprehensive coverage of natural trigger terms including synonyms and product names — "chaos experiment", "fault injection", "gameday", "resilience test", "blast radius", "steady state", "abort criteria", plus Chaos Toolkit/Mesh/Litmus/Gremlin/AWS FIS.

5 / 5

Distinctiveness Conflict Risk

Clear niche (chaos engineering) with distinct triggers and named tooling; composition with two other skills is framed as integration, not capability overlap, so conflict risk is minimal.

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.