CtrlK
BlogDocsLog inGet started
Tessl Logo

deployments-cicd

Vercel deployment and CI/CD expert guidance. Use when deploying, promoting, rolling back, inspecting deployments, building with --prebuilt, or configuring CI workflow files for Vercel.

68

Quality

85%

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

78%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 highly actionable, well-structured reference with copy-paste CI pipelines, but it carries a lot of inlined reference content with no bundle files to offload it into. Tightening explanatory prose and splitting provider-specific YAML into reference files would lift both conciseness and progressive disclosure.

Suggestions

Move the per-provider CI YAML (GitHub Actions, GitLab, Bitbucket) and the build-error/strategy tables into separate reference files under references/, keeping only a concise canonical example inline in SKILL.md.

Trim definitional asides like 'Preview deployments are created automatically... They provide a unique URL for testing.' that restate platform behavior Claude already knows.

Add an explicit validate-then-proceed checkpoint (e.g. verify build output / run tests before `vercel deploy --prebuilt --prod`) to the core deploy workflow.

DimensionReasoningScore

Conciseness

Mostly efficient reference material with executable code, but a few prose asides (e.g. 'Preview deployments are created automatically for every push... They provide a unique URL for testing.') explain things Claude already knows and could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready vercel commands and complete CI YAML for GitHub Actions, GitLab, and Bitbucket covering the common deploy/preview/promote cases.

5 / 5

Workflow Clarity

Clear sequences (pull -> build --prod -> deploy --prebuilt) and a validated promote-after-tests pattern with e2e gates, but the core deploy flow lacks an explicit validate-before-proceed checkpoint.

4 / 5

Progressive Disclosure

Well-organized into clear sections with an Official Documentation pointer, but no bundle reference files exist and large reference blocks (three full provider YAMLs, build-error table, strategy matrix) are inlined that would fit better in separate files.

3 / 5

Total

16

/

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 names concrete Vercel actions and pairs them with an explicit 'Use when' trigger clause. Minor room to add synonyms/file extensions for fully comprehensive trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'deploying, promoting, rolling back, inspecting deployments, building with --prebuilt, or configuring CI workflow files' — covering the domain comprehensively, matching the anchor for comprehensive concrete actions.

5 / 5

Completeness

Explicitly answers both 'what' (Vercel deployment and CI/CD expert guidance with named actions) and 'when' ('Use when deploying, promoting, rolling back...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage (deploy, promote, rollback, inspect, --prebuilt, CI workflow files for Vercel) but missing some synonyms and file-extension-style triggers that would push it to comprehensive.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to Vercel-specific commands and triggers (--prebuilt, vercel deploy/promote/rollback), giving it a clear niche with minimal conflict risk against generic CI/CD skills.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

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.