CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/toxiproxy-chaos

Use for any question or task about simulating network faults such as latency, timeouts or dropped connections in integration tests or dev environments, including adding Toxiproxy to a compose file, without Kubernetes or paid tools. Runs Toxiproxy between client and upstream and applies latency, bandwidth, slow close, timeout, slicer, data limit and reset toxics through its control API.

Quality

84%

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

Overview
Quality
Evals
Security
Files

Quality

Content

75%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: sequenced steps, executable examples for every interface, and useful anti-pattern/limitation tables. It falls short of top marks on small accuracy details (comment/command mismatches), the absence of an explicit verify step, and inline SDK material that could be externalized.

Suggestions

Fix the comment/command mismatches in Step 4: pair 'Force the proxy down' with the `down` toxic (or correct the comment), and describe the single-toxic `toxiproxy-cli toxic remove` command accurately rather than as 'Remove all toxics'.

Add an explicit verification checkpoint after Step 2 (e.g., `toxiproxy-cli list` or `curl http://localhost:8474/proxies`) so users confirm the proxy is healthy before injecting toxics.

Move the per-language SDK examples (Step 6) into a references/ file (e.g., references/sdks.md) and keep one representative snippet inline, reducing SKILL.md footprint and the 'When to use' / 'Use cases' overlap.

DimensionReasoningScore

Conciseness

The body is dominated by executable commands and code with almost no explanation of concepts Claude already knows, but the 'When to use' bullets overlap the 'Step 8 Use cases' table and a few sections restate the same point — minor trimming opportunities that fit 4's 'minor instances of over-explanation'.

4 / 5

Actionability

Docker, curl, CLI, Python/Node SDK, and compose examples are concrete and executable, but two comment/command mismatches ('Force the proxy down' paired with a timeout toxic; 'Remove all toxics' describing a single named removal) leave minor gaps, placing it between 4 and 5 but closer to 4.

4 / 5

Workflow Clarity

Steps 1-8 are cleanly sequenced (install → proxy → toxics → directions → SDKs → compose → use cases) with explicit cleanup guidance (anti-patterns table, proxy.destroy()), but there is no explicit verification checkpoint such as confirming proxy health before injecting toxics — minor validation gaps per the 4 anchor, short of 5's explicit validation steps.

4 / 5

Progressive Disclosure

No bundle files exist and the ~190-line body has clear, well-signaled sections with one-level external pointers, but at this length the multi-language SDK catalog (Step 6) and toxic details could live in reference files — good structure with minor organization gaps rather than the ideal split of the 5 anchor.

4 / 5

Total

16

/

20

Passed

Description

88%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 description: concrete capabilities, explicit 'Use for' triggers, and a clearly staked-out niche. Its only weaknesses are missing common synonyms (notably 'chaos testing') in the trigger terms and slight boundary blur with the sister test-suite skill.

DimensionReasoningScore

Specificity

The description enumerates the full toxic catalog ('latency, bandwidth, slow close, timeout, slicer, data limit and reset toxics'), the control API mechanism, and compose-file integration — multiple specific concrete actions with comprehensive coverage, matching the 5 anchor rather than 4's 'minor gaps'.

5 / 5

Completeness

It explicitly answers 'when' ('Use for any question or task about simulating network faults... in integration tests or dev environments') and 'what' ('Runs Toxiproxy between client and upstream and applies... toxics through its control API') with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('simulating network faults', 'latency', 'timeouts', 'dropped connections', 'integration tests', 'compose file'), but common variations users would say — 'chaos testing', 'resilience testing', 'slow network', 'packet loss' — are absent, so it falls short of the comprehensive-synonyms 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The Toxiproxy niche is clear and K8s/paid tools are explicitly excluded, but the broad 'any question or task... in integration tests' phrasing risks overlap with the closely related test-suite-driven sister skill, matching 4's 'minor overlap risk' rather than 5's 'minimal conflict risk'.

4 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

On this page