Executing Distributed System Tests

Runs the distributed systems test plans that the design skill produces. This is the execution half: it drives chaos scenarios, fault injection, partition tests, and consistency checks against your actual cluster or simulator. It won't improvise oracles or quietly skip steps that would let broken tests pass. Before reporting success it verifies the workload actually ran, the fault actually landed, and the checker actually observed something meaningful. Produces a structured findings report with a 10-state verdict system that distinguishes between real failures, flaky results, environmental problems, and gaps in test coverage. The process is deliberate: it catalogs your existing test tooling before writing anything new, asks about your environment capabilities up front, and runs boundary scenarios with separate verdicts per surface so an untested code path can't hide inside an aggregate pass.

GitHub stars: 217
last updated: May 22, 2026

View on GitHub

Install

$ npx -y skills add shenli/distributed-system-testing --skill executing-distributed-system-tests --agent claude-code

Installs into .claude/skills of the current project.

Files

Executing Distributed-System Tests

Pairs with designing-distributed-system-tests. That skill produces a plan; this skill runs it. The two communicate only through filesystem artifacts: the plan file in and a session directory plus findings report out.

The most common failure mode this skill is built to avoid: a run that produces a green checkmark without anyone having checked that the workload, the fault, and the oracle each did their job. The "green-but-broken" checks are not optional.

Process

1. Load the plan

If a plan file path was supplied, read it. If the user described a plan in conversation, extract the scenario list. If the plan is missing oracles or per-scenario budget tiers (Smoke / Hardening / Release, per the plan template's §7 scenario fields), halt — hand back to the design skill rather than improvise. Improvising an oracle in the moment is how green-but-broken results get produced.