CtrlK
BlogDocsLog inGet started
Tessl Logo

release

Release vercel-plugin — run gates, bump version, generate artifacts, commit, and push. Use when asked to "release", "ship", "bump and push", or "cut a release".

80

Quality

100%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

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.

This is an excellent release workflow skill. It is concise, fully actionable with executable commands, clearly sequenced with validation gates, and well-structured for its scope. The checklist at the end is a nice touch for verification, and the skill avoids explaining concepts Claude already knows while providing all the project-specific details needed.

DimensionReasoningScore

Conciseness

Every section earns its place. No unnecessary explanations of what semver is, what git does, or how bun works. The table for version bump types is compact and informative. The checklist is practical, not filler.

3 / 3

Actionability

Provides exact executable commands (bun run typecheck, bun test, bun run validate, bun run build, git add/commit/push), specifies the exact file to modify (.plugin/plugin.json), and gives a concrete commit message format with examples.

3 / 3

Workflow Clarity

Clear 5-step sequence with explicit validation checkpoints: step 1 is a gate that must pass before proceeding, step 4 rebuilds artifacts, and the pre-commit hook provides an additional safety net. The 'Stop if any gate fails' instruction and the checklist provide feedback loops. The note about never amending commits handles error recovery.

3 / 3

Progressive Disclosure

For a single-purpose workflow skill under 50 lines, the content is well-organized with clear sections (pre-flight, version bump, build, commit/push, version source of truth, checklist). No need for external references given the scope, and no monolithic walls of text.

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.

This is a strong, well-crafted description that concisely names the target project (vercel-plugin), lists specific release actions, and provides explicit trigger terms in a 'Use when...' clause. It uses third person voice and covers natural user language variations effectively. Minor improvement could include mentioning file types or tooling (e.g., npm, changelog) but overall it's excellent.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'run gates, bump version, generate artifacts, commit, and push.' These are clear, actionable steps in a release pipeline.

3 / 3

Completeness

Clearly answers both what ('run gates, bump version, generate artifacts, commit, and push') and when ('Use when asked to "release", "ship", "bump and push", or "cut a release"') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Includes natural trigger terms users would actually say: 'release', 'ship', 'bump and push', 'cut a release'. These are common developer phrases for this workflow.

3 / 3

Distinctiveness Conflict Risk

Scoped specifically to 'vercel-plugin' releases with a distinct set of triggers ('release', 'ship', 'cut a release') that are unlikely to conflict with general coding or deployment skills. The project name anchors it clearly.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
vercel/vercel-plugin
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.