CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chaos-experiment

Interactive wizard to design and validate a chaos engineering experiment

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/chaos-experiment/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 body is an efficient, well-structured operational spec: concrete script commands, a clear four-step sequence, and explicit pre/post-conditions with no padding. The main gaps are undefined shell variables in the implementation block and an unspecified interactive input-gathering step, which keep actionability and workflow clarity just below excellent. Overall a strong, near-copy-paste-ready skill body.

Suggestions

Specify how inputs are gathered in Step 1 (e.g., "ask the user for target, hypothesis, attack, magnitude, and duration before running the script") and define each shell variable's source.

Add an explicit feedback loop after the blast radius step, e.g., "If risk is RED, reduce magnitude or duration and re-run blast_radius_calculator.py before rendering the plan."

DimensionReasoningScore

Conciseness

The body is lean with zero concept explanations — it never explains what chaos engineering is, and sections like Usage, Output, Pre-conditions, and Post-conditions each carry only operational facts. Every token earns its place, matching the anchor-5 example of tight, code-first content.

5 / 5

Actionability

Concrete python invocations with real flags (e.g., "--target $TARGET --hypothesis $HYPOTHESIS --abort-if $ABORT") and a worked usage example ("--target checkout-svc --attack latency"), but the shell variables are never defined and Step 1's "gather inputs interactively" doesn't specify how. Mostly executable with minor gaps — anchor 4, not 5, since it isn't fully copy-paste ready.

4 / 5

Workflow Clarity

Steps 1-4 are clearly sequenced with inline comments, and the PROCEED/REDUCE/ABORT recommendation acts as a decision checkpoint. Not 5 because there is no explicit feedback loop (e.g., recalculate blast radius after reducing magnitude on a RED result); not 3 because the checkpoints are present and the skill plans rather than executes the risky operation.

4 / 5

Progressive Disclosure

This is a compact, well-organized skill with clean sections and no need for external references — the referenced scripts belong to the wrapped chaos-engineering skill, and no bundle files exist in this skill's directory. Per the simple-skill guideline, well-organized sections alone warrant a 5.

5 / 5

Total

18

/

20

Passed

Description

53%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 gives a clear, concise statement of what the skill does in a distinct niche, but it omits any "when to use" trigger guidance and lacks synonym coverage. Specificity stops at two generic verbs (design, validate) even though the body reveals richer concrete capabilities. Adding an explicit use-when clause and a few natural trigger phrases would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user wants to design a chaos experiment, run a game day, or plan a fault-injection test against a service."

Surface the concrete capabilities from the body: "Produces an experiment plan, calculates blast radius against the error budget, validates abort criteria, and outputs a peer-review-ready markdown plan."

Include natural synonyms users would say — "chaos test", "failure injection", "resilience testing", "blast radius" — to improve trigger term coverage.

DimensionReasoningScore

Specificity

"design and validate a chaos engineering experiment" names the domain plus exactly two concrete actions; "interactive wizard" is a form factor, not an action. Matches anchor 3 (1-2 concrete actions, not comprehensive) rather than 4, which requires several listed actions such as plan generation, blast radius calculation, or abort-criteria validation.

3 / 5

Completeness

The "what" is clear ("Interactive wizard to design and validate a chaos engineering experiment"), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not score 4 because the "when" is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

"chaos engineering experiment" is a natural phrase a user would say, but the description misses common variations like "game day", "fault injection", "resilience testing", or "blast radius". This fits anchor 3 (relevant keywords but missing common variations) rather than 4 (good coverage with only a few terms missing).

3 / 5

Distinctiveness Conflict Risk

"chaos engineering experiment" carves a distinct niche with minimal conflict risk against unrelated skills. Not 5 because as a wrapper around the broader chaos-engineering skill it has minor overlap with that closely related skill, matching anchor 4.

4 / 5

Total

13

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/chaos-experiment/SKILL.md

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.