release-beta

Cut a beta release of Paseo. Use when the user says "release beta", "cut a beta", "ship a beta", "beta release", or "/release-beta".

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/release-beta/SKILL.md

Quality

Content

55%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 admirably concise and appropriately delegates detail to a referenced doc, but it provides almost no actionable or workflow guidance within SKILL.md itself—Claude must read docs/release.md to do anything. For a release operation, inlining at least the key steps or a validation checkpoint would materially improve actionability and workflow clarity.

Suggestions

Inline the high-level sequence of the Beta flow (e.g. branch/tag, build, smoke-test, publish) so the skill is actionable without first opening docs/release.md.

Add an explicit validation/checklist checkpoint before publishing (e.g. confirm the completion checklist passes) to satisfy the feedback-loop expectation for a release operation.

Clarify that docs/release.md is the source of truth and confirm it exists in the repo, since the reference is external to the skill bundle and cannot be verified here.

Dimension	Reasoning	Score
Conciseness	The body is a lean two-sentence pointer with no padding and no over-explanation of concepts Claude already knows; every token earns its place.	5 / 5
Actionability	"Follow the Beta flow and Beta release completion checklist in docs/release.md end-to-end" defers all specifics to an external file and offers no concrete commands or code, leaving only minimal high-level guidance missing the executable steps; not 1 because it does name a specific file and sections.	2 / 5
Workflow Clarity	A beta release is a batch/risky operation that the guidelines cap at 3 absent validation, and the body itself provides no sequence or validation checkpoints—only a rough reference to an external flow and checklist, fitting the many-gaps/validation-absent anchor.	2 / 5
Progressive Disclosure	SKILL.md acts as a clear overview with a one-level-deep, well-signaled reference to docs/release.md naming the relevant sections; not 5 because the referenced file is external (not in any bundle) and the overview is extremely thin.	4 / 5
	Total	13 / 20 Passed

Description

90%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 is excellent: it answers both what and when, uses third person, and provides comprehensive natural trigger phrases. The only minor gap is specificity, since it names a single action rather than enumerating the concrete steps a beta release entails.

Dimension	Reasoning	Score
Specificity	"Cut a beta release of Paseo" names the domain and one concrete action, but lists only a single action rather than several, fitting the 1-2 concrete actions anchor and not the comprehensive coverage of 4 or 5.	3 / 5
Completeness	Clearly states what ("Cut a beta release of Paseo") and explicitly states when with concrete trigger phrases ("Use when the user says..."), matching the explicit-what-and-when anchor.	5 / 5
Trigger Term Quality	Provides comprehensive natural trigger coverage including synonyms ("release beta", "cut a beta", "ship a beta", "beta release") plus the "/release-beta" invocation, matching the comprehensive-synonyms anchor.	5 / 5
Distinctiveness Conflict Risk	Scoped to Paseo beta releases with distinct, specific trigger phrases, giving it a clear niche with minimal overlap risk versus other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: getpaseo/paseo
Path: .agents/skills/release-beta/SKILL.md
Commit: 8533c5c

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