CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 well-structured, actionable workflow that is concise, executable, and clearly sequenced with validation checkpoints and a real reference file for deeper detail. It avoids over-explanation and respects the context budget.

DimensionReasoningScore

Conciseness

Lean and operational — bash commands, MCP calls, a categorization table, and bump rules — with no padding explaining concepts Claude already knows (e.g., what git or semver is).

3 / 3

Actionability

Provides fully executable, copy-paste-ready guidance: concrete git commands and complete mcp__github__run_workflow/list/get calls with exact owner, repo, workflow_id, and inputs.

3 / 3

Workflow Clarity

Six clearly sequenced steps with an explicit confirmation checkpoint ('WAIT for explicit confirmation before proceeding') and a poll-until-completed feedback loop, plus an Error Handling recovery section.

3 / 3

Progressive Disclosure

Body serves as an overview with a single, clearly signaled one-level-deep reference to references/WORKFLOW-REFERENCE.md (verified to exist), keeping detailed workflow docs appropriately separated.

3 / 3

Total

12

/

12

Passed

Description

100%

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 strong description that is specific, trigger-rich, and complete, clearly defining both the skill's actions and the conditions for its use without over-claiming. It is distinct and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'analyzing commits since the last release, categorizing changes, recommending semantic version bump type (major/minor/patch), and triggering the release workflow' — matching the multi-action anchor rather than the domain-plus-some-actions level.

3 / 3

Completeness

Explicitly answers both what it does and when to use it via a clear 'Use when…' clause with several triggers, satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Natural trigger terms users would say are well covered: 'cutting a release', 'version bump', 'cut a release', 'checking what changed since last release'.

3 / 3

Distinctiveness Conflict Risk

Scoped to ToolHive release PRs with distinct release/version triggers, giving it a clear niche unlikely to fire for unrelated skills; uses correct third-person voice.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
stacklok/toolhive
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.