Cypress docs lookup for agents
Answer Cypress questions from official docs only — llms.txt-first lookup with an anti-hallucination guard that refuses unverified claims
- What
- Answer Cypress questions from official docs only — llms.txt-first lookup with an anti-hallucination guard that refuses unverified claims
- Cost
- Free
- Needs
- live access to docs.cypress.io at run time; nothing else — documentation lookup only, it writes or fixes no tests
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @cypress-io's official docs-search skill for agents: whenever a task depends on finding, reading or quoting Cypress documentation — commands, APIs, assertions, lifecycle hooks, config options, env vars, CLI flags, plugins, TypeScript types — the agent searches docs.cypress.io first using the LLM-optimized docs strategy (fetch `/llms.txt`, prefer the markdown endpoints under `/llm/*`, fall back to standard pages, then changelog and blog), classifies the query type (how-do vs what-is vs API vs config vs CI/CD vs errors), routes errors to the error-message reference, and extracts structured content (syntax, required vs optional arguments, return behavior, version awareness). Its hard rule is anti-hallucination: never assume a feature is missing, never invent APIs or syntax, and when a claim cannot be verified, say "I could not verify this in Cypress docs" with the closest supported alternative instead of guessing. Honest caveats: documentation lookup only — it does not write or fix tests (the skill points to sibling skills `cypress-author` and `cypress-explain` for those, which are not bundled here); needs live access to docs.cypress.io at run time; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: live access to docs.cypress.io at run time; nothing else — documentation lookup only, it writes or fixes no tests Install "Cypress docs lookup for agents" for me. It teaches the agent @cypress-io's official docs-search workflow: query classification (how-do / what-is / API / config / CI-CD / errors), the LLM-optimized docs strategy (fetch /llms.txt, prefer /llm/* markdown endpoints, fall back to standard pages), structured extraction (syntax, arguments, return behavior, version awareness), and a strict anti-hallucination guard that refuses unverified claims. MIT-licensed. Repository: https://github.com/cypress-io/ai-toolkit/blob/main/skills/cypress-docs/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "cypress-docs". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — ask it any Cypress question; fetch the sibling cypress-author / cypress-explain skills separately if you want test authoring or explanation). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.