CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

marketplace

Vercel Marketplace expert guidance — discovering, installing, and managing third-party integrations via the `vercel integration` CLI. Use when building any app that needs an external capability without a dedicated skill — commerce (stores, storefronts, selling products), payments (checkout, subscriptions, billing), observability/monitoring, messaging/email, search, or CMS — or when discovering, installing, or managing integrations.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

Excellent instructional content: an explicit MUST FOLLOW decision procedure, a fully concrete command surface, and a well-gated sequence with error-recovery and destructive-operation safeguards. The only trimmable fat is the duplicated install-first emphasis and repeated dedicated-skill routing.

Suggestions

Consolidate the install-first warning into one place — the opening paragraph and step 3 of the sequence both deliver the same 'scaffold-first is throwaway' message.

State the dedicated-skill routing (vercel-storage/auth/ai-sdk) once and let the Cross-References section carry the rest.

DimensionReasoningScore

Conciseness

The body is dense and operational — no concepts Claude already knows are explained, and nearly every line is a command, decision rule, or warning. It falls short of 'every token earns its place' only because the install-first/throwaway warning is stated twice (opening paragraph and step 3) and dedicated-skill routing appears three times (intro, category map, cross-references).

4 / 5

Actionability

Commands are copy-paste ready with exact flags: "`vercel integration add <name> --no-claim`", "`vercel env pull --yes`", "`vercel integration resource remove <resource>`", plus a concrete provider-decision table, framework-specific guide flags, and the `npx skills add` recovery command — fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

"The sequence" gives a numbered categorize → discover → install → build workflow with explicit validation checkpoints: a STOP-and-ask gate for account/browser steps, an error-recovery loop for failed skill installs ("never re-run `vercel integration add`... have the user run only that"), and an explicit user-approval gate before destructive removal.

5 / 5

Progressive Disclosure

This is a self-contained single-file skill (no references/scripts/assets bundle exists) whose content fits comfortably inline: clear section headers, well-signaled one-level cross-references ("⤳ skill: vercel-storage"), and explicit official-doc links. Nothing that belongs in a separate file is inlined, and navigation is easy.

5 / 5

Total

19

/

20

Passed

Description

96%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 description: it names the exact CLI, lists the full action lifecycle, and provides an explicit 'Use when' clause with an extensive catalog of natural trigger phrases. The only weakness is that broadly applicable category words (payments, search, monitoring) are not scoped to Vercel, creating slight trigger ambiguity against domain-specific skills.

Suggestions

Tie the broad category triggers to the Vercel context (e.g., "payments or a store on Vercel") so terms like "payments" and "search" don't risk firing for non-Vercel domain skills.

Consider mentioning removal/updates explicitly (e.g., "installing, updating, or removing") since "managing" currently subsumes them.

DimensionReasoningScore

Specificity

"discovering, installing, and managing third-party integrations via the `vercel integration` CLI" names both the exact tool and multiple concrete lifecycle actions (discover, install, manage — which covers add/update/remove), matching the comprehensive-coverage anchor rather than the 'minor gaps' level below.

5 / 5

Completeness

It explicitly answers 'what' ("Vercel Marketplace expert guidance — discovering, installing, and managing third-party integrations via the `vercel integration` CLI") and 'when' ("Use when building any app that needs an external capability without a dedicated skill — ... — or when discovering, installing, or managing integrations") with concrete trigger phrases.

5 / 5

Trigger Term Quality

The description catalogs natural user phrasings with synonyms across categories — "stores, storefronts, selling products", "checkout, subscriptions, billing", "messaging/email, search, or CMS" — plus "discovering, installing, or managing integrations", giving comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

"without a dedicated skill" carves a clear Vercel niche, but broad category terms like "payments", "search", and "observability/monitoring" carry minor overlap risk with closely related non-Vercel domain skills. It is mostly distinct with only minor overlap risk, short of the 'minimal conflict risk' anchor.

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

Validation — 13 / 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

Path

skills/marketplace/SKILL.md

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.