Claude Code Skills·Claude Skills·The open SKILL.md registry for Claude
ClaudSkills / Engineering / testing

Executing Distributed System Tests

Category: Engineering  ·  Sub-category: testing  ·  Last updated:
Use when running a previously designed distributed-systems test plan against a real or simulated cluster — driving fault injection, workload, chaos scenarios, linearizability / consistency runs, durability tests, partition tests, crash-recovery tests, upgrade tests, performance/SLO runs, tenant isolation runs, boundary or authz runs, fairness / noisy-neighbor runs, or release validation. Also use when asked to "execute the plan", "reproduce a distributed bug", "run stability tests", "drive chaos", "validate a release end-to-end", "run the tenant isolation tests", "check fairness across tenants", or when a plan file exists at docs/testing-plans/ or any caller-specified location and needs to be run. Discovers the SUT's existing test toolbox (tools/, scripts/, runbooks) and uses it rather than reinventing, captures nemesis landing evidence per scenario, runs the green-but-broken and weak-oracle audits before any PASS, and (for boundary or fairness scenarios with §7.M.S arms in the plan) runs each surface arm separately with its own verdict and applies a downgrade rule so the aggregate verdict cannot silently fold an untested surface into a passing scenario. Produces a session directory of raw artifacts plus a structured findings report carrying a 10-state verdict (PASS-smoke / PASS-hardening / FAIL-reproducible / FAIL-nondeterministic / INCONCLUSIVE-env / INCONCLUSIVE-oracle-too-weak / INCONCLUSIVE-fault-not-proven / PARTIAL-surface / PARTIAL-model / NOT-RUN), a SUT / harness / checker / environment blame classification per finding, a TaxDC bug-type tag, per-arm Surface coverage table, and Release-budget disclosures.

From the source SKILL.md

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.

What this skill does

Executing Distributed System Tests is a community-contributed Claude Code skill in the testing sub-category. It ships as a SKILL.md file that Claude Code auto-discovers under ~/.claude/skills/executing-distributed-system-tests/ and loads when your prompt matches the skill's trigger.

When to invoke it: Use when running a previously designed distributed-systems test plan against a real or simulated cluster — driving fault injection, workload, chaos scenarios, linearizability / consistency runs, durability tests, partition tests, crash-recovery tests, upgrade tests, performance/SLO runs, tenant isolation runs, boundary or authz runs, fairness / noisy-neighbor runs, or release validation. Also use when asked to "execute the plan", "reproduce a distributed bug", "run stability tests", "drive chaos", "validate a release end-to-end", "run the tenant isolation tests", "check fairness across tenants", or when a plan file exists at docs/testing-plans/ or any caller-specified location and needs to be run.

Who uses this skill

The Executing Distributed System Tests Claude Code skill is built for software engineers, backend developers, full-stack teams, and technical leads building and maintaining production systems. It's part of ClaudSkills (also referred to as Claude Skills or Claude Code Skills) — the open community-curated registry of 93,000+ SKILL.md files for Anthropic's Claude Code agent and the wider Claude ecosystem (Claude API, Claude Agent SDK).

How to install

Free

Manual install (2 steps)

mkdir -p ~/.claude/skills/executing-distributed-system-tests
curl -L https://claudskills.com/skills/executing-distributed-system-tests/SKILL.md \
  -o ~/.claude/skills/executing-distributed-system-tests/SKILL.md

Or just download SKILL.md directly and drop it into ~/.claude/skills/executing-distributed-system-tests/. Claude Code auto-discovers it on next session.

Skills live at ~/.claude/skills/executing-distributed-system-tests/SKILL.md on macOS/Linux, or %USERPROFILE%\.claude\skills\executing-distributed-system-tests\SKILL.md on Windows. See the full install guide for step-by-step instructions.

Telegram

📱 Install from your phone or desktop Telegram

Open @claudskills_bot on Telegram, tap Open Desktop App, and the desktop app installs this skill for you. Or share the bot link with a colleague — they get the same one-tap install. Learn more →

Pro

One-click install via the desktop app

The ClaudSkills desktop app installs any skill directly into ~/.claude/skills/ with one click — no terminal required. Pro starts at $9/mo or $149 lifetime.

Pro

For the full experience including quality scoring and one-click install features for each skill — upgrade to Pro.

See pricing → Download desktop app

Frequently asked questions

