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

72

Quality

89%

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

86%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 concise, well-structured reference skill that surfaces genuinely non-obvious gotchas and executable commands. The main gap is the absence of example spec code demonstrating the intercept/session patterns advertised in the description.

Suggestions

Add a short code block showing a minimal cy.intercept() + cy.session() spec so the body demonstrates the patterns promised by the description.

Reframe the run/verify/failure-recover guidance as a short numbered checklist with an explicit validation checkpoint before CI upload.

Verify the ../../.opencastle/stack/testing-config.md reference resolves in the target project, since no bundle file is present to confirm it.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — it never explains what Cypress is, and sections like Layout and Gotchas deliver only non-obvious, earned information; every token earns its place.

5 / 5

Actionability

Provides copy-paste bash commands ('npx cypress run --spec ... --headed') and concrete selector-priority rules, but shows no example spec code for the cy.intercept()/cy.session() usage the description promises, leaving a minor gap.

4 / 5

Workflow Clarity

A clear run/verify sequence ('npm install ... run npx cypress verify', 'assert exit 0') with a failure feedback loop ('re-run the failing spec alone and inspect the screenshot/video artifacts') is present, but it is not framed as an explicit numbered checklist with checkpoints.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and a single one-level-deep, clearly-signaled reference ([testing-config.md](../../.opencastle/stack/testing-config.md)); the simple-skill exception applies and no nested references exist.

5 / 5

Total

18

/

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, third-person description that names concrete capabilities and provides explicit 'Use when...' trigger guidance. Trigger-term coverage is good but could add synonyms and file extensions for full comprehensiveness.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Writes Cypress E2E/component tests, configures cy.intercept() and cy.session(), authors custom commands, and wires CI artifacts' — giving comprehensive coverage of capabilities rather than vague language.

5 / 5

Completeness

Explicitly answers both what ('Writes... configures... authors... wires...') and when ('Use when creating E2E specs, component tests, or CI test pipelines') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

'Trigger terms: cypress, e2e, component test, cy.intercept, cy.session' covers the natural terms users say, but is missing common synonyms (e.g. 'end-to-end' spelled out, 'spec') and file extensions, so it falls just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The Cypress-specific niche and API triggers (cy.intercept, cy.session) mark a clear domain with minimal overlap risk against other testing skills.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

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.