Name: zephyr-squad-legacy
Rating: 55.2 (1 reviews)
Author: membranedev

zephyr-squad-legacy

Zephyr Squad (Legacy) integration. Manage Projects. Use when the user wants to interact with Zephyr Squad (Legacy) data.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/zephyr-squad-legacy/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

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

The content is highly actionable with concrete, executable CLI commands and a clear connection workflow, but loses points to marketing prose and a lack of validation guidance for the destructive delete actions it exposes. A verification checkpoint before destructive runs and trimming promotional language would raise the score.

Suggestions

Add an explicit validation/confirmation checkpoint before running destructive actions (delete-execution, delete-test-cycle, delete-test-step, delete-folder) — e.g. confirm the target ID or list-then-delete.

Remove marketing fluff such as "so you can focus on the integration logic rather than auth plumbing" and rewrite the garbled agent-types sentence into a concise note.

Consider moving the 20-row popular actions table into a references file (e.g. ACTIONS.md) and keeping only a few representative examples inline, to tighten the overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples, but includes unnecessary marketing prose ("so you can focus on the integration logic rather than auth plumbing", "burn less tokens and make communication more secure") and a poorly worded agent-types line that could be trimmed.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, connection get --wait, action list, action run, request) with flags and JSON examples, plus a concrete 20-row actions table covering the common cases.	5 / 5
Workflow Clarity	The connect-to-run sequence is clear with explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling, but the available actions include destructive operations (delete-execution, delete-test-cycle, delete-test-step, delete-folder) whose run workflow has no validation checkpoint, capping this at 3.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections with no nested references and no bundle files needed, though the 20-row actions table inlined in SKILL.md is borderline content that could live in a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

57%Weight 40%Scale 1-5

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

The description has an explicit trigger clause and a clearly named, distinctive product, but its capability statement is thin and generic. Expanding "Manage Projects" into the concrete test-cycle/execution/step actions would lift specificity and trigger-term quality.

Suggestions

Replace the generic "Manage Projects" with concrete capabilities, e.g. "Manage test cycles, executions, test steps, and folders in Zephyr Squad (Legacy)."

Add natural trigger terms users actually say, such as "test execution", "test cycle", "test steps", or "Jira test management".

Tighten the "when" clause to name the specific data (e.g. "Use when the user wants to manage Zephyr Squad test cycles, executions, or test steps in Jira.").

Dimension	Reasoning	Score
Specificity	The description names the domain but offers only one minimal/generic action ("Manage Projects") while "interact with Zephyr Squad (Legacy) data" is vague; the body reveals ~20 concrete actions (test cycles, executions, steps) that are not surfaced here.	2 / 5
Completeness	Both a "what" ("Zephyr Squad (Legacy) integration. Manage Projects.") and an explicit "when" ("Use when the user wants to interact with Zephyr Squad (Legacy) data") are present and in third person, though the "what" is thin and the "when" could name specific data types.	4 / 5
Trigger Term Quality	It includes the relevant product keyword "Zephyr Squad (Legacy)" but misses the natural phrases users would say for test management ("test cycles", "test execution", "test steps", "Jira tests"), and "interact with...data" is generic.	3 / 5
Distinctiveness Conflict Risk	The named product "Zephyr Squad (Legacy)" gives it a clear niche with minimal conflict risk, but the generic "Manage Projects" clause and potential confusion with the related Zephyr Scale family leave minor overlap risk.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/zephyr-squad-legacy/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.