Tessl • The management layer for AI agent skills

An exemplary operational runbook: exact commands, explicit sequencing, destructive boundaries named, verification gating, and an error-recovery section. Its only deductions are stale-prone literal version/asset-count examples and slight reference clutter from repo-external paths and the canonical-source footer.

Dimension	Reasoning	Score
Conciseness	The body is dense and command-first with essentially no padding — it explains only non-obvious rationale such as "`--silent`, or pnpm's lifecycle banner lands in the saved post". Hard-coded version examples (`v0.24.0`, `v0.25.1`) and the "complete 27-asset set" count are version-number details outside any old-patterns section, keeping it just below anchor 5.	4 / 5
Actionability	Nearly every step ships an exact, copy-paste-ready command: `pnpm run release:notes:validate`, `node tools/release/build-release-notes.mjs --consume`, `git push upstream master`, `git push upstream v0.25.1`, `pnpm run release:verify:draft`. The few non-command steps ("finish every editorial field", "Manually publish the release") are explicitly manual/editorial, so the guidance is fully executable where execution is possible.	5 / 5
Workflow Clarity	Clear sequence with explicit validation and feedback loops: preflight checks (tag existence, CI green, `release:notes:validate`, `i18n:check`), ordering constraints with rationale ("Steps 5 and 6 must precede `--consume`: `highlight:` exists only in the note files it deletes"), a named destructive boundary, `release:verify:draft` gating publication, and a Failure Safety recovery loop (regenerate, resolve the exact tag target, delete the bad tag, retag). The destructive-operation cap does not apply because validation is pervasive.	5 / 5
Progressive Disclosure	Well-sectioned overview that correctly defers the "Full contract, asset table and rationale" to `docs/architecture/release-pipeline.md`, with one-level references. No bundle files exist (references/, scripts/, assets/ are absent), one reference uses a buried `../../../docs/development/release-cover-artwork.md` path outside the skill bundle, and the trailing "Canonical source: `.agents/skills/`" line is meta-clutter — good structure with minor organization gaps, matching anchor 4.	4 / 5
	Total	18 / 20 Passed

Description

70%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 highly distinct, well-triggered description whose 'when' clause doubles as a capability list. Its main weakness is the absence of an explicit 'what' statement, leaving the functional summary implicit. Trigger coverage is good but could add common release synonyms.

Suggestions

Add an explicit 'what' clause before the trigger, e.g. "Guides the full IPTVnator release process: changelog and notes generation, announcement drafts, tagging, asset verification, and publishing. Use when...".

Include common trigger synonyms such as "ship", "roll out", or "cut a release of IPTVnator" to broaden natural keyword coverage.

Name the concrete artifacts the skill handles (changelog, blog post, Telegram/Reddit drafts, highlight cards, Snap/Docker assets) to sharpen the capability list.

Dimension	Reasoning	Score
Specificity	"preparing, cutting, tagging, publishing, or verifying an IPTVnator release or its release assets" lists several concrete release-lifecycle actions, matching anchor 4. It falls short of anchor 5 because the actions are lifecycle stages of one process rather than comprehensive coverage of the skill's distinct capabilities (changelog generation, announcements, screenshots are never named).	4 / 5
Completeness	The description is entirely a "Use when..." clause: 'when' is explicit and rich, but no standalone 'what' is stated. The enumerated activities lift it above anchor 2's vague only-'when' example, but scoring only what is explicit, it cannot match anchor 4's "has both 'what' and 'when'".	3 / 5
Trigger Term Quality	Natural user phrasings like "cutting", "tagging", "publishing", "release", and "release assets", anchored by the product name "IPTVnator", give good keyword coverage. A few natural synonyms ("ship", "roll out", "version bump") are missing, so it does not reach anchor 5's comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	"IPTVnator release or its release assets" carves out a clear product-specific niche with distinct triggers, giving minimal conflict risk with any other skill. This clearly matches anchor 5.	5 / 5
	Total	16 / 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
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: 4gray/iptvnator
Path: .agents/skills/release-cut/SKILL.md
Revision: d3f7f89

Reviewed: 5 days ago

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.

release-cut

Table of Contents

Is this your skill?