Name: release
Rating: 55.2 (1 reviews)
Author: membranedev

release

Release integration. Manage data, records, and automate workflows. Use when the user wants to interact with Release data.

Quality

62%

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

Quality

Content

67%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 a well-structured, command-heavy integration guide with strong actionability and a clear connection-state workflow including feedback loops. Its main weaknesses are a padded intro that over-explains Release, slightly confusing step numbering, and no validation guidance for action execution.

Suggestions

Trim the opening paragraph and entity overview that describe what Release is; assume Claude's domain knowledge and lead directly with the CLI workflow.

Fix the step numbering (e.g., label "1a"/"1b" and an actual "Step 2" section) so the "skip to Step 2" references resolve.

Add a brief validation/check step after `membrane action run` (e.g., inspect the `output` field and handle error states) to cover destructive or batch action execution.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient concrete commands, but the intro paragraph ("Release is a deployment management tool that helps software teams automate and orchestrate their release pipelines...") and the entity overview explain context Claude largely already knows, so it could be tightened.	3 / 5
Actionability	It provides copy-paste-ready CLI commands with flags throughout (connection ensure, action run, request proxy), but placeholders like CONNECTION_ID/QUERY and minor gaps in showing full output handling keep it just below fully executable.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with an explicit state machine (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-after-user-action feedback loop; minor gaps are the confusing step labels ("skip to Step 2" with only a "1b" section) and lack of post-run validation for potentially destructive actions.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Popular actions, Best practices) with no nested references, though some inline material (entity list, proxy flag table) 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 correctly pairs an explicit "Use when" trigger with a named domain, but the listed capabilities are generic verbs ("manage data, records, automate workflows") rather than concrete Release-specific actions. Stronger trigger guidance and more specific capability wording would lift it above the midpoint.

Suggestions

Replace generic verbs with concrete Release-specific actions (e.g., "deploy releases, promote build artifacts across channels, roll back versions, manage release versions") to improve specificity.

Expand the trigger phrase with natural synonyms users actually say (e.g., "Use when the user wants to deploy, promote, roll back, or check release status in Release").

Add file-extension or entity keywords (release channels, versions, deployments) to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ("Release integration") but the stated actions — "Manage data, records, and automate workflows" — are generic and minimal rather than concrete capabilities, matching the anchor where the domain is named but actions are generic.	2 / 5
Completeness	It provides both a "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Release data"); the "when" is clearly stated while the "what" is somewhat generic, placing it above the midpoint but not at the top anchor.	4 / 5
Trigger Term Quality	It includes relevant keywords ("Release", "Release data", "workflows") and an explicit trigger phrase, but misses common variations or synonyms users might naturally say, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to a specific named product ("Release") gives it a clear, mostly distinct niche with minimal conflict risk, though the generic action verbs leave minor overlap risk with adjacent data-management skills.	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/release/SKILL.md
Commit: f484c82

Reviewed: 5 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.