release

Execute the rtp2httpd release workflow — cumulative prerelease and formal release notes, tagging, GitHub releases, collapsing superseded prerelease notes after GA, CI handling, and stable branch updates.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/release/SKILL.md

Quality

Content

77%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 thorough, highly executable runbook with clear sequencing and validation for a complex release process. Its weak spots are repetition that inflates the token budget and a monolithic structure that forgoes progressive disclosure via reference files.

Suggestions

Move the bilingual release-note format templates (patch and minor/major) plus the canonical donation block into a single references file and link to it, removing the triplicated markdown from the body.

Trim the trailing 'Notes' section to only items not already stated in the step bodies to reduce redundancy.

Extract the Step 10 accordion-collapse procedure into a reference script or document so the main flow stays lean.

Dimension	Reasoning	Score
Conciseness	The procedural detail is largely justified for a complex release process, but the donation block markdown is repeated three times and the trailing 'Notes' section restates rules already covered in the steps, which could be tightened.	3 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (`gh release list`, `git tag -a`, `gh release create`, `gh run list`) with exact flags and placeholders, covering the common release cases fully.	5 / 5
Workflow Clarity	Steps 0–14 are explicitly sequenced with validation checkpoints (clean-workspace pre-flight, lint, AskQuestion confirmations, 'verify afterward' checks) and feedback loops (alert-and-stop on CI failure or non-fast-forward), appropriate for destructive batch edits to GitHub releases.	5 / 5
Progressive Disclosure	The file is well-sectioned for in-file navigation, but as a ~470-line skill it inlines material — release-note format templates and the collapse/CI procedures — that would be better placed in one-level-deep reference files, and no bundle references exist.	3 / 5
	Total	16 / 20 Passed

Description

75%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 and clearly scoped to a single project's release process, listing concrete sub-tasks. Its main weakness is the absence of an explicit 'Use when…' trigger clause, which limits completeness.

Suggestions

Add an explicit 'Use when…' clause naming the natural trigger phrases (e.g., 'Use when releasing rtp2httpd, creating release notes, tagging a version, or publishing a GitHub release').

Include common synonyms and the file/tag patterns users might mention (e.g., 'prerelease', 'rc', 'stable branch') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete actions — 'cumulative prerelease and formal release notes, tagging, GitHub releases, collapsing superseded prerelease notes after GA, CI handling, and stable branch updates' — giving comprehensive coverage rather than generic verbs.	5 / 5
Completeness	The 'what' is explicit and detailed, but there is no 'Use when…' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Natural keywords like 'release workflow', 'release notes', 'tagging', and 'GitHub releases' are present and would be said by users, though it leans on project-specific naming and omits a few synonyms.	4 / 5
Distinctiveness Conflict Risk	Scoped specifically to the rtp2httpd release workflow with a clear niche and distinct triggers, making overlap with unrelated skills minimal.	5 / 5
	Total	17 / 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: stackia/rtp2httpd
Path: .agents/skills/release/SKILL.md
Commit: 33fecb8

Reviewed: about 13 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.