Cypress Docs
Search and extract Cypress information from official documentation (docs.cypress.io, cypress.io); prefer LLM markdown under /llm/* and refuse unverified API or behavior claims.
Install
npx skills add cypress-io/ai-toolkit --skill cypress-docsgit clone --depth 1 https://github.com/cypress-io/ai-toolkit.git /tmp/ai-toolkit
mkdir -p ~/.claude/skills
cp -r /tmp/ai-toolkit/skills/cypress-docs ~/.claude/skills/cypress-docsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Cypress Documentation ## Purpose Enable the agent to retrieve accurate, up-to-date, and verifiable information about the Cypress testing framework by prioritizing official documentation and structured sources. ## When to use Apply this skill whenever the task depends on **finding, reading, or quoting Cypress documentation** rather than general testing intuition: - **Look up facts**: commands, APIs, assertions, lifecycle hooks, configuration options, environment variables, CLI flags, plugins, or TypeScript types as documented by Cypress. - **Confirm behavior**: how something works in a given Cypress version, E2E vs component testing differences, browser support, or networking/cy.intercept semantics. - **Before asserting “Cypress can/cannot…”**: search docs first; do not rely on memory for exact signatures, defaults, or deprecated APIs. - **Extract structured content**: follow the LLM-optimized docs strategy below (`llms.txt`, `/llm/*`) when fetching or summarizing doc pages. - **Ground answers for others**: when explaining Cypress to a user, writing examples, or reviewing code where correctness must match official docs. If the user only needs **writing or fixing tests** without a documentation lookup, prefer `cypress-author`; if they only need **test explanation** without fetching docs, prefer `cypress-explain`. Use **this** skill when official documentation is the source of truth. ## Source Prioritization ### Primary Sources (ALWAYS search first)
Details
- Skill name
cypress-docs- Repository
- cypress-io/ai-toolkit
- Path
skills/cypress-docs/SKILL.md- License
- MIT
- Repo updated
- 23 October 2026
- Listed in
- VoltAgent/awesome-agent-skills
FAQ
What does the Cypress Docs skill do?
Search and extract Cypress information from official documentation (docs.cypress.io, cypress.io); prefer LLM markdown under /llm/* and refuse unverified API or behavior claims.
How do I install the Cypress Docs skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add cypress-io/ai-toolkit --skill cypress-docs. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Cypress Docs popular?
It lives in cypress-io/ai-toolkit, which has 46 GitHub stars and 4 forks, and is included in 1 curated skill list.
Related skills
Cypress Author
46cypress-io/ai-toolkit
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.
Cypress Explain
46cypress-io/ai-toolkit
Explains Cypress tests (E2E and component tests), and answers questions about Cypress use and behavior. Use when the user asks to explain how a test works, explain how Cypress works, review or critique a test without writing code. Apply even when the user does not say 'Cypress' (e.g. 'explain this test'). Prefer the cypress-author skill when the user wants to create, fix, or update tests.
Pc Control
40AnubhavChaturvedi-GitHub/PC-Automation
Hands on the local Mac for any agent - system state (battery, volume, brightness, IP), app launch/quit, open websites and YouTube, media and browser control via keystrokes, screenshots, clipboard, notifications, TTS, and honest mic/speaker hardware tests. Use whenever the user asks to control the computer, change volume or brightness, open an app or site, play or pause media, check battery/IP/running apps, take a screenshot, or test the mic or speakers. Rebuilt from the PC-Automation repo: the agent is the intent brain; this skill is only the hands.
Playwright Browser
51AndyShiu/claude-skill-playwright-browser
Headless, reproducible browser automation with Playwright for any project — screenshots of web pages or local dev servers (desktop/tablet/mobile, full page or one element, single page or every page/menu of an app in one batch), frontend audits (console errors, failed requests, broken images/links, responsive overflow, axe accessibility, LCP/CLS performance), before/after visual comparison, scripted E2E flows (log in, click, fill, page through, assert), and logged-in pages via saved sessions. Use this whenever the user wants to screenshot or visually check a site, find frontend bugs, see how a
Econometrics
41xiaomihu1992/econometrics-skill
Causal inference and applied econometric analysis on tabular data, from uploaded-data diagnostics and cleaning advice to treatment-effect estimation and publication-grade applied research design. Use for policy impact, ATE/ATT/LATE/ITT, OLS, propensity scores, IV/2SLS, DID/event studies, RDD, robustness checks, falsification tests, identification memos, 因果推断, 政策评估, 数据清洗建议, 稳健性检验, and 异质性分析.
Precoil Emt
62David-Precoil/testing-business-ideas-with-claude
Use this skill when the user wants to test a business idea, strategy, or initiative against real-world risk. Triggers include: 'test my idea', 'what are the riskiest assumptions', 'help me validate this', 'run EMT on this', 'extract assumptions', 'assumption mapping', 'what could go wrong with this plan', 'pressure test this', 'validate this plan', 'what could go wrong with this strategy', 'identify hidden risk in this idea', or any request to pressure-test a business decision before committing resources. Runs a guided Extract → Map → Test system based on David J. Bland's Precoil methodology.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.