Name: vercel
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

vercel

Vercel integration. Manage Projects, Users, Teams, Secrets. Use when the user wants to interact with Vercel data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/vercel/SKILL.md

Quality

Content

67%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.

The body is a well-structured, mostly executable guide to driving Vercel through the Membrane CLI, with a strong connection-state workflow and a handy actions table. Its main weaknesses are an unnecessary Vercel explainer and the absence of validation notes around destructive actions.

Suggestions

Cut the opening "Vercel is a platform..." paragraph and the "focus on the integration logic" filler; assume Claude knows what Vercel is.

Add a validation/confirmation step before destructive actions, e.g. "Before running cancel-deployment or delete-project, confirm the target ID with the user and check the result's `output` field for success".

Consider moving the 20-row popular-actions table into a references/popular-actions.md and linking to it, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The guide is mostly efficient CLI commands and a useful actions table, but the opening paragraph ("Vercel is a platform for deploying and hosting web applications...") explains what Vercel is, which Claude already knows, and there is light filler like "so you can focus on the integration logic rather than auth plumbing".	3 / 5
Actionability	It provides concrete, copy-pasteable commands for install, login, connection ensure, action list/run, and proxy requests, plus a table of real action keys, but examples rely on unresolved placeholders (CONNECTION_ID, <actionId>, <id>) with no end-to-end worked example, leaving minor gaps.	4 / 5
Workflow Clarity	The connection workflow is well sequenced with explicit state checkpoints and a feedback loop (poll after CLIENT_ACTION_REQUIRED), but there is no validation guidance for the destructive operations it surfaces (cancel-deployment, delete-project), which is a minor validation gap.	4 / 5
Progressive Disclosure	The single SKILL.md is well organized with clear section headers and no nested references, and there are no bundle files; the 20-row popular-actions table could arguably live in a separate reference, which is a minor organization gap keeping it at 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

62%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.

The description cleanly answers both what and when and is clearly Vercel-scoped, but it leans on one generic verb ("Manage") and a somewhat abstract trigger phrase rather than concrete actions and natural user terms.

Suggestions

Replace the generic "Manage" with specific verbs, e.g. "Create, list, update, and delete Projects, Deployments, Domains, Teams, Users, and Secrets".

Make the trigger phrase more natural and concrete, e.g. "Use when the user wants to deploy to Vercel or manage their Vercel projects, deployments, domains, teams, or environment secrets".

Add Deployments and Domains to the resource list, as these are among the most common Vercel interactions users will name.

Dimension	Reasoning	Score
Specificity	Names the Vercel domain and several concrete resources ("Manage Projects, Users, Teams, Secrets"), but the single generic verb "Manage" carries all of them rather than listing distinct specific actions, so it is not comprehensive enough for a 4.	3 / 5
Completeness	It states a clear "what" ("Manage Projects, Users, Teams, Secrets") and an explicit "when" ("Use when the user wants to interact with Vercel data"), but the when-clause could be more concrete with specific trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	"Vercel" plus resource names give some relevant keywords, but the trigger phrase "interact with Vercel data" is generic and omits common natural terms users would actually say (deployments, domains, deploys).	3 / 5
Distinctiveness Conflict Risk	"Vercel integration" with Vercel-specific resource names carves a clear, mostly distinct niche with minimal conflict risk, but the broad "interact with Vercel data" trigger keeps it just short of the minimal-conflict 5 anchor.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/vercel/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.