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

77

Quality

96%

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

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 well-structured, highly actionable workflow with executable commands, explicit confirmation and monitoring checkpoints, and a clean one-level reference to a real bundle file. Minor trimming of the example output would tighten conciseness.

DimensionReasoningScore

Conciseness

Mostly efficient with commands, tables, and numbered steps assuming Claude's competence, though the detailed example output and some explanatory prose could be trimmed; not quite the lean anchor 5.

4 / 5

Actionability

Provides copy-paste-ready bash commands and fully-parameterized MCP tool calls covering the common cases, matching the executable anchor 5.

5 / 5

Workflow Clarity

Clear six-step sequence with an explicit human-confirmation checkpoint before the destructive release trigger, plus polling and error-handling feedback loops for recovery.

5 / 5

Progressive Disclosure

Well-organized sections in the body with a single one-level-deep, clearly signaled reference to the real references/WORKFLOW-REFERENCE.md for detail; content appropriately split.

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.

The description is exemplary: it states concrete capabilities, includes a rich set of natural trigger phrases, and explicitly covers both what and when. It is third-person, concise, and clearly distinct.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — analyzing commits, categorizing changes, recommending bump type, triggering the workflow — with comprehensive coverage matching the anchor 5 example.

5 / 5

Completeness

Explicitly answers both what (creates release PRs via analyze/categorize/recommend/trigger) and when via a concrete 'Use when...' clause with trigger phrases, matching anchor 5.

5 / 5

Trigger Term Quality

Covers natural phrases a user would say ('cutting a release', 'version bump', 'cut a release', 'preparing a new version') with synonym variation, matching the comprehensive anchor 5.

5 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche (ToolHive release PRs) with distinct release/version triggers and minimal conflict risk with other 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.

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.