CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

toolhive-release

Creates ToolHive release PRs by analyzing commits since the last release, categorizing changes, recommending semantic version bump type (major/minor/patch), and triggering the release workflow. Use when cutting a release, preparing a new version, checking what changed since last release, or when the user mentions "release", "version bump", or "cut a release".

Quality

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 tightly sequenced, fully actionable runbook: exact git commands, parameterized MCP tool calls, an explicit user-confirmation gate before the irreversible workflow trigger, polling validation, and error-recovery loops, with detailed workflow documentation properly externalized to a one-level reference file. Its only weakness is mild redundancy — the 'When to Use' section and the workflow-chain details duplicate the frontmatter description and Step 6's reporting instructions — which keeps conciseness just below the top anchor.

Suggestions

Trim the 'When to Use' section (or reduce it to a single line) since the frontmatter description already carries the same trigger phrases, cutting redundant tokens.

State the release-environment approval detail once — either in Step 6's reporting instructions or the 'Release Workflow Chain' section — and let WORKFLOW-REFERENCE.md carry the full chain description.

Shorten the 22-line 'Example Output' to a skeleton (section headers plus one entry per category) to preserve the format model while reducing tokens.

DimensionReasoningScore

Conciseness

The steps are command-dense with no concept explanations Claude already knows, but there is redundancy: the intro line and 'When to Use' section restate the frontmatter description, and the release-environment approval detail appears both in Step 6 ('waits for a reviewer on the `release` environment') and in the 'Release Workflow Chain' section. This matches anchor 4 (efficient, minor instances that could be trimmed) rather than 5, where every token would earn its place.

4 / 5

Actionability

Every step gives exact, ready-to-run commands ('git tag --sort=-v:refname | head -1', 'git log <last-tag>..HEAD --oneline --no-merges') and fully parameterized MCP calls (mcp__github__run_workflow with owner, repo, workflow_id, ref, and bump_type inputs), plus a concrete example output and specific error-handling commands. This matches the fully-executable anchor rather than 4, as there are no meaningful gaps in the guidance.

5 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced with an explicit validation checkpoint ('Present the analysis and recommendation to the user and WAIT for explicit confirmation before proceeding'), polling validation ('check the `status` field until it shows "completed"'), and feedback loops for error recovery (Error Handling section: check `conclusion`, investigate with get_job_logs, re-poll then search for the PR). Checkpoints and recovery loops are explicit, matching anchor 5 rather than 4.

5 / 5

Progressive Disclosure

The body is a well-sectioned overview that externalizes detailed workflow documentation to a single clearly-signaled, one-level-deep reference ('See [WORKFLOW-REFERENCE.md](references/WORKFLOW-REFERENCE.md)'), which exists in the bundle (191 lines, no nested references). The inline three-step workflow chain summary is appropriate overview-level content, and the categorization table and example output belong inline; this matches the clear-overview anchor rather than 4.

5 / 5

Total

19

/

20

Passed

Description

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

This is an exemplary description: it names the specific project and four concrete actions in third person, and pairs a clear 'what' with an explicit 'Use when' clause containing natural quoted trigger phrases and their synonyms. It closely matches the rubric's good-example pattern with no vague or padded language.

DimensionReasoningScore

Specificity

'Creates ToolHive release PRs by analyzing commits since the last release, categorizing changes, recommending semantic version bump type (major/minor/patch), and triggering the release workflow' lists four concrete, specific actions covering the full workflow end-to-end in third person. This matches the comprehensive-coverage anchor; it is not 4 because there are no meaningful gaps in the action coverage.

5 / 5

Completeness

It explicitly answers both 'what' (the four concrete actions) and 'when' ('Use when cutting a release, preparing a new version, checking what changed since last release, or when the user mentions "release", "version bump", or "cut a release"') with concrete trigger phrases, mirroring the anchor-5 example structure exactly. A missing or weak 'when' clause would cap it at 3; here both parts are explicit.

5 / 5

Trigger Term Quality

It includes natural phrases users would actually say ('cutting a release', 'preparing a new version', 'checking what changed since last release') plus explicitly quoted keywords ('release', 'version bump', 'cut a release') with synonym variation. Coverage is comprehensive for this domain; it is not 4 because no significant natural terms are missing.

5 / 5

Distinctiveness Conflict Risk

'Creates ToolHive release PRs' anchors the skill to a specific project niche with release-specific triggers, giving a clear niche with minimal conflict risk against generic skills. It is not 4 because the project-specific domain leaves virtually no overlap with closely related skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

stacklok/toolhive

Path

.claude/skills/toolhive-release/SKILL.md

Reviewed

Table of Contents

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.