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.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryEngineeringStars0
About this skill
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.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
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.
About this listing
Category
Engineering
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI