CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fix

Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

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

A well-structured, lean, and actionable debugging workflow with a genuine verify-and-retry feedback loop. The main defects are the dangling reference to a nonexistent `flaky-taxonomy.md` (step 3 would fail to load it) and a few vague fix bullets in the Environment category.

Suggestions

Remove the "Load `flaky-taxonomy.md` from this skill directory" instruction (the taxonomy table is already inlined) or actually create the file under references/ so the reference resolves.

Replace "Compare CI vs local screenshots/traces" with a concrete command, e.g. `npx playwright test <file> --trace=on` locally and downloading the CI trace artifact for side-by-side comparison.

De-duplicate the burn-in command: step 5 repeats step 1's `--repeat-each=10` command verbatim; referencing the earlier command or a shared snippet would trim tokens.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: bare commands, a compact diagnostic table, and terse bullet fixes with no padding or explanations of concepts Claude already knows. Only the burn-in command repeated verbatim in step 5 is trimmable, which is not enough to drop below the top anchor.

5 / 5

Actionability

Mostly executable: copy-paste commands (`npx playwright test <file> --repeat-each=10 --reporter=list`, `--trace=on --retries=0`) and specific fixes (`waitForTimeout()` → web-first assertions, `toBeVisible()`, `retries: 2`, `trace: 'on-first-retry'`). Gaps: step 3 says "Load `flaky-taxonomy.md` from this skill directory" but no such file exists in the bundle, and "Compare CI vs local screenshots/traces" gives no concrete command — anchor 4 (minor gaps), not 5.

4 / 5

Workflow Clarity

Six clearly sequenced steps (reproduce → trace → categorize → fix → verify → prevent) with an explicit validation checkpoint and feedback loop: "All 10 must pass. If any fail, go back to step 3." This matches the top anchor with error-recovery loops.

5 / 5

Progressive Disclosure

Section structure is good, but the only external reference is broken: `flaky-taxonomy.md` does not exist in the skill directory (no references/ or other bundle directories), and the taxonomy is simultaneously inlined as a table. This sits between anchor 2 (references misplaced/buried) and anchor 4 (minor organization gaps) — structure is present but the one reference dangles.

3 / 5

Total

17

/

20

Passed

Description

90%Weight 40%Scale 1-5

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

A strong description: concrete, third-person, with an explicit 'Use when...' clause backed by seven natural trigger phrases. The only weakness is that it states a single capability (fix) rather than enumerating several specific actions like diagnosing, categorizing, or verifying.

DimensionReasoningScore

Specificity

"Fix failing or flaky Playwright tests" names the domain (Playwright) and one concrete action (fix), matching the 'domain and 1-2 concrete actions, but not comprehensive' anchor. It does not list several specific actions, so anchor 4 does not fit.

3 / 5

Completeness

Explicitly answers both what ("Fix failing or flaky Playwright tests") and when ("Use when user says...") with concrete trigger phrases, exactly matching the top anchor's example pattern.

5 / 5

Trigger Term Quality

Seven natural quoted phrases ("fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", "intermittent failure") comprehensively cover how users would phrase this need, including synonyms and colloquial variants.

5 / 5

Distinctiveness Conflict Risk

Playwright is a named niche and the triggers are specific to failing/flaky test debugging, giving a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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.

Repository

alirezarezvani/claude-skills

Path

engineering-team/playwright-pro/skills/fix/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.