release-cut

Cut an IPTVnator release — bump the version, generate release notes from .changes/, scaffold the website post, tag, and verify the draft. Use when asked to release, cut a version, prepare release notes, or publish a new version.

Quality

91%

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

90%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, executable release runbook with a clear sequenced workflow, explicit validation, and useful failure-mode recovery guidance. It would benefit from splitting denser reference material into bundle files and trimming a few explanatory clauses that restate the surrounding commands.

Suggestions

Move the per-platform asset checklist (dmg/zip/exe/deb/rpm/AppImage + latest*.yml) into a references file linked from step 8 to reduce body length and enable one-level-deep progressive disclosure.

Trim clauses that restate the commands (e.g. 'so the changelog step is not optional', 'the only destructive step') since the code and failure-mode notes already convey this.

Add a short pointer to a manifest schema reference for tools/release/screenshots.manifest.json instead of inlining the slug-matching rule.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes competence, but a few clauses restate what the commands already imply (e.g. 'the only destructive step', 'so the changelog step is not optional'), keeping it just short of the score-3 lean bar.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands (pnpm run release:notes:validate/changelog/blog, node ... --consume, git tag/push) plus concrete output paths and manifest edits.	3 / 3
Workflow Clarity	Clear numbered sequence with explicit validation checkpoint (release:notes:validate), idempotency and guard/abort notes for screenshots, and a Failure modes section giving fix-and-retry feedback loops for destructive steps.	3 / 3
Progressive Disclosure	Internally well-organized into Sequence and Failure modes, but the skill is monolithic with no bundle files to offload the longer reference material (asset lists, manifest schema) into, so it is not one-level-deep reference structured.	2 / 3
	Total	10 / 12 Passed

Description

92%

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 strong, third-person description that lists concrete actions and provides an explicit 'Use when' trigger clause, clearly satisfying both the what and when requirements. Minor conflict risk remains because several trigger terms are generic across publish/versioning workflows.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ('bump the version, generate release notes from .changes/, scaffold the website post, tag, and verify the draft') rather than vague language, matching the score-3 anchor.	3 / 3
Completeness	Explicitly answers both what (the release pipeline surfaces) and when (the 'Use when...' clause), so both halves are present.	3 / 3
Trigger Term Quality	Natural trigger phrasing users would actually say ('asked to release, cut a version, prepare release notes, or publish a new version') gives good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The release/version niche is fairly specific to IPTVnator, but 'cut a version' and 'publish a new version' are generic enough to overlap with other packaging/publish skills.	2 / 3
	Total	11 / 12 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: deae0a2

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.