CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/cypress-testing

Authors and improves Cypress E2E tests - installs Cypress, configures `cypress.config.ts`, authors `cy.*` command chains, refactors existing specs (`cy.wait(ms)` sleeps into assertions, repeated flows into `cy.session` custom commands), and debugs with the time-travel GUI; Cypress Cloud for parallel runs and recording. Use for both greenfield test authoring and improving hand-written specs already in the codebase. For automated refactor of raw Cypress Studio recordings specifically, use a dedicated codegen-review pass.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

The content is highly actionable with a clear sequenced workflow and a well-structured one-level reference split. The only drag is the Overview section, which quotes Cypress marketing material and concepts Claude already knows.

Suggestions

Replace the Overview blockquotes ('next generation front end testing tool', differentiators) with a one-line purpose statement; keep only the auto-waiting claim since it directly drives the no-`cy.wait` guidance.

Drop the repeated 'Per [cy-overview][cy]' citations inline — keep the link once in References rather than re-attributing each derived claim.

DimensionReasoningScore

Conciseness

The body is mostly lean and code-driven, but the Overview restate Cypress marketing/concepts Claude already knows ('a next generation front end testing tool', the differentiators blockquote) and 'Per [cy-overview][cy]' is cited four times — tightening the Overview would push this to 3.

2 / 3

Actionability

Provides fully executable, copy-paste-ready guidance throughout: install commands, a complete `cypress.config.ts`, a full E2E spec, testing-library setup, a `cy.session` custom command, and CI wiring via the reference.

3 / 3

Workflow Clarity

A clear 8-step numbered sequence from install to Cloud/CI, with a real error-recovery feedback loop (run headless, then replay failures in the time-travel GUI) and a worked example that confirms success ('green 20/20 locally').

3 / 3

Progressive Disclosure

The authoring loop stays in SKILL.md while recording/parallelization and CI wiring are split into a verified one-level-deep reference ([references/ci-and-cloud.md]), clearly signaled in both the How-to-use list and Step 8.

3 / 3

Total

11

/

12

Passed

Description

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.

The description is specific, third-person, and gives explicit 'Use for...' triggers plus a boundary clause — a strong, comprehensive description. No weak dimensions to address.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'installs Cypress, configures `cypress.config.ts`, authors `cy.*` command chains, refactors existing specs (`cy.wait(ms)` sleeps into assertions, repeated flows into `cy.session` custom commands), and debugs with the time-travel GUI' — covering the full lifecycle, not just a domain.

3 / 3

Completeness

Explicitly answers both what (author/improve Cypress tests) and when ('Use for both greenfield test authoring and improving hand-written specs already in the codebase'), plus a negative boundary clause steering Cypress Studio recordings elsewhere.

3 / 3

Trigger Term Quality

Uses natural terms a user would say ('Cypress E2E tests', 'hand-written specs', 'greenfield test authoring', 'Cypress Cloud for parallel runs and recording') alongside the API tokens a Cypress user naturally mentions.

3 / 3

Distinctiveness Conflict Risk

Cypress-specific niche with distinct triggers and an explicit handoff ('For automated refactor of raw Cypress Studio recordings specifically, use a dedicated codegen-review pass'), making conflict with adjacent E2E skills unlikely.

3 / 3

Total

12

/

12

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.

Reviewed

Table of Contents