CtrlK
BlogDocsLog inGet started
Tessl Logo

release

Perform Harbor release procedures — version bumping, codegen, committing, pushing, and drafting GitHub releases. Use this skill when the user wants to release a new version of Harbor, bump the version number, create a release on GitHub, run the release codegen pipeline, or anything related to shipping a new Harbor version. Triggers on phrases like "release Harbor", "bump version", "new release", "ship a new version", or "prepare 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%

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

The content is a highly actionable, well-sequenced release pipeline with executable commands and an explicit lint validation feedback loop. Its only weakness is progressive disclosure: everything lives in one long SKILL.md with no offloaded reference files.

Suggestions

Move the release-notes template and/or the Step 5 lint-gate script into a referenced file (e.g. references/release-notes-template.md) and link to it from the body, so the main SKILL.md stays a lean overview with one-level-deep references.

Consider extracting the Step 3 commit-classification heuristics into a short checklist reference to reduce inline length while keeping the core 7-step sequence prominent.

DimensionReasoningScore

Conciseness

The body is dense and actionable with no padding of concepts Claude already knows (it does not explain git, versioning, or what a release is); each section earns its tokens for a genuinely multi-step pipeline, matching the lean-and-efficient anchor rather than the mostly-efficient score-2 example.

3 / 3

Actionability

Every step provides fully executable bash, exact file paths (e.g. .scripts/seed.ts line ~9), a fixed commit message, a Python URL-encoding snippet, and a copy-paste release-notes template — copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

A clear 7-step sequence with pre-flight checks and an explicit validation feedback loop in Step 5 ('If this fails, fix every finding and rerun the full lint gate before proceeding'); because validation is present for the batch/destructive release operation, workflow clarity is not capped at 2.

3 / 3

Progressive Disclosure

It opens with an overview paragraph and is well-sectioned, but it is a ~200-line monolithic file with all content inline and no signaled one-level-deep references; exceeding the 50-line simple-skill threshold, it fits the score-2 anchor where content that could be separate stays inline rather than the score-3 split-with-references anchor.

2 / 3

Total

11

/

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.

The description is specific, complete, and distinct: it names concrete release actions, provides explicit 'use when' triggers with natural keyword examples, and is tightly scoped to Harbor releases. It is a strong, low-conflict trigger description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'version bumping, codegen, committing, pushing, and drafting GitHub releases' — matching the score-3 anchor for specific concrete actions rather than vague language.

3 / 3

Completeness

Clearly answers both what (Harbor release procedures and the listed actions) and when ('Use this skill when the user wants to release a new version of Harbor...'), with explicit trigger guidance, so it is not capped at 2.

3 / 3

Trigger Term Quality

Explicitly enumerates natural user phrases ('release Harbor', 'bump version', 'new release', 'ship a new version', 'prepare a release'), giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Targets a clear Harbor-release niche with distinct triggers, unlikely to fire for unrelated skills; uses third-person voice ('Perform Harbor release procedures') so no specificity penalty applies.

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
av/harbor
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.