release-cut

Use when preparing, cutting, tagging, publishing, or verifying an IPTVnator release or its release assets.

Quality

96%

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

Quality

Content

92%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 dense, executable release runbook with strong sequencing, explicit validation checkpoints, and a clear destructive boundary; its only weakness is literal version numbers embedded in examples, which slightly undercuts token efficiency.

Suggestions

Replace literal version numbers in examples (v0.24.0, v0.25.1) with placeholders like v<version> to avoid time-sensitive content, or move concrete version examples into a dedicated 'examples' section.

Consider moving the '27-asset set' detail fully behind the existing release-pipeline.md reference rather than restating the count inline.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational with no concept padding, but embeds literal version numbers (e.g. "v0.24.0", "v0.25.1", "27-asset set") as command examples; per the rubric, version-number time-sensitivity dents conciseness unless isolated in a deprecated section.	4 / 5
Actionability	Fully executable throughout — concrete commands like `pnpm run release:notes:validate`, `node tools/release/extract-changelog-section.mjs --public "${VERSION}"`, `git push upstream master`, and `git push upstream v0.25.1` are copy-paste ready and cover the common cases.	5 / 5
Workflow Clarity	Clear Preflight → Generate → Push → verify → publish sequence with explicit validation checkpoints (`release:notes:validate`, `release:verify:draft`), a marked destructive boundary (the `--consume` step), and a Failure Safety feedback loop for missing CHANGELOG sections.	5 / 5
Progressive Disclosure	Well-organized sections (Preflight, Generate, Push and External Effects, Failure Safety) with a clearly signaled one-level reference to `docs/architecture/release-pipeline.md` for the full contract and asset table; no bundle files exist, so the well-structured overview earns the top anchor.	5 / 5
	Total	19 / 20 Passed

Description

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

A tight, third-person description that pairs a concrete action list with an explicit "Use when" trigger and a project-specific niche, covering both what and when with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "preparing, cutting, tagging, publishing, or verifying" an IPTVnator release plus "its release assets" — giving comprehensive coverage of the release lifecycle rather than generic verbs.	5 / 5
Completeness	Explicitly answers both what (the five release actions and assets) and when via the "Use when preparing, cutting, tagging, publishing, or verifying..." trigger clause, matching the concrete-trigger anchor.	5 / 5
Trigger Term Quality	"preparing, cutting, tagging, publishing, or verifying" are exactly the natural phrases a user would say when needing this skill (e.g. "cut a release", "tag the release", "publish v0.24"), with several synonyms covered.	5 / 5
Distinctiveness Conflict Risk	Scoped to "an IPTVnator release or its release assets" — a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	20 / 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: 4gray/iptvnator
Path: .claude/skills/release-cut/SKILL.md
Commit: 9a3aa63

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.