Skills cypress-author

📦

cypress-author

Name: cypress-author
Author: cypress-io

v1.0.1 Content revision r1 Safe 🌐 Network access📁 Filesystem access⚙️ External commands

Create Reliable Cypress Tests

Writing stable Cypress tests requires project context, framework knowledge, and careful command usage. This skill creates, updates, and repairs tests using established project conventions.

Supports: Claude Codex Code(CC)

📊 76 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "cypress-author" from https://skillstore.io/skills/cypress-io-cypress-author.md and its manifest at https://skillstore.io/api/skills/cypress-io-cypress-author/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/cypress-io-cypress-author.md Signed manifest GET /api/skills/cypress-io-cypress-author/manifest Signed lockfile GET /api/skills/cypress-io-cypress-author/lockfile

Test it

Using "cypress-author". Create an E2E test for invalid login attempts in the existing login specification.

Expected outcome:

Updated the existing login specification instead of creating a duplicate file.
Added an isolated invalid-login scenario with explicit validation assertions.
Reused the project's stable selectors and reset application state before the test.

Using "cypress-author". Fix a test that waits five seconds before checking search results.

Expected outcome:

Replaced the fixed delay with a network alias and a retryable result assertion. The test now waits for observable application behavior.

Using "cypress-author". Add component coverage for a React button with loading and disabled states.

Expected outcome:

Added focused component scenarios for loading and disabled states using the project's mount helper and accessible element queries.

Security Audit

Safe

v2 • 8/18/2026 Open versioned report

All 11 static findings are false positives caused by internal Markdown links, inline Cypress syntax, and legitimate testing guidance. No prompt injection, malicious intent, credential exfiltration, or unsafe path access was found.

Files scanned

261

Lines analyzed

Review items

False positives ignored

Risk Factors

🌐 Network access (1)

references/author/author-rules.md:41

📁 Filesystem access (2)

references/author/author-rules.md:7 subskills/author.md:7

⚙️ External commands (1)

SKILL.md:13

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/cypress-io-cypress-author/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/cypress-io-cypress-author/security.svg)](https://skillstore.io/skills/cypress-io-cypress-author?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/cypress-io-cypress-author?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cypress-io-cypress-author/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/cypress-io-cypress-author.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

cypress-io. (2026). cypress-author security audit report (audit version 2) [Author version 1.0.1]. Skillstore. https://skillstore.io/skills/cypress-io-cypress-author/audits/2

BibTeX citation

@techreport{cypress-io-cypress-io-cypress-author-2026,
  author = {cypress-io},
  title = {cypress-author security audit report (audit version 2)},
  institution = {Skillstore},
  year = {2026},
  number = {2},
  url = {https://skillstore.io/skills/cypress-io-cypress-author/audits/2},
  note = {Author version 1.0.1}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "cypress-author security audit report (audit version 2)"
version: "1.0.1"
type: report
authors:
  - name: "cypress-io"
date-released: "2026-08-18"
url: "https://skillstore.io/skills/cypress-io-cypress-author/audits/2"
identifiers:
  - type: other
    value: "skillstore:cypress-io-cypress-author:audit:2"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Add Journey Coverage

Create end-to-end coverage for a new user journey while reusing existing setup and selector conventions.

Repair Unstable Tests

Replace arbitrary waits and fragile selectors with retryable assertions, aliases, and controlled network behavior.

Test UI Components

Create isolated component tests for React, Vue, or Angular behavior using the project's mounting patterns.

Try These Prompts

Create a Basic Test

Create a Cypress test for [behavior] in [spec path]. Use the existing project conventions and tell me whether it is E2E or component testing.

Extend Existing Coverage

Update [spec path] to cover [new behavior]. Reuse existing helpers, preserve test independence, and add explicit assertions for [expected outcome].

Fix a Flaky Test

Fix the flaky test at [spec and test name]. Investigate waits, selectors, shared state, asynchronous logic, and network timing before editing.

Refactor a Test Suite

Refactor Cypress tests in [scope]. Consolidate repeated setup, preserve isolated execution, align selectors with project priorities, and verify configured quality checks.

Best Practices

Provide the target specification, testing type, expected behavior, and relevant failure details.
Keep tests independent and prepare application state before each scenario.
Use stable selectors, retryable assertions, and network aliases instead of fixed delays.

Avoid

Do not request Cypress changes without identifying the affected behavior or specification.
Do not depend on state created by another test or a previous test run.
Do not store Cypress command results in variables or mix command chains with unmanaged Promises.