vercel-services

Vercel Services — deploy multiple services within a single Vercel project. Use for monorepo layouts or when combining a backend (Python, Go) with a frontend (Next.js, Vite) in one deployment.

Quality

78%

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 ./plugins/vercel/skills/vercel-services/SKILL.md

Quality

Content

75%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 well-structured, actionable skill body with concrete configuration examples, runtime-specific guidance, and clear references to a real reference bundle. Minor gaps in inline validation gating and a few trimmable asides keep it just below the top level across dimensions.

Suggestions

Make the main Usage workflow's validation explicit with a checkpoint (e.g. 'Validate each service has entrypoint and routePrefix before deploying; if missing, fix vercel.json and re-check') to strengthen the feedback loop.

Trim minor over-explanation such as the parenthetical on the -L flag, or move it to the reference bundle, to push conciseness toward the lean level.

Inline a minimal complete root vercel.json from the reference project (or confirm it is shown via the bundle) so the canonical layout is visible without a separate read for the common case.

Dimension	Reasoning	Score
Conciseness	The body is efficient and mostly assumes Claude's competence, with only minor over-explanation (e.g. 'The -L flag (short for --local) runs without authenticating') that could be trimmed, fitting the efficient anchor rather than the fully lean level.	4 / 5
Actionability	It provides a concrete vercel.json example, a field-by-field config table, and runtime-specific executable instructions (e.g. set entrypoint to a directory for Go, must set 'framework': 'go'), with only minor gaps such as no inline full deploy command.	4 / 5
Workflow Clarity	The Usage section gives a clear numbered sequence including a validate step, and Troubleshooting offers feedback loops (404 -> set Services preset -> redeploy), but the main workflow's validation checkpoint is implicit rather than a hard validate-then-proceed gate.	4 / 5
Progressive Disclosure	The body is a well-sectioned overview that signals one-level-deep references to a real bundle ('references/fastapi-vite/', 'see reference project') and the deployments-cicd skill, with only minor organization gaps keeping it below the top anchor.	4 / 5
	Total	16 / 20 Passed

Description

82%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, concise description that clearly states the capability and gives explicit use-when guidance with concrete, natural trigger terms. Its only weakness is a single core action rather than an enumeration of multiple capabilities.

Dimension	Reasoning	Score
Specificity	The description names the domain and one core concrete action — 'deploy multiple services within a single Vercel project' — but does not list multiple distinct actions, fitting the anchor for naming the domain with 1-2 concrete actions rather than the several-action level above.	3 / 5
Completeness	It explicitly answers both what ('deploy multiple services within a single Vercel project') and when ('Use for monorepo layouts or when combining a backend ... with a frontend ... in one deployment') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	It includes natural terms users would say — 'monorepo layouts', 'backend (Python, Go)', 'frontend (Next.js, Vite)', 'deploy' — giving good keyword coverage, though a few common synonyms are absent so it does not reach the comprehensive level.	4 / 5
Distinctiveness Conflict Risk	'Vercel Services' is a clear niche and the triggers (monorepo, combined backend+frontend in one Vercel deployment) are distinct, giving minimal conflict risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: openai/plugins
Path: plugins/vercel/skills/vercel-services/SKILL.md
Commit: 1e28582

Reviewed: 6 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.