Name: zephyr-scale
Rating: 60 (1 reviews)
Author: membranedev

zephyr-scale

Zephyr Scale integration. Manage Requirements, Projects, Users, Roles. Use when the user wants to interact with Zephyr Scale data.

Quality

70%

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-scale/SKILL.md

Quality

Content

78%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 body is highly actionable with concrete CLI commands and a well-validated connection workflow, but it is a monolithic single file that inlines reference content better suited to separate files and has minor workflow-labeling inconsistencies.

Suggestions

Move the Popular actions table and proxy flag reference into a separate references file (e.g., ACTIONS.md) and link to it from the overview to improve progressive disclosure.

Fix the workflow labeling: define 'Step 1'/'Step 2' explicitly or renumber the '1b. Wait for the connection' subsection to match a '1a'.

Trim the opening product-definition paragraph or fold it into a one-line context note to reduce over-explanation Claude largely does not need.

Dimension	Reasoning	Score
Conciseness	Mostly lean executable commands, but the two-sentence product intro and the ~20-row Popular actions table are minor padding that could be trimmed or externalized.	4 / 5
Actionability	Copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request proxy) with flags documented, covering the common cases.	5 / 5
Workflow Clarity	The connection flow includes state-checking validation and error-recovery feedback, but references an undefined 'Step 2' and uses inconsistent '1b' labeling without a matching '1a'.	4 / 5
Progressive Disclosure	A single file with no bundle files or external references inlines reference material (the Popular actions table and proxy options) that would be better placed in separate reference files.	3 / 5
	Total	16 / 20 Passed

Description

62%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 names a distinct product and provides both a 'what' and a 'when' clause, but relies on the generic verb 'Manage' and omits core Zephyr Scale test-management terminology.

Suggestions

Replace the generic 'Manage' with concrete verbs (e.g., 'Create, list, and update test cases, executions, and cycles') to lift specificity.

Add core Zephyr Scale trigger terms like 'test cases', 'test executions', 'test cycles', and 'test plans' to improve trigger-term coverage.

Sharpen the 'Use when...' clause with concrete scenarios (e.g., 'Use when the user wants to query or create Zephyr Scale test cases, cycles, or executions').

Dimension	Reasoning	Score
Specificity	Names the Zephyr Scale domain and four concrete entities ('Requirements, Projects, Users, Roles') but uses a single generic verb ('Manage'), so actions are minimal rather than comprehensive.	3 / 5
Completeness	Explicitly answers both what ('Manage Requirements, Projects, Users, Roles') and when ('Use when the user wants to interact with Zephyr Scale data'), though the 'when' clause is generic.	4 / 5
Trigger Term Quality	'Zephyr Scale' plus the entity keywords are relevant triggers, but core test-management terms (test cases, executions, cycles) and synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	Names a specific product (Zephyr Scale) giving a clear niche, but the generic entity nouns overlap slightly with Jira-related skills.	4 / 5
	Total	14 / 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-scale/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.