CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/zephyr-integration

Syncs automated test results to Zephyr Scale for Jira (formerly TM4J / SmartBear / Adaptavist): picks the product variant (Scale Cloud / Squad / Enterprise), authenticates with a long-lived API token as a Bearer header, opens a Test Cycle per build, posts executions via `POST /testexecutions` (or bulk JUnit via `/automations/executions/junit`), and maps test methods to Zephyr Test Cases via `@TestCaseKey`-style annotations. Use when the team's Jira test management is Zephyr Scale; for the Xray Jira app use xray-integration, for standalone TestRail use testrail-integration, and for over-time flakiness analytics rather than TCM sync use currents-integration.

74

Quality

93%

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.

An actionable, well-sequenced body with executable code and a clean single-level reference structure. The main weakness is conciseness: the dated auth/region-gated narrative recurs in three places and a couple of sections restate already-listed references.

Suggestions

Consolidate the '2026-05-05 / auth/region-gated / WebFetch limits' note into a single short Limitations entry instead of repeating it across Overview, Limitations, and References to save tokens.

In 'Operating in CI', reference api-wiring.md once without re-listing its contents, since How to use and References already enumerate them.

Move the time-sensitive fetch-failure date out of the main narrative or frame it once under Limitations so it does not penalize the body's conciseness.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes Claude's competence (no 'what is Jira/Zephyr' preamble), but the time-sensitive auth/region-gated narrative ('2026-05-05 ... behind WebFetch limits') is repeated across the Overview, Limitations, and References sections, and the CI section restates the references already listed in How to use.

2 / 3

Actionability

Provides fully executable, copy-paste-ready code (open_cycle, post_execution with concrete endpoint shapes and field names), a curl healthcheck, exact status-name enums, a 60 req/min rate limit, and a CI YAML block — concrete rather than abstract.

3 / 3

Workflow Clarity

A clear numbered 'How to use' sequence plus a worked example and CI ordering ('if: always() so failed runs still update Zephyr') with validation awareness (query /statuses at init, raise_for_status, bounded concurrency under the rate limit).

3 / 3

Progressive Disclosure

SKILL.md is an overview that consistently signals a single one-level-deep reference (references/api-wiring.md, verified to exist and contain the batch helper, CI workflow, and JUnit import path), with content appropriately split between the overview and the deep file.

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 specific, well-triggered description that clearly states both capabilities and use-conditions and actively distinguishes the skill from its siblings. Third-person voice is used throughout, with no fluff or over-claims.

DimensionReasoningScore

Specificity

Names many concrete actions — 'picks the product variant', 'authenticates with a long-lived API token as a Bearer header', 'opens a Test Cycle per build', 'posts executions via POST /testexecutions', 'maps test methods ... via @TestCaseKey-style annotations' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (the sync actions) and when via the 'Use when the team's Jira test management is Zephyr Scale' clause, with sibling-routing guidance for Xray/TestRail/currents.

3 / 3

Trigger Term Quality

Includes natural terms a user would say ('automated test results', 'Zephyr Scale', 'Jira', 'Test Cycle') plus the distinguishing product name and the 'Use when the team's Jira test management is Zephyr Scale' framing.

3 / 3

Distinctiveness Conflict Risk

Has a clear niche (Zephyr Scale TCM sync) and explicitly routes away from the sibling skills ('for the Xray Jira app use xray-integration, for standalone TestRail use testrail-integration, ... use currents-integration'), minimizing wrong-skill triggering.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents