Xray
Legacy Cypress-specific alias for Xray case export. Prefer the standalone `test-artifact-export-skill` skill for transforming approved test cases into Xray-ready artifacts, and use this only when Cypress-local conventions must be preserved explicitly.From its SKILL.md
npx -y skills add jovd83/Cypress-skill --skill xrayAssembled 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.
SKILL.md
1.9 KB, 236 tokens by cl100k_base, 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 Xray
Use this skill to convert narrative test cases into Xray import artifacts.
Action
Inputs:
- source scenarios in TDD, BDD, or plain-text form,
- the target Xray structure if the project already uses one,
- any required Jira or Xray metadata conventions.
Output contract:
- an Xray-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, steps, expected outcomes, and requirement references,
- keep Jira or issue identifiers intact where possible,
- preserve ordered steps and execution meaning,
- call out any source fields that have no clean Xray destination.
What ships with it: 1 file
296 B alongside SKILL.md
agents/
- openai.yaml296 B