CtrlK
BlogDocsLog inGet started
Tessl Logo

cypress-testing

Writes Cypress E2E/component tests, configures `cy.intercept()` and `cy.session()`, authors custom commands, and wires CI artifacts. Use when creating E2E specs, component tests, or CI test pipelines. Trigger terms: cypress, e2e, component test, cy.intercept, cy.session

77

Quality

96%

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.

An exemplary lean skill body: dense with non-obvious, project-specific gotchas and executable commands, organized into clean sections with a failure-recovery loop. No verbosity, no inferred-knowledge padding, and nothing that belongs in a separate reference file.

DimensionReasoningScore

Conciseness

Every line carries project-specific knowledge Claude cannot infer (session cache-key pitfalls, alias collisions, selector priority, corrupted binary cache), with zero padding or explanation of concepts Claude already knows — every token earns its place.

5 / 5

Actionability

Commands are copy-paste ready with real flags ('npx cypress run --spec "cypress/e2e/auth/login.cy.ts" --headed', 'npx cypress verify') and the guidance includes specific executable practices (fixture payloads over seeding, upload artifacts only on failure).

5 / 5

Workflow Clarity

For a simple single-purpose skill under 50 lines, validation checkpoints are present ('run npx cypress verify' after install, 'assert exit 0' in CI) and an explicit error-recovery loop exists ('On failure, re-run the failing spec alone and inspect the screenshot/video artifacts'), so the single task is unambiguous.

5 / 5

Progressive Disclosure

The body is a short, well-organized overview with clear sections (Layout, Gotchas, Commands) and no bundle files to disclose; per the rubric's simple-skill guideline, well-organized sections alone merit 5 here.

5 / 5

Total

20

/

20

Passed

Description

92%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 description: concrete, third-person action list plus an explicit 'Use when' clause and enumerated trigger terms. The only gap is trigger-term breadth — a few natural synonyms like 'end-to-end' or 'spec' are absent.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('Writes Cypress E2E/component tests, configures `cy.intercept()` and `cy.session()`, authors custom commands, and wires CI artifacts') at API-level specificity in third person, matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

It explicitly answers both what ('Writes Cypress E2E/component tests, configures...') and when ('Use when creating E2E specs, component tests, or CI test pipelines. Trigger terms: ...') with concrete trigger phrases, matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

Trigger terms 'cypress, e2e, component test, cy.intercept, cy.session' are natural phrases users would say, but common synonyms and variations (e.g., 'end-to-end', 'spec', '.cy.ts') are missing, which fits the 4 anchor (good coverage, a few natural terms missing) rather than the comprehensive-synonym 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The Cypress niche is unambiguous, reinforced by named APIs (cy.intercept, cy.session) and Cypress-specific triggers, giving minimal conflict risk with other testing skills.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
monkilabs/opencastle
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.