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
Test-management mapping skill for Zephyr Scale. Use when Codex needs to apply authoritative Zephyr case IDs back into local Cypress docs, titles, or annotations so the repository can trace automation to imported Zephyr records.
SKILL.md
1.7 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)
Zephyr Mapper
Use this skill after Zephyr has assigned IDs and the local repository needs to reflect them.
Action
Inputs:
- an authoritative mapping from local scenario names or paths to Zephyr IDs,
- the target markdown or automation files,
- the team convention for where IDs belong in docs or test titles.
Output contract:
- updated local docs or code references,
- a summary of which IDs were applied where,
- any ambiguous matches that still need human confirmation.
Guardrails:
- Do not invent IDs.
- Do not overwrite an existing different ID without calling out the conflict.
- Prefer annotations or title conventions already used by the repository.