Skip to main content
ZICQ

Skills ZICQ category:Documents cypress-docs

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.

6114 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

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.

When to use it

Apply this skill whenever the task depends on **finding, reading, or quoting Cypress documentation** rather than general testing intuition:

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Cypress Documentation; Purpose; When to use; Source Prioritization; Primary Sources (ALWAYS search first); 🤖 LLM-Optimized Docs Strategy.

File analysis

File analysis: besides SKILL.md, the body references references/error-messages/, references/error-messages. Those resources load on demand.

Cypress DocumentationPurposeWhen to useSource PrioritizationPrimary Sources (ALWAYS search first)🤖 LLM-Optimized Docs StrategyCritical RulesNever Assume Missing FeaturesAnti-Hallucination GuardSearch Strategy1. Classify the Query2. Search Flow

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
cypress-docs
description
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.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 2
  • references/error-messages/
  • references/error-messages

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "cypress-docs" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-c9d35ab0a38912b7-Cypress-Docs.html
Save it as .cursor/skills/cypress-docs/SKILL.md or .claude/skills/cypress-docs/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/cypress-io/ai-toolkit instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/cypress-io/ai-toolkit' --list

npx skills add 'https://github.com/cypress-io/ai-toolkit' --skill 'cypress-docs'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout

name: cypress-docs description: 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. model: inherit background: false metadata: version: 1.0.0

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)

  • https://docs.cypress.io
  • https://www.cypress.io

🤖 LLM-Optimized Docs Strategy

When accessing docs.cypress.io:

  1. Fetch /llms.txt

  2. Parse it to discover:

    • LLM-friendly documentation paths
    • Structured content endpoints
  3. Prefer content under /llm/*. Every path on the site has an optimized version hosted under /llm - for example, https://docs.cypress.io/app/faq is available at https://docs.cypress.io/llm/markdown/app/faq.md.

  4. Why:

    • Markdown / JSON format
    • Cleaner structure
    • Less noise than HTML
  5. Fallback:

    • If /llm/* is incomplete, use standard docs pages

Critical Rules

Never Assume Missing Features

  • NEVER assume Cypress does not support a feature
  • ALWAYS search before concluding
  • Retry with alternate terminology if needed

Anti-Hallucination Guard

If documentation cannot verify a claim:

  • Say: "I could not verify this in Cypress docs"
  • Provide closest supported alternative (if available)
  • DO NOT invent APIs or behavior

Search Strategy

1. Classify the Query

| Query Type | Search Location | |------------------|------------------------------| | How do I... | /guides/, /core-concepts/ | | What is... | /core-concepts/ | | API / Commands | /api/commands/ | | Assertions | /api/assertions/ | | Config issues | /configuration/ | | CI/CD | /guides/ci-cd/ | | Errors | /references/error-messages/ |

2. Search Flow

  1. /llm/* (via /llms.txt)
  2. Standard docs pages
  3. /changelog/
  4. cypress.io (blog, updates)

3. Error-Aware Routing

If the query includes:

  • Error messages
  • Stack traces

Then:

  1. Search /references/error-messages
  2. Expand to guides and API docs

Structured Extraction Rules

Commands

  • Syntax
  • Required arguments
  • Optional options
  • Return behavior
  • Example usage

Concepts

  • Definition
  • Key rules
  • Common pitfalls
  • Example

Configuration

  • Option name
  • Type
  • Default value
  • Example

Version Awareness

  • Detect Cypress version if provided
  • If NOT provided: assume latest stable version
  • If behavior differs by version:
    • Explicitly call it out

Response Style Guidelines

  • Prefer official examples
  • Provide working code snippets
  • Keep answers concise but complete
  • Avoid speculation

Caching Strategy (Optional)

Cache frequently used topics:

  • cy.visit
  • cy.get
  • cy.intercept
  • authentication patterns
  • common configuration

Confidence Annotation

Internally assess confidence:

  • High → Direct match in official docs
  • Medium → Inferred from multiple sources
  • Low → Unclear or edge case

If LOW:

  • Clearly communicate uncertainty

LLM Path Auto-Discovery

  • Always parse /llms.txt
  • Dynamically adapt to:
    • New /llm/* paths
    • Updated documentation formats

Safety Rules

  • NEVER invent Cypress APIs
  • NEVER guess syntax
  • ALWAYS verify behavior
  • Prefer "unknown" over incorrect

Example Behavior

User: "How do I mock API requests in Cypress?"

Agent should:

  1. Classify → API / network
  2. Search /llm/markdown/api/ and /llm/markdown/guides/
  3. Identify cy.intercept
  4. Extract structured details
  5. Return:
    • Explanation
    • Syntax
    • Example
    • Notes

Summary

This skill ensures:

  • Accurate answers from official sources
  • Reduced hallucination
  • Structured, high-quality outputs
  • Adaptability to evolving Cypress docs

Related skills

Documents

Ontology

Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, …

Documents

Nano Pdf

Edit PDFs with natural-language instructions using the nano-pdf CLI.

Documents

Word / DOCX

Create, inspect, and edit Microsoft Word documents and DOCX files with reliable styles, numbering, tracked changes, tables, sections, and co…

Documents

Api Gateway

Call third-party APIs through the Maton gateway, which injects the credential for an app the user has already connected. Use this skill when…