CtrlK
BlogDocsLog inGet started
Tessl Logo

e2e-testing-patterns

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

81

1.27x
Quality

74%

Does it follow best practices?

Impact

93%

1.27x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/developer-essentials/skills/e2e-testing-patterns/SKILL.md

The canonical home for this skill is e2e-testing-patterns in wshobson/agents

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 rich, highly actionable patterns reference with excellent executable code, undermined by some redundant well-known explanations and by references to bundle files that do not actually exist. Adding the missing bundle files (or inlining their content) would meaningfully raise the progressive_disclosure and conciseness scores.

Suggestions

Provide the missing bundle files referenced at the end (references/playwright-best-practices.md, references/cypress-best-practices.md, references/flaky-test-debugging.md, assets/e2e-testing-checklist.md, assets/selector-strategies.md, scripts/test-analyzer.ts) so the signaled navigation resolves.

Trim the testing-pyramid diagram and 'Best Practices'/'Common Pitfalls' lists that restate widely known testing truisms Claude already knows; keep only non-obvious guidance.

Add an explicit validate->fix->retry feedback loop to the debugging workflow (e.g., run a single test, inspect trace, fix selector/wait, re-run until green) to lift workflow_clarity.

DimensionReasoningScore

Conciseness

The bulk is valuable executable code, but the intro restates the description and the testing-pyramid, best-practices, and common-pitfalls sections restate well-known truisms Claude already knows, adding unnecessary explanation.

3 / 5

Actionability

Extensive copy-paste-ready, executable examples (config, page objects, fixtures, waits, network mocking, intercept, visual regression, sharding, a11y, debugging) cover the common cases with only minor stub spots.

5 / 5

Workflow Clarity

The debugging section provides a numbered sequence, but this is a patterns reference rather than a single orchestrated pipeline, and there are no explicit validate-fix-retry feedback loops for risky operations.

3 / 5

Progressive Disclosure

The body signals one-level-deep references (references/, assets/, scripts/), but none of the referenced files or directories exist in the bundle, so navigation to the detailed material fails.

2 / 5

Total

13

/

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 strong, well-scoped description that clearly states capabilities and trigger conditions with named tools, distinguishing it from generic testing skills. Minor specificity gains are possible by replacing outcome-fluff with distinct operations.

DimensionReasoningScore

Specificity

Names the domain (Playwright, Cypress, E2E) and several concrete actions ('build reliable test suites', 'catch bugs', 'improve confidence', 'enable fast deployment'), with minor gaps since some actions are outcomes rather than distinct operations.

4 / 5

Completeness

Explicitly answers both 'what' ('Master end-to-end testing... build reliable test suites...') and 'when' ('Use when implementing E2E tests, debugging flaky tests, or establishing testing standards') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases ('E2E tests', 'flaky tests', 'Playwright', 'Cypress', 'testing standards') with good coverage, missing only a few common synonyms or tool-version cues.

4 / 5

Distinctiveness Conflict Risk

Names specific tools (Playwright, Cypress) and a clear E2E niche with concrete triggers, giving it a distinct profile with minimal conflict risk against general testing skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (545 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

14

/

16

Passed

Repository
Dicklesworthstone/pi_agent_rust
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.