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

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

An excellent, executable runbook: concise, concrete, well-sequenced with validation checkpoints, and appropriately self-contained. No meaningful weaknesses relative to the rubric.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — assumes Claude's knowledge of git, CI, and releases without restating basics; every section adds project-specific value rather than padding.

5 / 5

Actionability

Fully executable, copy-paste ready commands at every step (release.sh, git tag/log, lint gate block, commit/push, URL-building python snippet) with concrete file paths and parameter tables.

5 / 5

Workflow Clarity

Clear 7-step sequence with explicit pre-flight checks and an enforced validation checkpoint (zero-findings lint gate with fix-and-rerun feedback loop) for this batch/push operation.

5 / 5

Progressive Disclosure

No bundle files are needed; the self-contained body is cleanly sectioned (Pre-flight, Steps 1–7, Release Notes Template) and well-organized, meeting the simple-skill exception for top marks.

5 / 5

Total

20

/

20

Passed

Description

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

A strong, specific description that clearly states what it does and when to invoke it, with a good set of natural trigger phrases. The only minor gap is slightly broader synonym coverage in the trigger terms.

Suggestions

Consider adding a couple more natural synonyms/shorthand to the trigger list (e.g. 'cut a release', 'publish Harbor', 'version bump') to broaden coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete release actions — 'version bumping, codegen, committing, pushing, and drafting GitHub releases' — covering the procedure comprehensively with no vague filler.

5 / 5

Completeness

Explicitly answers both 'what' (the release procedures and actions) and 'when' with concrete trigger phrases in a 'Use this skill when...' / 'Triggers on...' clause.

5 / 5

Trigger Term Quality

Provides several natural phrases users would say ('release Harbor', 'bump version', 'new release', 'ship a new version', 'prepare a release') but is missing a few common synonyms or shorthand variations.

4 / 5

Distinctiveness Conflict Risk

Scoped narrowly to Harbor release procedures with distinct triggers, making overlap with unrelated skills minimal.

5 / 5

Total

19

/

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