CtrlK
BlogDocsLog inGet started
Tessl Logo

condition-based-waiting

Anti-flaky test patterns: wait on conditions, not timeouts. Trigger: flaky tests, waitForTimeout, race conditions.

76

Quality

93%

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

100%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.

Excellent content: executable, well-organized pattern catalog that respects the reader's competence and cleanly offloads edge-case detail to a single real reference file. No meaningful gaps relative to the rubric.

DimensionReasoningScore

Conciseness

Lean, code-forward body that assumes Playwright competence with no padding explaining what tests or libraries are; every section earns its place.

5 / 5

Actionability

Fully executable copy-paste TypeScript patterns across eight waiting scenarios, anti-patterns with BAD/GOOD pairs, and a decision matrix mapping needs to concrete APIs.

5 / 5

Workflow Clarity

A single-purpose pattern catalog with an unambiguous decision matrix and a sequenced integration example; the simple-skill exception applies as no destructive or batch operation requires validation checkpoints.

5 / 5

Progressive Disclosure

Concise overview body with one clearly-signaled one-level-deep reference (references/patterns-and-implementation.md, which exists and holds deeper edge cases) plus external Playwright docs, giving easy navigation.

5 / 5

Total

20

/

20

Passed

Description

87%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 concise, well-structured description that states the capability clearly and pairs it with explicit, natural trigger terms. Minor room to enumerate a few more concrete actions, but completeness and distinctiveness are strong.

DimensionReasoningScore

Specificity

Names the domain and a concrete principle ("wait on conditions, not timeouts") but enumerates limited concrete actions rather than a comprehensive list, fitting the 'several specific actions; minor gaps' anchor.

4 / 5

Completeness

Explicitly answers both what ("Anti-flaky test patterns: wait on conditions, not timeouts") and when ("Trigger: flaky tests, waitForTimeout, race conditions") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Trigger: flaky tests, waitForTimeout, race conditions" supplies natural user phrasing and API names; good coverage with a few synonyms missing, matching the 'good keyword coverage' anchor.

4 / 5

Distinctiveness Conflict Risk

Niche focus on condition-based waiting with distinct, specific triggers minimizes overlap 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
YoizenSA/dev-ai-workflow
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.