Summary
Takes the claim-driven approach to distributed system testing and turns it into a structured plan. You feed it a PR, feature, or whole system, and it mines your docs and code for guarantees (linearizability, durability, tenant isolation, idempotency), then generates hypotheses that try to falsify those claims under faults. It knows the techniques that matter (Jepsen, deterministic simulation, chaos injection, property testing) and organizes scenarios by what could actually break in production: partition tolerance, crash recovery, noisy neighbors, upgrade safety. For project-wide plans it inventories existing tests and does gap analysis. The output is a Markdown file with hypothesis-driven scenarios you can hand off to the executing skill or run yourself. Honest take: this encodes the kind of paranoid, literature-informed testing discipline most teams skip because they don't know where to start.
Install to Claude Code
npx -y skills add shenli/distributed-system-testing --skill designing-distributed-system-tests --agent claude-codeInstalls into .claude/skills of the current project.
Connect Claude to +800M contacts, +150M companies. Find & Enrich leads in chat.
Try For Free →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
An agent that runs the SEO playbooks that move rankings and ships PRs you control.
Get founding access →Files
SKILL.md
Select a file.
Featured
Connect Claude to +800M contacts, +150M companies. Find & Enrich leads in chat.
Try For Free →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →An agent that runs the SEO playbooks that move rankings and ships PRs you control.
Get founding access →