How do I install the Executing Distributed System Tests Claude Code skill?
Install via the ClaudSkills desktop app (one click) or copy SKILL.md from the source repository to ~/.claude/skills/executing-distributed-system-tests/SKILL.md and restart Claude Code. Both flows are detailed at claudskills.com/install/.
What does the Executing Distributed System Tests skill do?
Use when running a previously designed distributed-systems test plan against a real or simulated cluster — driving fault injection, workload, chaos scenarios, linearizability / consistency runs, durability tests, partition tests, crash-recovery tests, upgrade tests, performance/SLO runs, tenant isolation runs, boundary or authz runs, fairness / noisy-neighbor runs, or release validation. Also use when asked to "execute the plan", "reproduce a distributed bug", "run stability tests", "drive chaos", "validate a release end-to-end", "run the tenant isolation tests", "check fairness across tenants", or when a plan file exists at docs/testing-plans/ or any caller-specified location and needs to be run. Discovers the SUT's existing test toolbox (tools/, scripts/, runbooks) and uses it rather than reinventing, captures nemesis landing evidence per scenario, runs the green-but-broken and weak-oracle audits before any PASS, and (for boundary or fairness scenarios with §7.M.S arms in the plan) runs each surface arm separately with its own verdict and applies a downgrade rule so the aggregate verdict cannot silently fold an untested surface into a passing scenario. Produces a session directory of raw artifacts plus a structured findings report carrying a 10-state verdict (PASS-smoke / PASS-hardening / FAIL-reproducible / FAIL-nondeterministic / INCONCLUSIVE-env / INCONCLUSIVE-oracle-too-weak / INCONCLUSIVE-fault-not-proven / PARTIAL-surface / PARTIAL-model / NOT-RUN), a SUT / harness / checker / environment blame classification per finding, a TaxDC bug-type tag, per-arm Surface coverage table, and Release-budget disclosures.
Is this skill free to install?
Yes. ClaudSkills is an open registry — every skill keeps its source repository's license, and manual install via copy is free. ClaudSkills Pro ($9/mo, $79/yr, or $149 one-time) adds one-click install via the desktop app and a multi-signal Quality Score.
When should I use the Executing Distributed System Tests skill?
Use Executing Distributed System Tests when your Claude Code task falls under the Engineering category — specifically in the testing area. Claude Code auto-discovers installed skills and invokes the right one based on the task description, so you can also ask Claude directly (e.g. "use Executing Distributed System Tests" or describe the task and let Claude pick). Browse related skills at /category/engineering/.
What is a Claude Code skill and how does the Executing Distributed System Tests skill fit in?
A Claude Code skill is a SKILL.md file that lives under ~/.claude/skills/<name>/ and tells the Claude Code CLI agent how to perform a specific task (instructions, prompts, allowed tools). Skills are auto-discovered at session start. Executing Distributed System Tests is one of 67,000+ skills indexed in the open ClaudSkills catalog, classified under the Engineering category. Learn more at /learn/what-is-a-claude-skill/.

Attribution & license

Cite this skill

If you reference this skill in a blog post, paper, or documentation, you can cite it as:

APA
shenli. (2026). Executing Distributed System Tests [Claude Code skill]. ClaudSkills. https://claudskills.com/skills/executing-distributed-system-tests/
BibTeX
@misc{executing-distributed-system-tests-2026,
  author    = {shenli},
  title     = {Executing Distributed System Tests [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/executing-distributed-system-tests/}
}

Embed this skill

Promote, attribute, or link this skill from your own README, blog post, or documentation. All three snippets are free to use — no sign-up, no API key. More distribution surfaces →

Badge
[![ClaudSkills](https://claudskills.com/badge/executing-distributed-system-tests.svg)](https://claudskills.com/skills/executing-distributed-system-tests/?utm_source=badge&utm_medium=readme&utm_campaign=skill_badge)
<script>
<script src="https://claudskills.com/embed/executing-distributed-system-tests.js" async></script>
<iframe>
<iframe src="https://claudskills.com/embed/executing-distributed-system-tests.html" width="100%" height="160" frameborder="0" loading="lazy" title="ClaudSkills: Executing Distributed System Tests"></iframe>

Free. No spam. Unsubscribe in one click.

More Engineering skills

Browse all Engineering skills in the ClaudSkills registry, or explore these other picks from the same category:

Browse all Engineering skills → Top 100 skills
Part of ClaudSkills — the open registry for Claude Skills & Claude Code Skills.  ·  What's New  ·  Install guide  ·  About  ·  llms.txt

Part of Acreator Store — Adam Lankamer's AI tools: PerfectStudio · Ucaption · UTagger · AutoXPoster · TestYourSkills · AutomationFlows · Au Naturel · Telegram @acreatorstore

Categories

Use cases

Popular tags

Learn

Site