Cypress Author
Skill Verified ActiveCreates, updates, and fixes Cypress tests (E2E/end-to-end and component tests). Use when the user asks to create tests, add tests, write tests, update tests, test this file/component, new spec, or fix a failing or flaky test. Apply even when the user does not say 'Cypress' (e.g. 'create tests for this file'). Prefer cypress-explain when the user only wants to explain or review tests without changing code.
To empower AI tools with Cypress-specific knowledge, enabling them to consistently generate reliable, well-formed, and maintainable Cypress tests.
Features
- Creates, updates, and fixes Cypress tests (E2E and component)
- Provides Cypress-specific context and best practices to AI tools
- Follows a structured, mandatory flow for test authoring tasks
- Adapts to user requests even when 'Cypress' is not explicitly mentioned
- Leverages sub-skills for task identification and code authoring
Use Cases
- When a user asks to create new Cypress tests for a file or component.
- When a user requests to update or fix existing failing or flaky Cypress tests.
- When a user specifies adding new specs or test coverage.
- When a user mentions Cypress commands (e.g., 'cy.*') but not the tool name explicitly.
Non-Goals
- Creating tests for projects not using Cypress.
- Running or executing existing tests without authoring changes.
- Providing explanations or reviews of tests without making edits.
- Using alternative testing tools or migrating from them.
Practical Utility
- info:Usage examplesWhile the skill's purpose is clear and its instructions detailed, explicit end-to-end usage examples of prompts are not provided directly in the SKILL.md or README.
Installation
First, add the marketplace
/plugin marketplace add cypress-io/ai-toolkit/plugin install ai-toolkit@cypressQuality Score
VerifiedTrust Signals
Similar Extensions
Cypress
89Cypress end-to-end and component testing patterns for web apps: reliable selectors, stable waits, network stubbing, auth handling, CI parallelization, and flake reduction
Vue Testing Best Practices
100Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.
Playwright Best Practices
100Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
Telegram Crabbox E2e Proof
100Use when reviewing, reproducing, or proving OpenClaw Telegram behavior with a real Telegram user on Crabbox, including PR review workflows that need an agent-controlled Telegram Desktop recording, TDLib user-driver commands, Convex-leased credentials, WebVNC observation, and motion-trimmed artifacts.
E2E Testing Patterns
98Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
E2e Test
79Run Cypress E2E tests, analyze failures including screenshots, and stress test for flakiness