npx skills add cypress-io/ai-toolkit --skill cypress-author
jgamaraalv/delivery-loop · Archived
cypress-author
Creates, updates, and fixes Cypress tests (E2E and component) — use to write, add, update, or fix failing/flaky tests, even if the user only says "tests". For explaining or reviewing without edits, prefer cypress-explain.
Installation
$
npx skills add jgamaraalv/delivery-loop --skill cypress-author
Stronger alternatives
This repository is archived — consider an actively maintained alternative.
hunt-race-condition
Same source · more installs
jgamaraalv/delivery-loop
Hunting playbook for race-condition / TOCTOU vulnerabilities — concurrent-request abuse, HTTP/2…
3 installs
canvas-design
Same source · more installs
jgamaraalv/delivery-loop
Create beautiful visual art in .png and .pdf documents using design philosophy. Use when the us…
3 installs
css-architecture
Same source
jgamaraalv/delivery-loop
Organize CSS using BEM, SMACSS, and CSS-in-JS patterns. Use when building scalable, maintainabl…
2 installs
vercel-react-view-transitions
Same source
jgamaraalv/delivery-loop
Animate React route/page changes, shared elements, and enter/exit/reorder with the View Transit…
2 installsSimilar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
agent-browser
Same topic
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installs
azure-diagnostics
Same topic
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installs
azure-validate
Same topic
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…
567.7K installs
azure-aigateway
Same topic
microsoft/azure-skills
Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…
566.3K installs
azure-compute
Same topic
microsoft/azure-skills
Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…
510K installs
supabase-postgres-best-practices
Same topic
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …
391.6K installsAlso in this package
Other skills from jgamaraalv/delivery-loop · top by installs.
npx skills add jgamaraalv/delivery-loop
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude Code
Not declared
Cursor
Not declared
Codex
Not declared
GitHub Copilot
Not declared
Windsurf
Not declared
Gemini CLI
Not declared
Cline
Not declared
OpenCode
Not declared
Also listed on
Alternate registries and mirrors of this skill.
Repository health
Stars
3
License
LICENSE
Default branch
main
Open issues
0
Status
Archived
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,581 B -
docs
SUMMARY.md245 B
History
- First seen on skills.sh
- First recorded snapshot · 2 installs
SKILL.md
Cypress Author
Task
You are an expert QA automation engineer with vast experience in Cypress tests. Your task is to collect information from the user to determine the type, scope, and goals of necessary testing tasks so that you can automatically create or update Cypress tests and concepts.
Mandatory flow (do not skip)
You MUST complete the following steps in order. Do not skip structured identification: follow [task.md](./subskills/task.md) before diving into implementation-only reading; you MUST run the full flow below.
- Identify — Read and follow [./subskills/task.md](./subskills/task.md); determine the necessary information (task, spec, test, type, instructions) as specified there.
- Execute — Read and follow [./subskills/author.md](./subskills/author.md) using the determined task data.
- Sign-off — End your response with a clear sign-off (e.g. "Thank you for using Cypress!"). Do not omit this for brevity.
Do not proceed when required data is missing; prompt the user for the missing information first, then re-run the skill if needed.
Conclusion
You MUST end your response with a clear sign-off (e.g. "Thank you for using Cypress!") so it stands out. In a long conversation with multiple turns, one sign-off at the end of the flow is sufficient.