release-process

Operate Squad's automated insider, preview, and stable release channels safely

Quality

67%

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

Quality

Content

81%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.

A well-structured, actionable release runbook with explicit preconditions and validation checkpoints and a recovery loop. Its only real weakness is the Recovery section's reference to an external canonical runbook that is not included in the bundle.

Suggestions

Inline the actual recovery/rerun commands in the Recovery section instead of deferring to a 'canonical runbook' that is not present in the bundle, or ensure the referenced `.squad/skills/release-process/SKILL.md` file ships with the skill.

Set or note `$VERSION` explicitly in the Preconditions block so it is self-contained rather than relying on a value defined later in the Preview section.

Dimension	Reasoning	Score
Conciseness	The body is lean: a compact table, copy-paste bash blocks, and brief prose that conveys team-specific operational detail Claude would not already know; minor explanatory sentences could still be trimmed.	4 / 5
Actionability	Preconditions, Preview, Insider, Stable, and Verify blocks give mostly executable copy-paste commands, but the Recovery section defers to a 'canonical runbook' for exact commands and the Preconditions block uses $VERSION before it is defined.	4 / 5
Workflow Clarity	The release flow is clearly sequenced (preconditions -> dispatch -> watch -> verify) with explicit validation (ancestry commit, version match, SDK floor, changelog entry) and a Recovery feedback loop for the destructive publish operations.	5 / 5
Progressive Disclosure	Content is well split into clearly headed sections (Preconditions, Preview, Insider, Stable, Verify, Recovery), but the referenced `.squad/skills/release-process/SKILL.md` runbook is not present in the bundle, a minor navigation gap.	4 / 5
	Total	17 / 20 Passed

Description

53%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 specific niche (Squad's three release channels) but relies on a single generic verb and omits any explicit 'when to use' trigger guidance. It is distinct but under-specified on actions and triggers.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when publishing or promoting Squad insider/preview/stable releases, or when the user mentions cutting a release, npm publish, or Homebrew/WinGet updates.'

Replace the single verb 'Operate' with multiple concrete actions: 'Publish, promote, and verify Squad releases across insider, preview, and stable channels.'

Include natural trigger synonyms users actually say (publish, promote, cut a release, ship, npm release) alongside the channel names.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete channels ("insider, preview, and stable release channels") but uses only one generic action verb ("Operate ... safely"), so it does not list several specific actions like publish/promote/verify.	3 / 5
Completeness	It states a clear 'what' (operate the three release channels safely) but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Channel names (insider/preview/stable) are relevant, but common natural terms users would say (publish, promote, cut a release, ship, npm release, Homebrew/WinGet) are missing.	3 / 5
Distinctiveness Conflict Risk	"Squad's automated insider, preview, and stable release channels" carves a clear niche with minimal overlap risk; not a 5 only because the trigger phrasing is thin.	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: bradygaster/squad
Path: .copilot/skills/release-process/SKILL.md
Commit: 9587fcd

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