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
96%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
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 clearly articulates specific Cypress-related capabilities, provides explicit trigger guidance with a 'Use when' clause and enumerated trigger terms, and is highly distinctive. It uses proper third-person voice and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: writing Cypress E2E/component tests, configuring cy.intercept() and cy.session(), authoring custom commands, and wiring CI artifacts. These are precise, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (writes Cypress tests, configures intercept/session, authors custom commands, wires CI artifacts) and 'when' (explicit 'Use when' clause plus listed trigger terms). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'cypress', 'e2e', 'component test', 'cy.intercept', 'cy.session'. Also includes 'CI test pipelines', 'E2E specs', and 'custom commands' in the body, covering a good range of natural user language. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Cypress testing framework with distinct triggers like 'cy.intercept', 'cy.session', and 'cypress'. Unlikely to conflict with other testing skills (e.g., Jest, Playwright) due to framework-specific terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured Cypress testing skill that provides concrete, executable guidance with a clear workflow and validation checkpoints. The content is concise and respects Claude's intelligence by focusing on Cypress-specific patterns rather than general testing concepts. The only weakness is the progressive disclosure: REFERENCE.md is referenced twice at the bottom for overlapping purposes, and no bundle files exist to verify the referenced paths.
Suggestions
Consolidate the two REFERENCE.md references at the bottom into a single, clearly organized pointer (e.g., 'For CI pipeline examples, `cypress.config.ts` snippets, and advanced optimizations, see [REFERENCE.md](REFERENCE.md)').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Cypress is or how testing frameworks work in general. Every section delivers actionable information without padding. The best practices section specifically notes 'Cypress-specific and non-obvious' which shows intentional filtering. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples for E2E tests and custom commands, concrete bash commands for installation and running, and specific file paths. The login test example is copy-paste ready with realistic selectors and assertions. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced from install through CI, with explicit validation checkpoints: 'npx cypress verify' after install, running a single spec as a smoke check after authoring, and inspecting screenshots/videos on failure. The feedback loop for failures (re-run failing spec, inspect artifacts) is present. | 3 / 3 |
Progressive Disclosure | References to REFERENCE.md and testing-config.md are well-signaled and one level deep, which is good structure. However, REFERENCE.md is referenced twice at the bottom for slightly different purposes (CI pipeline examples and advanced configuration), and no bundle files exist to verify these references resolve. The duplicate REFERENCE.md references at the end feel slightly disorganized. | 2 / 3 |
Total | 11 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- monkilabs/opencastle
- Commit
7a69a05
- 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.