Flaky Test Diagnoser
Systematically diagnoses why a test is flaky by running multi-run experiments, isolation tests, ordering permutations, and timing analysis. Use when the user says a test is flaky, intermittent, non-deterministic, randomly failing, passes sometimes, or asks to debug test flakiness.
Install
/plugin marketplace add npow/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add npow/claude-skills --skill flaky-test-diagnosergit clone --depth 1 https://github.com/npow/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/flaky-test-diagnoser ~/.claude/skills/flaky-test-diagnoserPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Flaky Test Diagnoser Runs competing-hypothesis experiments to isolate the true root cause of a flaky test. Produces a diagnosis with reproducible evidence — or an honest inconclusive label. Never promotes a guess to "root cause." This is a tracing skill, not a fixer. The goal is to explain **why** the test is intermittent with falsifiable evidence, not to jump into patching code. ## Execution contracts **Subagent watchdog:** any time this skill spawns a test-running subagent via `run_in_background=true` (multi-run protocols, ordering bisection, distinguishing experiments), it MUST be armed with a staleness monitor per [`_shared/subagent-watchdog.md`](../_shared/subagent-watchdog.md). Use Flavor A (Monitor tail per spawn) with thresholds `STALE=15 min`, `HUNG=45 min` — test suites can legitimately take a long time, especially with N≥10 reruns, but a 45-min silent window is pathological. `TaskOutput` status reports PID liveness only; output-file mtime is the ground truth for progress. Contract inheritance: `timed_out_heartbeat` joins this skill's termination vocabulary as a peer of `blocked_by_environment` (watchdog kill is a different failure class — the test-runner subagent hung, not the test environment). A watchdog-killed experiment contributes zero runs to the N≥10 count; the skill must retry or escalate. ## Workflow
Details
- Skill name
flaky-test-diagnoser- Repository
- npow/claude-skills
- Path
flaky-test-diagnoser/SKILL.md- License
- Apache-2.0
- Repo updated
- 20 August 2026
FAQ
What does the Flaky Test Diagnoser skill do?
Systematically diagnoses why a test is flaky by running multi-run experiments, isolation tests, ordering permutations, and timing analysis. Use when the user says a test is flaky, intermittent, non-deterministic, randomly failing, passes sometimes, or asks to debug test flakiness.
How do I install the Flaky Test Diagnoser skill?
Claude Code plugin: /plugin marketplace add npow/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Flaky Test Diagnoser popular?
It lives in npow/claude-skills, which has 5 GitHub stars and 1 forks.
Related skills
Autopilot
5npow/claude-skills
Use when the user says "autopilot", "build this", "make it", "ship it", "just do it", "do it", "implement this", or gives a vague idea, spec, task list, or bug fix and expects autonomous execution. Handles decomposition, agent coordination, and verification automatically. "build me end to end", "go from idea to code", "do everything", "run this autonomously". Follows the Spec-Driven Development workflow: specify → clarify → plan → tasks → analyze → implement.
Build Python Library
5npow/claude-skills
Implements pip-installable Python libraries from scratch using src layout, pyproject.toml, and pytest. Use when the user asks to build, create, implement, or scaffold a Python library, package, pip package, middleware, SDK, or wrapper. Covers project scaffolding, proxy/wrapper patterns, provider-agnostic interfaces, async/sync support, and test infrastructure.
Canon Design Review
5npow/claude-skills
Architecture-level design review evaluating 15 Tier 2 best practices drawn from DDD (Evans), POEAA (Fowler), Release It! (Nygard), DDIA (Kleppmann), Team Topologies (Skelton/Pais), How Buildings Learn (Brand), and Systemantics (Gall). Auto-invoke when a PR touches: - Service definitions, infrastructure code, API boundaries, or database schemas - Files matching **/architecture*, **/design*, **/api/*, **/schema*, **/migrations/* - Any directory named services/, infrastructure/, platform/, domain/, core/ Also invoke when the user says: - "design review", "architecture review", "review the design"
Gen Crash Test
5npow/claude-skills
Crash-recovery test for the sagaflow generic interpreter. Multiple sequential tool calls with a sleep in the middle.
Deep QA Ensemble V1
5npow/claude-skills
Use when the user asks to review with ensemble judges, or explicitly requests the ensemble variant of deep-qa. Benchmark variant that uses three heterogeneous providers for severity judging instead of a single judge. Same triggers as deep-qa but with multi-provider ensemble scoring.
Gen Smoke
5npow/claude-skills
Smoke test for the sagaflow generic interpreter. Writes a greeting to report.md and ends turn. Use only for testing the interpreter round-trip.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.