Designing Distributed System Tests
Claim-driven test plans for distributed and stateful systems, tied to fault-injection scenarios
Test report
- Verdict
- Tested · Works
- Score
- Tested
- Jul 31, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · dcddfef
Fetched SKILL.md via GitHub API/raw; frontmatter parses with name+description; spot-checked assets/plan-template.md, references/catalog-index.md, references/common-distributed-systems-pitfalls.md — all HTTP 200. No security smells (no curl|sh, base64, exfil). Trigger: judged 5 phrasings, all 5 correct. Output: designed one change-scoped task and wrote two real artifacts to scratchpad. Baseline gave a 7-item flat checklist whose crash test is "kill leader after ack, restart, value still there" with exit criterion "all tests pass in CI"; the skill-followed plan named claims C1-C4 plus a "missing claims" section, and scenario S1 injected SIGKILL "between value-WAL-fsync and dedup-WAL-fsync" with oracle "exactly ONE committed effect ... state comparison against model, not logs fine" — a double-commit-on-retry window the baseline never targets.
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 8/10
- Docs & honesty 5/5
What Designing Distributed System Tests does
Guides an agent to design a claim-driven test plan for a distributed or stateful system: it extracts the guarantees the system claims (durability, linearizability, idempotency, isolation, ordering), generates failure-mode hypotheses tied to each claim, picks techniques from a catalog, and emits a structured plan file with fault-injection scenarios and machine-checkable oracles. Triggers when asked what to test for a change, for a holistic release-validation plan, or how to test durability, partitions, tenant isolation, or fairness across shards or tenants.
How to install Designing Distributed System Tests
git clone --depth 1 https://github.com/shenli/distributed-system-testing.git /tmp/designing-distributed-system-tests-src
mkdir -p ~/.claude/skills
cp -R /tmp/designing-distributed-system-tests-src/skills/designing-distributed-system-tests ~/.claude/skills/designing-distributed-system-tests
# Companion skill in same repo: skills/executing-distributed-system-tests (runs the plan this one emits).
# Plugin marketplace alt: repo ships .claude-plugin/marketplace.json (plugin "distributed-testing-skills").
# No external deps to produce a plan; executing the plan needs docker/netem/etc. per the plan's env section.
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger Designing Distributed System Tests
-
/designing-distributed-system-testsClaim-driven test plans for distributed and stateful systems, tied to fault-injection scenarios
It also activates on plain-language prompts like these:
-
Design a test plan for this replicated database -
Write a fault matrix for this consensus system -
Create a stability plan for our messaging service
Frequently asked questions
- Is the Designing 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 Designing Distributed System Tests work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 31, 2026. Verdict: Tested · Works. Fetched SKILL.md via GitHub API/raw; frontmatter parses with name+description; spot-checked assets/plan-template.md, references/catalog-index.md, references/common-distributed-systems-pitfalls.md — all HTTP 200. No security smells (no curl|sh, base64, exfil). Trigger: judged 5 phrasings, all 5 correct. Output: designed one change-scoped task and wrote two real artifacts to scratchpad. Baseline gave a 7-item flat checklist whose crash test is "kill leader after ack, restart, value still there" with exit criterion "all tests pass in CI"; the skill-followed plan named claims C1-C4 plus a "missing claims" section, and scenario S1 injected SIGKILL "between value-WAL-fsync and dedup-WAL-fsync" with oracle "exactly ONE committed effect ... state comparison against model, not logs fine" — a double-commit-on-retry window the baseline never targets.
- What is the Designing Distributed System Tests SkillProof Score?
- 9.2/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 8/10, docs & honesty 5/5.
- How do I install Designing 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 Designing 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.