Zephyr
End-to-end Cypress skill pack for planning, authoring, debugging, documenting, and operationalizing test automation.
npx -y skills add jovd83/Cypress-skill --skill zephyrAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Legacy Cypress-specific alias for Zephyr case export. Prefer the standalone `test-artifact-export-skill` skill for transforming approved test cases into Zephyr-ready artifacts, and use this only when Cypress-local conventions must be preserved explicitly.
SKILL.md
1.9 KB, as published. Nobody here has run it
Telemetry & Logging
[!IMPORTANT] All usage of this skill must be logged via the Skill Dispatcher to ensure audit logs and wallboard analytics are accurate:
./log-dispatch.cmd --skill <skill_name> --intent <intent> --model <model_name> --reason <reason>(or./log-dispatch.shon Linux)
Transforming Test Cases to Zephyr
Use this skill to convert narrative test cases into Zephyr import artifacts.
Action
Inputs:
- source scenarios in TDD, BDD, or plain-text form,
- the target Zephyr structure if the project already uses one,
- any required suite, folder, or metadata conventions.
Output contract:
- a Zephyr-compatible JSON or CSV payload,
- a field-mapping table when the user wants the transformation planned before generation,
- or a normalized scenario table ready for downstream import tooling.
Mapping rules:
- preserve scenario titles, preconditions, steps, and expected results,
- keep requirement identifiers where Zephyr fields allow them,
- preserve ordering and execution meaning,
- call out any source fields that have no clean Zephyr destination.