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

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.

A tightly written operational skill: every gate and build command is executable, the workflow is clearly sequenced with validation gates and recovery guidance, and the semver decision table plus checklist remove ambiguity. The only flaw is a small redundancy between step 3 and the version-source section.

Suggestions

Merge the "Version source of truth" section into step 3 — keep the useful note that there is no package.json version to sync, but drop the duplicated 'only source of truth' phrasing.

Optionally note what `bun run validate` checks in one clause (frontmatter + manifest integrity is already commented for typecheck/validate), so a failure message is actionable without re-reading the build step.

Clarify the push target in step 5 (e.g., confirm `git push` targets main), since the checklist says 'pushed to main' but the command leaves the branch implicit.

DimensionReasoningScore

Conciseness

The body is lean — terse commands with inline comments and no explanation of concepts Claude already knows — but the "only version source of truth" statement in step 3 is restated nearly verbatim in the "Version source of truth" section, a minor duplication that could be trimmed.

4 / 5

Actionability

All commands ("bun run typecheck", "bun test", "bun run validate", "bun run build", "git add -A / commit / push") are copy-paste ready, and the commit message template "<summary>; bump to <new-version>" with a pointer to git-log conventions is concrete.

5 / 5

Workflow Clarity

The five-step sequence has explicit validation checkpoints ("Stop if any gate fails", pre-commit hook re-running typecheck), an error-recovery loop (fix and create a new commit, never amend), and a closing checklist — satisfying the validation requirement for a push-to-main workflow.

5 / 5

Progressive Disclosure

This is a compact, single-purpose, self-contained skill with no bundle files; its well-organized sections (workflow, version source, checklist) need no external references, fitting the simple-skill top anchor.

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.

An exemplary description: it enumerates the concrete steps of the release process, states an explicit 'Use when' clause with four natural trigger phrasings, and scopes itself to a specific plugin. Third-person imperative voice is used correctly and there is no padding.

DimensionReasoningScore

Specificity

"run gates, bump version, generate artifacts, commit, and push" lists five concrete actions that comprehensively cover the release workflow, matching the top anchor rather than the minor-gaps level 4.

5 / 5

Completeness

The description explicitly 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 concrete trigger phrases, mirroring the anchor-5 example.

5 / 5

Trigger Term Quality

"release", "ship", "bump and push", and "cut a release" are all natural phrasings a user would say when requesting this skill, with strong synonym coverage and no common release-request variant missing.

5 / 5

Distinctiveness Conflict Risk

Naming the specific project ("Release vercel-plugin") plus release-only trigger phrases gives it a clear niche with minimal risk of triggering for an unrelated skill.

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.

Validation — 16 / 16 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.