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
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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. It names the specific project (vercel-plugin), lists concrete release actions, and provides an explicit 'Use when' clause with natural trigger terms. It follows third-person voice and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
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 |
Implementation
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 at every step, has clear sequencing with validation gates and error recovery guidance, and is well-structured for its scope. The checklist at the end is a nice touch for verification.
| Dimension | Reasoning | Score |
|---|---|---|
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 for every step (bun run typecheck, bun test, bun run validate, bun run build, git add/commit/push). The commit message format is specified with a concrete pattern. The version source of truth is explicitly identified. | 3 / 3 |
Workflow Clarity | Clear 5-step numbered sequence with explicit validation checkpoints: 'Stop if any gate fails' after pre-flight, and the note about pre-commit hook failures with recovery guidance (create new commit, never amend). The checklist at the end serves as a final verification step. Feedback loops are present for both pre-flight and pre-commit failures. | 3 / 3 |
Progressive Disclosure | For a single-purpose skill under 50 lines, the content is well-organized with clear sections (workflow steps, version source of truth, checklist). No need for external references given the scope, and the structure supports easy scanning. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- vercel/vercel-plugin
- Commit
61f1903
- 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.