CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/api-chaos-runner

Runs the project's existing API tests under injected network chaos - latency, timeouts, dropped connections, bandwidth caps, packet loss - via Toxiproxy (notes on Pumba / Gremlin / LitmusChaos). Builds a per-scenario chaos matrix and reports which assertions break under which conditions, verifying resilience patterns (retry, circuit-breaker, timeout, fallback). Unlike schemathesis-fuzzing and restler-fuzzing, which generate new tests from a schema, this drives your EXISTING example-based suite.

74

Quality

93%

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

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 dense, actionable skill body that earns its tokens: concrete toxics, a load-bearing chaos matrix, explicit validation via the control row, and a properly offloaded wiring reference. The only minor trim opportunity is the opening overview paragraph.

DimensionReasoningScore

Conciseness

The body is lean and mostly tables plus concrete content - tool comparison, chaos matrix, toxic-to-pattern mapping, anti-patterns, limitations - with only a brief overview paragraph and no padding explaining concepts Claude already knows.

3 / 3

Actionability

Concrete throughout: specific toxics with values (latency=1000ms, bandwidth=10kbps, reset_peer), a pattern-to-toxic mapping table, a worked example with a real verdict, and an executable runner script with toxiproxy-cli commands in the referenced wiring file.

3 / 3

Workflow Clarity

A clearly sequenced 7-step 'How to use' with explicit validation checkpoints - the no-toxic control row as baseline, the Expected column driving assertions, and the resilience matrix report as the feedback loop that surfaces missing resilience.

3 / 3

Progressive Disclosure

SKILL.md is an overview that cleanly points one level deep to the real, well-organized references/toxiproxy-wiring.md for docker-compose, proxy registration, toxic commands, and the runner script - navigation is clearly signaled and the file exists.

3 / 3

Total

12

/

12

Passed

Description

82%

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 specific, well-differentiated description with strong trigger terms, weakened only by the absence of an explicit 'Use when...' clause. Adding a trigger sentence would lift completeness to the top anchor.

Suggestions

Append an explicit trigger clause such as 'Use when the team needs to verify documented resilience patterns (retry, circuit-breaker, timeout, fallback) against existing API tests under simulated network failure.'

Front-load the 'when' before the differentiation sentence so the use case registers before the comparison to sibling skills.

Lead with a natural phrasing users actually say (e.g. 'Run network chaos / resilience testing against your existing API test suite') so the trigger term hits before the tooling detail.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - 'Runs the project's existing API tests under injected network chaos', 'Builds a per-scenario chaos matrix and reports which assertions break under which conditions, verifying resilience patterns (retry, circuit-breaker, timeout, fallback)' - matching the multi-action anchor.

3 / 3

Completeness

Clearly answers 'what does this do' but has no explicit 'Use when...' trigger clause; the differentiation sentence ('Unlike schemathesis-fuzzing...') is implicit guidance rather than an explicit when-to-use trigger, which caps completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes natural terms a user would say - 'network chaos', 'latency', 'timeouts', 'dropped connections', 'bandwidth caps', 'packet loss', 'retry', 'circuit-breaker', 'timeout', 'fallback' - giving good coverage of the domain's common phrasings.

3 / 3

Distinctiveness Conflict Risk

Explicitly carves a distinct niche from sibling skills ('Unlike schemathesis-fuzzing and restler-fuzzing, which generate new tests from a schema, this drives your EXISTING example-based suite'), making a wrong-skill trigger unlikely.

3 / 3

Total

11

/

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