Name: testland/flake-remediation-guide
Rating: 76 (1 reviews)
Author: testland

testland/flake-remediation-guide

Provides concrete code-level fixes for each of the eight recurring flake patterns in flake-pattern-reference: replacing fixed sleeps with framework auto-waits, isolating state in beforeEach fixtures, stable role-based locators, mocking network + clock, seeding RNG, closing leaked resources, and the per-worker DB-schema fix for shared parallel state. Use when a flake is already classified by pattern and you need the specific code change to apply; to classify the pattern first use flake-pattern-reference or flake-axis-bisection, and to quarantine the test while the fix is in review use flaky-test-quarantine.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and well-structured with executable code and a clean overview-to-reference split. The one gap is workflow_clarity: the re-measure step is presented as advice rather than an explicit validation checkpoint that gates shipping the fix.

Suggestions

Turn the 'Re-measure at a real depth' step into an explicit validation gate: state that the fix should not be considered resolved until a clean run at the chosen N (e.g. N=300 for 1% tolerance) is observed, and that a clean 0/20 is a non-result.

Add a short 'Verify the fix' checklist item after the code change — e.g. confirm the previously-failing test passes at the chosen N across reruns — so the feedback loop is a hard checkpoint rather than guidance.

Optionally note what to do when re-measurement still shows flakes (fall back to flake-axis-bisection to re-classify) so the error-recovery path is explicit.

Dimension	Reasoning	Score
Conciseness	The body is lean — each pattern is root cause plus executable before/after code with inline citations, with no 'what is a flake' preamble; the only mild repetition is the quick-reference table reusing APIs already shown, which aids scanning.	3 / 3
Actionability	Provides fully executable TypeScript/JavaScript before/after snippets with named APIs (getByRole, toBeVisible, beforeEach, workerIndex, try/finally) and config examples for both Playwright and Cypress, copy-paste ready.	3 / 3
Workflow Clarity	A clear 5-step 'How to use' sequence and a worked example exist, but re-measurement is framed as guidance rather than an explicit pass/fail validation gate before shipping the fix; the destructive-ish 'ship the fix' step lacks a hard checkpoint.	2 / 3
Progressive Disclosure	SKILL.md keeps patterns 1-4, a worked example, and a quick-reference table inline while splitting patterns 5-8 into two clearly-signaled, one-level-deep references that exist as real files under references/.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and well-differentiated: it lists concrete fixes, provides an explicit 'Use when' trigger keyed on prior pattern classification, and disambiguates from sibling skills. It uses third person and avoids fluff, so it lands at the top of the scale on every dimension.

Dimension	Reasoning	Score
Specificity	Enumerates seven concrete code-level fixes (replace fixed sleeps with auto-waits, isolate state in beforeEach, role-based locators, mock network+clock, seed RNG, close leaked resources, per-worker DB-schema), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly states both what the skill does (code-level fixes for eight flake patterns) and when to use it ('Use when a flake is already classified by pattern and you need the specific code change to apply'), with an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Uses natural practitioner phrasing ('flake is already classified by pattern', 'code change to apply', 'flaky test') and names the gating condition, giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (apply-the-fix, gated on prior classification) and explicitly routes classification, measurement, and quarantine to named sibling skills, making wrong-skill triggering unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

5 days ago

Table of Contents

Discovery Implementation Validation