Testrail
Legacy Cypress-specific alias for TestRail case export. Prefer the standalone `test-artifact-export-skill` skill for transforming approved test cases into TestRail-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 testrailAssembled 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, 231 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 TestRail
Use this skill to convert narrative test cases into TestRail import artifacts.
Action
Inputs:
- source scenarios in TDD, BDD, or plain-text form,
- the target TestRail structure if the project already uses one,
- any required suite, section, or metadata conventions.
Output contract:
- a TestRail-compatible XML or CSV payload,
- a structured mapping table when import planning should happen before generation,
- or a normalized scenario table ready for import tooling.
Mapping rules:
- map titles, preconditions, steps, and expected results consistently,
- keep requirement identifiers where TestRail fields allow them,
- preserve ordering and execution intent,
- call out any source fields that have no clean TestRail destination.
What ships with it: 1 file
312 B alongside SKILL.md
agents/
- openai.yaml312 B