Name: release-process
Rating: 60.8 (1 reviews)
Author: bradygaster

Blog Docs Log in Get started

release-process

Pre-release validation, npm publish procedures, and post-publish verification

Quality

71%

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

Quality

Content

77%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 and exceptionally well-sequenced with explicit validation gates and feedback loops for a risky publish workflow. Its main weaknesses are redundancy across the Rules, Gotchas, and Incident Learnings sections and heavy inlining of incident detail that could be split into reference files.

Suggestions

Consolidate the repeated v0.9.4/root-package.json/CHANGELOG/GITHUB_TOKEN lessons so each appears once; cross-reference from the Gotchas table instead of restating the full explanation.

Move the detailed v0.9.4 incident write-ups and the ancestry worked example into reference files under references/ and link to them one level deep, reducing SKILL.md to the overview and rules.

Isolate time-sensitive incident dates and version numbers (e.g., 2026-08-13, v0.9.0/v0.9.1/v0.9.4) into a dedicated 'Incident history' or 'Deprecated patterns' section so the evergreen rules stay lean.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational with no concept over-explanation, but the same lessons are repeated across Rules, Known Gotchas, and v0.9.4 Incident Learnings, and time-sensitive dates/versions are woven through main content rather than isolated in a deprecated section.	3 / 5
Actionability	Provides copy-paste-ready, fully executable commands throughout (git merge-base, grep scans, cd-based npm publish, gh workflow run, smoke-test commands) covering the common release cases.	5 / 5
Workflow Clarity	The release process is clearly sequenced with a 17-step checklist, explicit STOP validation gates (Rule 0, Rule 2), a numbered fallback protocol, and feedback loops (smoke test -> rollback), matching the anchor for explicit validation steps and checklists.	5 / 5
Progressive Disclosure	Section structure is present (SCOPE, Rules, Checklist, Gotchas, Learnings, Related) with signaled references to repo files, but no bundle files exist and substantial detail (full v0.9.4 incident write-ups, ancestry worked example) is inlined that could live in separate reference files.	3 / 5
	Total	16 / 20 Passed

Description

66%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 specific and well-scoped to npm release workflows, but it omits an explicit 'when to use' trigger clause, which caps its completeness. It is concise and distinct, with good but not comprehensive trigger-term coverage.

Suggestions

Add a 'Use when...' clause stating the trigger conditions (e.g., 'Use when preparing an npm release, publishing @bradygaster/squad packages, or recovering from a failed publish').

Include more natural trigger terms and synonyms such as 'version bump', 'release tag', 'npm registry', and 'CHANGELOG' to broaden keyword coverage.

Make the three capability areas slightly more concrete (e.g., 'validate package.json for file:/link: refs' instead of 'Pre-release validation') to push specificity toward 5.

Dimension	Reasoning	Score
Specificity	Names three concrete capability areas ('Pre-release validation', 'npm publish procedures', 'post-publish verification'), matching the anchor for several specific actions with minor gaps; 'procedures' and 'verification' are slightly abstract, keeping it below 5.	4 / 5
Completeness	Clearly answers 'what' with three named capabilities but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes solid natural phrases a user would say ('npm publish', 'pre-release validation') but lacks synonyms and adjacent terms like 'version bump', 'registry', or 'release tag', so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	Scoped to npm publish release workflows, a distinct niche with low conflict risk; minor overlap with general CI/versioning skills keeps it just below 5.	4 / 5
	Total	15 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: bradygaster/squad
Path: .squad/skills/release-process/SKILL.md
Commit: a0d2563

Reviewed: about 15 hours 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.