CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cypress

Cypress end-to-end testing best practices for web applications, covering test structure, commands, and reliability patterns.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./cypress/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body delivers concrete, executable Cypress guidance with good code examples and clean section organization. Its main weaknesses are abstract bullet-only sections lacking examples and the total absence of run/verify steps, leaving no validation checkpoints in the testing workflow.

Suggestions

Add a short section on running and verifying tests (e.g. `npx cypress open` for interactive mode, `npx cypress run` for CI) so the test-writing workflow has validation checkpoints.

Add a concrete example to the bullet-only sections — e.g. a `.should()` vs `.then()` comparison and a `beforeEach`/`cy.session` isolation example — to make all guidance executable.

Trim generic bullets Claude already knows (e.g. "Use descriptive test names", "Organize tests by feature or user flow") and merge the duplicated waiting guidance with the anti-patterns section.

DimensionReasoningScore

Conciseness

The body is lean with no background on what Cypress is, but a few generic bullets Claude already knows ("Use descriptive test names", "Chain commands fluently for readability") and slight redundancy between "avoid explicit waits" and the anti-patterns section could be trimmed.

4 / 5

Actionability

Provides executable code for selectors, a cy.session login custom command, and cy.intercept/cy.wait aliasing, but several sections (Test Structure, Commands and Assertions, Test Isolation) are bullet-only with abstract guidance and no examples.

4 / 5

Workflow Clarity

This is a declarative best-practices reference with no sequenced process or validation checkpoints; notably it contains zero guidance on running or verifying tests (e.g. npx cypress open), so the checkpoint gaps of anchor 3 apply rather than anchor 4.

3 / 5

Progressive Disclosure

All content is appropriately inline in one well-sectioned file with no external references needed; however the ~72-line body slightly exceeds the single-file ideal without a quick-start vs. advanced split, fitting anchor 4 rather than 5.

4 / 5

Total

15

/

20

Passed

Description

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

The description clearly identifies the Cypress e2e testing domain with good natural trigger terms, but it completely lacks a 'when to use' clause and describes topic areas rather than concrete actions. Adding explicit trigger guidance and specific capabilities would raise completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing or debugging Cypress tests, or when the user mentions e2e testing, flaky tests, or cypress.json/cypress.config.ts."

Replace topical category names with concrete actions, e.g. "Write reliable Cypress tests, create custom commands, mock network requests with cy.intercept, and fix flaky test patterns."

Include common user phrasings and synonyms such as "e2e", "end-to-end", and "flaky tests" to improve trigger term coverage.

DimensionReasoningScore

Specificity

"covering test structure, commands, and reliability patterns" names the domain and topic areas but frames them as categories rather than concrete actions; no specific capability verbs like 'write', 'mock', or 'debug' are listed.

3 / 5

Completeness

The 'what' is clear ("Cypress end-to-end testing best practices for web applications, covering test structure, commands, and reliability patterns") but the 'when' is entirely absent — no 'Use when...' clause or equivalent trigger guidance, which caps this at 3.

3 / 5

Trigger Term Quality

Contains strong natural terms users would say — "Cypress", "end-to-end testing", "web applications", "test structure" — but misses common variations such as "e2e" and "flaky tests".

4 / 5

Distinctiveness Conflict Risk

"Cypress" names a specific tool creating a clear niche, but "end-to-end testing best practices for web applications" leaves minor overlap risk with generic e2e or Playwright testing skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

Mindrally/skills

Path

cypress/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.