Is the Executing Distributed System Tests skill free?

Yes. The skill itself is free from shenli/distributed-system-testing. SkillProof publishes the install command and an independent test verdict at no cost.

What is the Executing Distributed System Tests SkillProof Score?

8.0/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 6/10, docs & honesty 4/5.

How do I install Executing Distributed System Tests?

Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.

Can I use Executing Distributed System Tests with Cursor, Copilot, Gemini CLI, Codex or other AI tools?

The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.

Executing Distributed System Tests

Runs a designed distributed-systems test plan, scoring each run on a 10-state verdict taxonomy

by shenli · shenli/distributed-system-testing

Works with setup

Install — copy the command Download source ↗

Test report

Verdict: Works with setup
Score: 8.0/10
Tested: Jul 31, 2026
Environment: Claude Code 2.x (agent harness)
Upstream re-checked: Aug 10, 2026 · 2b694d1

Fetched SKILL.md via the GitHub API; frontmatter parses (name+description), and 3 body-referenced files returned HTTP 200 (verdict-taxonomy.md, green-but-broken-red-flags.md, findings-report-template.md). No hardcoded paths or security smells; ships valid plugin.json/marketplace.json. The full execution path (driving fault injection against a live cluster) needs Docker + a distributed SUT + a designed plan file I could not provide, so I measured the skill's distinctive verdict/report-discipline slice: given a boundary scenario with 4 surface arms where 2 passed and 2 were never reached, my baseline called it "PASS (with caveats), nothing blocks shipping", while following the body's per-arm downgrade rule forced "PARTIAL-surface, NOT a pass, should NOT ship" plus a surface-coverage table — the exact folded-surface failure the skill claims to prevent (exec_baseline.md vs exec_skill.md).

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

Installs cleanly 5/5
Triggers reliably 5/5
Output vs. baseline 6/10
Docs & honesty 4/5

What Executing Distributed System Tests does

Executes a previously designed distributed-systems test plan against a real or simulated cluster: discovers the SUT's existing test toolbox, drives workload and fault injection, captures per-scenario nemesis-landing evidence, and assigns one of ten verdict states with green-but-broken and weak-oracle audits before any PASS. Triggers on "execute the plan", "reproduce a distributed bug", "run stability/chaos tests", "validate a release end-to-end", or when a plan file exists at docs/testing-plans/. For boundary and fairness scenarios it scores each surface arm separately and applies a downgrade rule so an untested arm cannot fold into a scenario pass.

How to install Executing Distributed System Tests

git clone --depth 1 https://github.com/shenli/distributed-system-testing.git /tmp/executing-distributed-system-tests-src
mkdir -p ~/.claude/skills
cp -R /tmp/executing-distributed-system-tests-src/skills/executing-distributed-system-tests ~/.claude/skills/executing-distributed-system-tests
# Plugin-marketplace alternative: /plugin marketplace add shenli/distributed-system-testing  then install the 'distributed-testing-skills' plugin (installs both design + execute skills)
# To ACTUALLY RUN a plan end-to-end you additionally need, none of which the skill bundles:
#   - a plan file produced by the paired 'designing-distributed-system-tests' skill (the skill halts if oracles/budget tiers are missing)
#   - a distributed system-under-test repo to run against
#   - container + fault-injection tooling: docker/podman + compose, iptables/tc/netem, optionally toxiproxy/libfaketime

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger Executing Distributed System Tests

/executing-distributed-system-tests Runs a designed distributed-systems test plan, scoring each run on a 10-state verdict taxonomy

It also activates on plain-language prompts like these:

Execute the test plan against the staging cluster
Reproduce this distributed bug with chaos testing
Run tenant isolation tests before this release

Frequently asked questions

Is the Executing Distributed System Tests skill free?: Yes. The skill itself is free from shenli/distributed-system-testing. SkillProof publishes the install command and an independent test verdict at no cost.
Does Executing Distributed System Tests work with Claude Code?: We tested it with Claude Code 2.x (agent harness) on Jul 31, 2026. Verdict: Works with setup. Fetched SKILL.md via the GitHub API; frontmatter parses (name+description), and 3 body-referenced files returned HTTP 200 (verdict-taxonomy.md, green-but-broken-red-flags.md, findings-report-template.md). No hardcoded paths or security smells; ships valid plugin.json/marketplace.json. The full execution path (driving fault injection against a live cluster) needs Docker + a distributed SUT + a designed plan file I could not provide, so I measured the skill's distinctive verdict/report-discipline slice: given a boundary scenario with 4 surface arms where 2 passed and 2 were never reached, my baseline called it "PASS (with caveats), nothing blocks shipping", while following the body's per-arm downgrade rule forced "PARTIAL-surface, NOT a pass, should NOT ship" plus a surface-coverage table — the exact folded-surface failure the skill claims to prevent (exec_baseline.md vs exec_skill.md).
What is the Executing Distributed System Tests SkillProof Score?: 8.0/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 6/10, docs & honesty 4/5.
How do I install Executing Distributed System Tests?: Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Executing Distributed System Tests with Cursor, Copilot, Gemini CLI, Codex or other AI tools?: The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.