CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/xray-integration

Imports CI test results into Xray for Jira - authenticates via the `client_id` + `client_secret` → JWT exchange (Cloud) or PAT / Basic (Server), posts to the format-specific `/api/v2/import/execution/*` endpoint (`/junit` for JUnit XML, `/cucumber` for Cucumber JSON, `/nunit` / `/testng` / `/robot` for the others), and maps automated results to existing Xray Test issues via the `xray-junit-extensions` `@XrayTest(key="...")` annotation. Use when the team uses the Xray Jira app to manage Test, Test Set, and Test Execution issue types and CI must keep those execution issues in sync; for the other Jira TCM app use zephyr-integration (Zephyr Scale), for standalone non-Jira TestRail use testrail-integration, and for hosted cross-run flakiness analytics rather than TCM sync use currents-integration.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced skill with strong validation feedback loops and clean progressive disclosure into a single verified reference. The only weakness is conciseness — date-stamped inline narration and some repeated auth prose could be trimmed or relocated to a notes section.

Suggestions

Move the 2026-05-05 WebFetch-failure narration (which appears in both the Overview and Limitations) into a single dated note or 'old patterns' section so time-sensitive commentary does not pad the main flow, per the conciseness guideline.

Consolidate the auth description so it lives once (Step 1) and is only cross-referenced from Step 6 and the Anti-patterns table, reducing repeated prose.

Trim soft qualifiers like '(well-documented across Xray API clients)' and 'the most reliable programmatically-fetchable sources' which add tokens without executable value.

DimensionReasoningScore

Conciseness

Mostly efficient with copy-paste-ready snippets, but inline time-sensitive narration ('At the time of authoring (2026-05-05)... 403 to automated WebFetch' appears twice outside any 'old patterns' section) and repeated auth prose across Overview, Step 1, Step 6, and Anti-patterns could be tightened — matching the 'mostly efficient but includes some unnecessary explanation' anchor rather than the fully lean top anchor.

2 / 3

Actionability

Provides fully executable curl commands with real auth payloads, concrete Java annotations, properties config, and a JSON payload with exact endpoint paths and query params — copy-paste ready, matching the 'fully executable code/commands' anchor.

3 / 3

Workflow Clarity

A clear 7-step sequence with an explicit 'Verify after the POST' validation checkpoint (assert 2xx with a body key, treat 4xx as failure, retry once on 5xx) plus an Anti-patterns table mapping failure modes to fixes — matching the 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor.

3 / 3

Progressive Disclosure

SKILL.md is an overview that pushes the full CI workflow and non-JVM Playwright path into a single one-level-deep reference (references/ci-and-non-jvm.md, verified to exist), clearly signaled inline and in the References section, matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that states concrete actions, explicit 'Use when' triggers, and clear disambiguation against sibling test-management skills. All four dimensions hit the top anchor with no verbosity or vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — authenticate via client_id/client_secret JWT exchange or PAT/Basic, post to format-specific endpoints (/junit, /cucumber, /nunit, /testng, /robot), and map results via @XrayTest(key=...) — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (imports results, authenticates, posts, maps to Test issues) and when ('Use when the team uses the Xray Jira app to manage Test, Test Set, and Test Execution issue types and CI must keep those execution issues in sync'), matching the 'clearly answers both what AND when' anchor.

3 / 3

Trigger Term Quality

Includes natural terms a user would say ('CI test results', 'Xray for Jira', 'Test Execution issues', 'keep those execution issues in sync', 'regression run') with good coverage of common variations, matching the 'good coverage of natural terms' anchor.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (Xray Jira app) and explicitly disambiguates against sibling skills ('for the other Jira TCM app use zephyr-integration', 'for standalone non-Jira TestRail use testrail-integration', 'for hosted cross-run flakiness analytics... use currents-integration'), so it is unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents