CtrlK
BlogDocsLog inGet started
Tessl Logo

chaos-engineer

Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates. Use when designing chaos experiments, implementing failure injection frameworks, or conducting game day exercises. Invoke for chaos experiments, resilience testing, blast radius control, game days, antifragile systems, fault injection, Chaos Monkey, Litmus Chaos.

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

Low

Low-risk findings worth noting

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.

The content is a well-structured, actionable overview with a clear workflow, enforced validation checkpoints, and properly split one-level-deep references. Its only weakness is mild verbosity from carrying three full worked examples rather than one primary example.

Suggestions

Consider trimming the Output Templates list, which largely restates the Core Workflow and the worked examples already shown, to reduce token cost.

The Chaos Monkey and toxiproxy examples could be shortened or moved into references/chaos-tools.md, keeping the SKILL.md body focused on the primary Litmus walkthrough.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but three full concrete examples (Litmus, toxiproxy, chaos-monkey) plus an Output Templates section add length beyond strict necessity; a couple of inline comments could be trimmed. It sits noticeably above the 'mostly efficient' anchor but not quite at the 'every token earns its place' level.

4 / 5

Actionability

Provides fully executable, copy-paste-ready bash and YAML across three concrete examples (ChaosEngine manifest, toxiproxy toxic injection, chaos-monkey config) with real flags and named resources, covering the common cases.

5 / 5

Workflow Clarity

A clear 5-step Core Workflow plus a 4-step worked example with explicit monitoring and a rollback/abort step, and a Safety Checklist enforcing validation checkpoints (verify baseline before injecting, expand only after validation, tested ≤30s rollback). The destructive-experiment context has an explicit validate→fix→retry feedback loop.

5 / 5

Progressive Disclosure

The body is a concise overview with a well-signaled reference table mapping five topics to five real, one-level-deep reference files (all verified to exist) with 'Load When' guidance, giving clear navigation without deep nesting.

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.

The description is exemplary: third-person voice, specific concrete actions and outputs, comprehensive natural trigger terms, and an explicit 'Use when' clause. It is concise yet complete with negligible conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises") plus concrete outputs ("runbooks, experiment manifests, rollback procedures, and post-mortem templates"), giving comprehensive coverage of the domain.

5 / 5

Completeness

Explicitly answers both what ("Designs chaos experiments... producing runbooks, experiment manifests...") and when ("Use when designing chaos experiments... or conducting game day exercises") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and product names users would actually say: "chaos experiments, resilience testing, blast radius control, game days, antifragile systems, fault injection, Chaos Monkey, Litmus Chaos".

5 / 5

Distinctiveness Conflict Risk

Occupies a clear chaos-engineering niche with distinct triggers (Chaos Monkey, Litmus Chaos, blast radius, game days) that are unlikely to fire for unrelated skills, 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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
Jeffallan/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.