CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/toxiproxy-chaos

Configures Toxiproxy for TCP-level fault injection - runs as a sidecar / proxy between client and upstream, applies toxics (latency, bandwidth, slow_close, timeout, slicer, limit_data, reset_peer) via control API. Focused on the proxy itself rather than an API-level chaos runner, including non-test usage (chaos in dev environments, integration tests, pre-prod simulation). Use when the team needs TCP-precise fault injection in development / integration environments without K8s or commercial tooling.

71

Quality

89%

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

82%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 body with executable examples across CLI, SDK, and compose. The main gaps are the absence of explicit verification checkpoints and no use of separate reference files for a ~195-line skill.

Suggestions

Add an explicit verification step after applying a toxic (e.g., `toxiproxy-cli list` / `toxiproxy-cli inspect` to confirm the toxic is active, then observe the fault effect) to strengthen workflow_clarity.

Consider moving the full toxic catalog table and/or the multi-language SDK snippets into a separate references file, keeping SKILL.md as a leaner overview, to improve progressive_disclosure.

Trim the opening README quote and obvious code comments to tighten conciseness toward the lean anchor.

DimensionReasoningScore

Conciseness

The body is mostly lean — compact tables, tight code blocks, no padding of concepts Claude already knows — but the overview README quote and inline code comments ('# Pull the official image', '# Run as a daemon') are minor instances that could be trimmed, keeping it just below the 5 anchor.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout — curl/docker/toxiproxy-cli commands, Python and Node SDK snippets, and a docker-compose block — with specific examples covering the common latency/bandwidth/timeout/direction cases.

5 / 5

Workflow Clarity

A clear linear Step 1–8 sequence with good sectioning, but there is no explicit verification checkpoint (e.g., confirm a toxic is applied with `toxiproxy-cli list` or observe latency), which leaves it just short of the 5 anchor.

4 / 5

Progressive Disclosure

Well-organized sections (Overview, When to use, Steps 1–8, Anti-patterns, Limitations, References) with clearly signaled references to the upstream README and sister skills, but no bundle files exist so nothing is split out, leaving it below the 5 anchor that expects content appropriately separated into files.

4 / 5

Total

17

/

20

Passed

Description

92%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, specific description that clearly states capabilities, an explicit use-when trigger, and boundaries against related skills. The only gap is moderate coverage of natural trigger synonyms.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'runs as a sidecar / proxy between client and upstream, applies toxics (latency, bandwidth, slow_close, timeout, slicer, limit_data, reset_peer) via control API' — with a comprehensive catalog of specific toxic types, matching the 5 anchor for multiple specific concrete actions.

5 / 5

Completeness

It explicitly answers both what ('Configures Toxiproxy for TCP-level fault injection ... applies toxics ... via control API') and when ('Use when the team needs TCP-precise fault injection in development / integration environments without K8s or commercial tooling') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage with natural phrases like 'TCP-level fault injection', 'chaos', 'development / integration environments', and 'pre-prod simulation', but common synonyms such as 'simulate network failure/latency', 'resilience testing', and 'chaos engineering' are missing, so it sits below the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — 'Focused on the proxy itself rather than an API-level chaos runner' and 'without K8s or commercial tooling' — explicitly boundary-stating against adjacent skills, giving minimal conflict risk.

5 / 5

Total

19

/

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

Reviewed

Table of Contents