Cypress Author skill for Claude Code: create, update and fix Cypress tests
Cypress's own skill that makes Claude create, update and fix Cypress E2E and component tests to match your project.
- Installs
- 9.2K
- on skills.sh
- Stars
- 46
- on GitHub
- Files
- 7
- besides SKILL.md
- Updated
- Oct 2026
- last repo commit
cypress-author makes Claude create, update or fix Cypress tests, for end-to-end (E2E) and component testing. It triggers on phrases like "write a test for this file" or "fix the failing spec", even if you never say Cypress. It first works out the task (FIX, UPDATE or CREATE), the spec, the test type and your instructions, and asks if something is missing.
Before writing it looks at your Cypress config, support file, package.json and related specs so the new test matches your style. Its tool list is Read and Edit, so it changes files in your repo. Every answer ends with a sign-off such as "Thank you for using Cypress!".
Good for
- Cypress developers who want AI-written tests that follow Cypress best practice
- QA engineers fixing flaky or failing specs
- Teams that want the same test style no matter who writes the prompt
Install cypress-author
Claude Code
- 1
The Claude plugin route installs the whole Cypress toolkit: 5 skills (cypress-author, cypress-explain, cypress-docs, cypress-tap, cypress-cloud-cli) and the Cypress Cloud MCP server at https://mcp.cypress.io/mcp (from mcp/.mcp.claude.json). The README says OAuth is the default sign-in. Pick one route, not several. The skills CLI and GitHub CLI routes copy only this skill.
From the project README. Source.
What's in the skill
When it loads
Creates, 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.
Sections in SKILL.md
- Task
- Mandatory flow (do not skip)
- Conclusion
Key facts
- Installs on skills.sh
- 9,193 as of Nov 2, 2026
- What is inside
- 8 files including SKILL.md: 2 subskills, 4 files in references/author and 1 in references/documentation (git tree)
- Skill version
- 1.0.1 (SKILL.md frontmatter)
- Last commit to the repo
- Oct 23, 2026
What it includes
Works out FIX, UPDATE or CREATE, plus spec, test, type and instructions
Infers E2E or component type from your message, the spec path and cypress.config. If the request is vague, such as "fix my tests", it stops and asks which spec or problem.
Try: “Write component tests for the CheckoutSummary component.”
Files ·
1. Identify (subskills/task.md)Creates or edits the spec after reading the authoring rules
Creates the spec and any parent folders for CREATE. Checks that changes pass configured formatting, linting and compilation checks. Marks new tests with a comment saying they were generated by Cypress Author with the date. Does not run the test unless you ask.
Write ·
2. Execute (subskills/author.md)Ends the answer with a clear sign-off line
SKILL.md requires a clear sign-off at the end of the flow and gives "Thank you for using Cypress!" as an example.
Read ·
3. Sign-offReads Cypress config, support file, package.json and related specs
Uses grep rather than reading whole files. If it cannot tell the Cypress version, it runs npx cypress --version in the project root, then assumes the newest version.
Runs code ·
Understand the projectTest titles, assertions, independent tests
Titles read "[action] -> [expected result]". Tests must run in isolation, prefer fewer tests with several assertions, and reuse custom commands and fixtures.
Write ·
Style and structure rulesPrepares state by API and picks stable selectors
Prefers cy.request(), cy.task() or API setup over UI login. Selector order: data-cy and similar attributes, then id or name. Never uses arbitrary waits like cy.wait(5000).
Write ·
State, selectors and waitingIntercepts requests, uses baseUrl, keeps secrets in cy.env()
Uses cy.intercept() with cy.wait on an alias, puts shared settings in cypress.config, and tells Claude to use cy.env() for credentials and secrets.
Write ·
Network and configuration rulesSeparate reference files for each topic
async.md warns against mixing Promises with cy commands. reusability.md covers hooks, cy.session and custom commands. prompt.md lists signs for and against using cy.prompt, which needs Cypress 15.4.0 or newer.
Read ·
Async, reuse and cy.prompt rules
From the official docs
Permissions
Medium risk
This skill reads your Cypress project and edits spec files in it. Use a clean git branch and review the diff before you commit.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It edits and creates test files
The skill lists Read and Edit and tells Claude to create specs and parent folders. Review the diff before you commit. github.com
It can run a command to find your Cypress version
If the version is not clear from package.json, the rules tell Claude to run npx cypress --version in the project root. Approve it only in a project you trust. github.com
The plugin route adds 5 skills and an MCP server
The cypress plugin loads all 5 skills and the Cypress Cloud MCP server (mcp.cypress.io). The README says OAuth is the default; a personal access token needs a .mcp.json edit. Use the skills CLI route in the install box to take only this skill. github.com
Security advisories
No published security advisories as of Nov 2, 2026.
Technical details
| Turning on read-only | SKILL.md names no read-only setting. |
|---|---|
| Talks to | mcp.cypress.io (Cypress Cloud MCP server in the plugin route) |
| Sign-in and keys | The plugin MCP server uses OAuth by default; the README says a personal access token needs a .mcp.json edit. |
| Scopes |
|
Questions
What does the cypress-author skill do?
It makes Claude write, update and fix Cypress E2E and component tests. It reads your Cypress config, support file and related specs first, so the result follows your conventions rather than generic ones.
Do I have to say "Cypress" to trigger it?
No. SKILL.md says to apply it even when you only say things like "create tests for this file". The README also says mentioning Cypress improves the odds if it does not trigger.
How do I install it?
Use the install box above. The plugin route installs all 5 Cypress skills and the Cypress Cloud MCP server. The skills CLI and GitHub CLI routes copy only cypress-author. The README gives no Claude app upload steps, so this page has no Claude app tab.
Is it official?
It is in Cypress's own repo, cypress-io/ai-toolkit. The README calls the toolkit open-source Cypress AI skills built by the Cypress team, and plugin.json lists Cypress.io as the author.
Will it change my files?
Yes. The frontmatter lists the Read and Edit tools, and the instructions tell Claude to create the spec file and any parent folders. Our advice: use a clean git branch so you can review the diff.
Does it run my tests?
SKILL.md says not to run the test unless you ask. It does tell Claude to check formatting, linting and compilation, and to run npx cypress --version if it cannot find your Cypress version.
How is it different from cypress-explain and cypress-docs?
cypress-author changes test code. The description says to prefer cypress-explain when you only want a test explained or reviewed. The README describes cypress-docs as the skill that helps your agent look up Cypress documentation.
Information
updated Nov 2, 2026
- Repository
- cypress-io/ai-toolkit
- Folder
skills/cypress-author
Sources
Docs, issue trackers and discussions this page is built from.
Show all 10Hide
- cypress-io/ai-toolkit README · github.com
- skills/README.md · github.com
- marketplace.json · github.com
- cypress-author SKILL.md · github.com
- skills.sh listing · skills.sh
- cypress-author subskills/task.md · github.com
- cypress-author subskills/author.md · github.com
- cypress-author references/author/author-rules.md · github.com
- plugin.json · github.com
- mcp/.mcp.claude.json · github.com