Cypress
v1.0.0Write reliable E2E and component tests with Cypress avoiding flaky selectors, race conditions, and CI failures.
⭐ 0· 601·4 current·4 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Cypress E2E/component testing) align with what the skill asks for: only 'npx' as a required binary and a set of guidance files describing test structure, commands, CI templates, and setup. Nothing requested is unrelated to running or authoring Cypress tests.
Instruction Scope
SKILL.md and the included documents direct the agent to read project files, create Cypress config/support/fixtures/tests, run common local/CI commands (npm ci, npx cypress run, etc.), and modify repository files — all within the normal scope of setting up/running tests. The instructions do reference reading package.json and filesystem paths inside the project (expected for this task).
Install Mechanism
There is no install spec and no code files to write or download; the skill is instruction-only. It relies on existing developer tooling (npx/npm) which is proportionate for Cypress work.
Credentials
The registry metadata declares no required env vars or credentials (appropriate). The docs do show common optional CI envs such as CYPRESS_RECORD_KEY, GITHUB_TOKEN, and examples that read Cypress.env('API_TOKEN') or use localStorage tokens — these are standard for CI/test runs but are not required by the skill. Users should avoid placing real production secrets in fixtures or test code and should manage CI secrets via the platform's secret store.
Persistence & Privilege
always is false and the skill does not request persistent system-wide privileges or modify other skills. It recommends creating project files under the repository (normal development behavior) and does not attempt to change agent/system configuration outside the project's scope.
Assessment
This skill is a documentation/guide for Cypress and appears coherent and appropriate. Before installing/using it: 1) ensure 'npx' and your node toolchain are available; 2) review any CI templates (they reference CYPRESS_RECORD_KEY, GITHUB_TOKEN) and only add secrets via your CI provider's secret store; 3) inspect generated tests/fixtures to ensure they don't embed real credentials or production data; 4) when following instructions that seed/reset databases (cy.task('db:seed')), confirm the agent has permission to run those commands in your environment. If you want tighter assurance, run the steps in a sandboxed repo or CI environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk979rzf991r9zq1rf1frcw23fh81mjr7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🌲 Clawdis
OSLinux · macOS · Windows
Binsnpx