Name: release
Rating: 72.8 (1 reviews)
Author: lfnovo

release

Orchestrate an Open Notebook release — changelog audit, risk-based A/B/C test matrix, Docker image gate (fresh + upgrade), fix loop via PRs, cut, publication with credits, retro. Use when preparing, testing, cutting or publishing a release.

Quality

90%

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

The canonical home for this skill is release in lfnovo/open-notebook

Quality

Content

88%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 highly actionable, well-sequenced release runbook with strong validation gates and feedback loops, and it appropriately defers detail to one-level-deep reference files. It could be slightly tighter on parenthetical asides, and the referenced bundle files are not present to verify the disclosure structure.

Suggestions

Trim narrative parentheticals (e.g. version-history anecdotes like "caught 48 leaked credentials in v1.12.0") into the referenced RELEASE_PROCESS.md so the overview stays leaner.

Ensure the referenced bundle files (gates.md, test-matrix.md, runbook.md, comms-templates.md) are actually shipped in the skill directory so the one-level-deep references resolve.

Consider moving the detailed per-bucket command lists of Phase 2 into test-matrix.md or a dedicated checklist to lighten the overview further.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven with no concept padding, but a few parenthetical operational asides (e.g. "caught 48 leaked credentials in v1.12.0", "a stale node_modules produces false build failures") add length that could be trimmed, placing it just below the fully lean 5 anchor.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands (e.g. "uv run pytest tests/", "make release-test TAG=<ver> OLD_TAG=<prev>", "gh workflow run build-and-release.yml --ref main -f push_latest=false") with clearly marked placeholders covering the common cases, matching the 5 anchor.	5 / 5
Workflow Clarity	A clear Phase 0–9 sequence with explicit validation checkpoints and human gates ("Do not proceed without their GO", "re-run the image gate") plus a feedback loop in Phase 4 that routes Phase 6 findings back, matching the 5 anchor for sequenced validation with error-recovery loops.	5 / 5
Progressive Disclosure	References to gates.md, test-matrix.md, runbook.md, and comms-templates.md are one level deep and clearly signaled inline at each phase, but no bundle files (references/scripts/assets) are physically present in the workspace to verify, and the overview itself carries substantial inline detail, so it sits below the fully-split 5 anchor.	4 / 5
	Total	18 / 20 Passed

Description

92%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, complete, and clearly scoped to a distinct niche, with concrete triggers for when to use it. Its only weakness is trigger-term breadth, where a few natural synonyms would push it to a perfect score.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete release actions — "changelog audit", "risk-based A/B/C test matrix", "Docker image gate (fresh + upgrade)", "fix loop via PRs", "cut", "publication with credits", "retro" — giving comprehensive coverage of the release lifecycle, matching the 5 anchor rather than 4.	5 / 5
Completeness	Explicitly answers both what ("Orchestrate an Open Notebook release" plus the enumerated steps) and when ("Use when preparing, testing, cutting or publishing a release") with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	"Use when preparing, testing, cutting or publishing a release" supplies good natural verbs users say, but lacks synonyms (e.g. "ship") and version/file markers, so it sits above 3 but below the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	"Open Notebook release" is a clear niche with distinct triggers unlikely to fire for unrelated skills, matching the 5 anchor for minimal conflict risk.	5 / 5
	Total	19 / 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: lfnovo/open-notebook
Path: .claude/skills/release/SKILL.md
Commit: 8297bb2

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.