tessl-labs/cypress-testing
Cypress E2E testing patterns -- selectors, cy.intercept, cy.session, cy.clock, custom commands, test isolation, and anti-patterns
98
99%
Does it follow best practices?
Impact
97%
1.25xAverage score across 4 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that follows best practices. It uses third person voice, lists specific capabilities, includes an explicit 'Use when...' clause with multiple trigger scenarios, and clearly identifies its niche (Cypress-specific E2E testing) to avoid conflicts with other testing frameworks.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'commands, selectors, network stubbing, auth caching, time control, test isolation, and best practices' - these are all concrete, actionable capabilities within the Cypress domain. | 3 / 3 |
Completeness | Clearly answers both what (Cypress E2E testing patterns with specific capabilities listed) AND when (explicit 'Use when...' clause covering building, reviewing, setting up, and debugging scenarios). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Cypress', 'E2E tests', 'browser testing', 'flaky Cypress tests'. These cover common variations of how users would describe their testing needs. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Cypress' as a specific framework identifier. Unlikely to conflict with other testing skills (e.g., Jest, Playwright) due to explicit Cypress mentions throughout. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill document that exemplifies best practices. It's concise yet comprehensive, with executable code examples for every pattern, clear anti-pattern guidance, and a well-structured checklist. The content assumes Claude's competence while providing the specific, non-obvious patterns needed for effective Cypress testing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It assumes Claude knows what Cypress is and jumps straight into actionable configuration and patterns. Every section provides value without explaining basic concepts. | 3 / 3 |
Actionability | All code examples are complete and executable. The skill provides copy-paste ready TypeScript/JavaScript with proper imports, realistic test scenarios, and specific commands. The anti-patterns table with correct alternatives is particularly actionable. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation patterns. The intercept-alias-wait pattern is consistently demonstrated, beforeEach isolation is explained with examples, and the checklist provides a clear verification workflow. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, a summary anti-patterns table, a checklist for quick reference, and links to verifiers for deeper testing scenarios. The structure allows quick scanning while providing depth where needed. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents