release-cut

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

Quality

94%

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

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

An excellently engineered release workflow: lean, fully actionable, with explicit validation checkpoints and failure-recovery loops for its destructive operations. The only minor weakness is that all content lives in one slightly-dense file rather than being progressively split.

Suggestions

Consider extracting the long artifact-verification checklist (macOS, Windows, DEB, RPM, Pacman, AppImage, Snap, Flatpak, etc.) into a references file so the main body stays a lean overview.

The final byte-identical `.codex`/`.claude` sync note could move to a maintenance note, keeping the release workflow itself focused.

Dimension	Reasoning	Score
Conciseness	The body is dense and lean: every line carries a concrete command, exact git invocation, or operational constraint, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (e.g. `pnpm run release:notes:validate`, `node tools/release/build-release-notes.mjs --consume`, `git push upstream v0.25.1`) with concrete example values for version and remote.	5 / 5
Workflow Clarity	Clear sequenced sections (Preflight, Generate, Push and External Effects, Failure Safety) with explicit validation checkpoints (notes validate, i18n, CI green, tag-existence, artifact verification) and error-recovery feedback loops, satisfying the destructive-ops validation requirement.	5 / 5
Progressive Disclosure	Well-organized into clear sections with easy navigation and no nested references, but it is a single self-contained ~68-line file slightly above the simple-skill threshold with no external split, so it is good rather than exemplary.	4 / 5
	Total	19 / 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.

A concise, well-constructed description that pairs an explicit "Use when" trigger with a comprehensive list of concrete release actions tied to a specific project, leaving little ambiguity about scope. The only gap is slightly limited synonym coverage in the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists five concrete release actions ("preparing, cutting, tagging, publishing, or verifying") on a defined domain ("an IPTVnator release or its release assets"), giving comprehensive coverage of the release lifecycle.	5 / 5
Completeness	Explicitly answers both what (the five release actions) and when via the "Use when preparing, cutting, tagging, publishing, or verifying..." clause, matching the concrete-trigger-phrase pattern.	5 / 5
Trigger Term Quality	Natural release phrases like "cutting", "tagging", "publishing", and "verifying" a release map well to what users say, but coverage lacks synonyms (e.g. ship, version bump) and is scoped to one project, so it is not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	Naming the specific project "IPTVnator" and its release assets carves out a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	19 / 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: 069b8b3

Reviewed: ~17 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.