release

Execute the rtp2httpd release workflow — tag, GitHub release, CI handling, and stable branch updates.

Quality

80%

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%

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

A highly actionable, clearly sequenced release workflow with strong validation checkpoints and feedback loops. Its main weaknesses are mild redundancy (donation block repeated, Notes restating steps) and a monolithic structure that could offload templates to reference files for better progressive disclosure.

Suggestions

Move the release-notes templates (patch and minor/major formats) and the canonical donation block into a reference file (e.g. references/release-notes-templates.md) and link to it, removing the inline repetitions.

Trim the trailing Notes section to only items not already covered by the steps, or convert it into a short 'Gotchas' list, to reduce redundancy.

Define the v3.x.y placeholder convention once near the top instead of repeating the literal placeholder across many command blocks.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient operational commands with no concept explanations Claude already knows, but the canonical donation block is shown three times and the Notes section restates step content, so it could be tightened — matching the level-2 anchor rather than the fully lean level-3.	2 / 3
Actionability	It provides fully executable git, gh, and pnpm commands with concrete examples and copy-paste-ready snippets (only version placeholders remain), matching the level-3 anchor and clearly above the pseudocode level-2.	3 / 3
Workflow Clarity	Thirteen steps are clearly sequenced with explicit validation checkpoints (clean-workspace pre-flight, lint with fix-and-retry, CI polling loop with a 10-minute timeout, ff-only merge abort) and feedback loops for this batch/release operation, matching the level-3 anchor.	3 / 3
Progressive Disclosure	Sections are well-organized with headers and separators, but at ~340 lines everything is inline in one file with no bundle references split out (release-note templates and the donation block could live in separate reference files), fitting the level-2 'content that should be separate is inline' anchor rather than the one-level-deep level-3.	2 / 3
	Total	10 / 12 Passed

Description

82%

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, specific, third-person description that names concrete actions and occupies a clear niche, but it omits an explicit 'Use when...' trigger clause, capping completeness at 2. Adding a trigger sentence would raise it to a strong 3 across the board.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when releasing rtp2httpd — cutting a tag, publishing a GitHub release, or updating the stable branch.'

Consider adding the SemVer/prerelease variants ('release', 'prerelease', 'tag a release') as natural trigger terms to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'tag, GitHub release, CI handling, and stable branch updates' lists multiple specific concrete actions within the rtp2httpd release domain, matching the level-3 anchor rather than the partial level-2 listing.	3 / 3
Completeness	It clearly states what the skill does but lacks any 'Use when...' clause or equivalent explicit trigger guidance, so per the guidelines completeness is capped at 2 even though the 'what' is strong.	2 / 3
Trigger Term Quality	Natural terms a user would say when needing this skill ('release', 'tag', 'GitHub release', 'stable branch') are present and cover common variations, fitting the level-3 anchor; not the jargon-heavy level-1 or partial level-2.	3 / 3
Distinctiveness Conflict Risk	The project-specific 'rtp2httpd release workflow' niche with distinct release triggers makes it unlikely to fire for unrelated skills, matching the level-3 clear-niche anchor.	3 / 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: stackia/rtp2httpd
Path: .agents/skills/release/SKILL.md
Commit: f63adb0

Reviewed: 2 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.