vercel-automation

Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, highly actionable MCP tool reference with clear workflow sequencing, weakened by duplicated content and missing validation checkpoints on destructive operations, all in a single monolithic file.

Suggestions

Add explicit verify-after-step checkpoints for destructive/batch operations (e.g., re-list env vars or DNS records after a delete/update to confirm the change took effect).

Remove or trim the Quick Reference table since it duplicates the per-workflow tool listings, or move it to a separate reference file.

Split the large API reference (Quick Reference + per-domain workflows) into a separate reference file and keep SKILL.md as a concise overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is a dense, mostly lean API reference that assumes Claude's competence, but the Quick Reference table largely duplicates the per-workflow tool listings, so it could be tightened.	2 / 3
Actionability	It provides exact tool slugs and concrete parameter enums (e.g., target 'production'/'preview', DNS 'A'/'CNAME'/'MX'), giving copy-ready actionable guidance for an MCP-tool skill.	3 / 3
Workflow Clarity	Workflows are clearly sequenced with [Required]/[Optional]/[Prerequisite] markers and setup validation, but destructive operations (delete env var, update/delete DNS) lack explicit verification checkpoints, capping the score.	2 / 3
Progressive Disclosure	The skill is a single ~230-line monolithic file with well-organized sections but no bundle files or one-level-deep references to split out the API reference material.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 specific, well-scoped description with strong trigger terms and a clear Vercel niche, but it lacks an explicit 'Use when…' trigger clause, which caps completeness.

Suggestions

Add an explicit 'Use when…' clause naming the user situations that should activate this skill (e.g., 'Use when the user wants to manage Vercel deployments, domains, env vars, or teams').

Mirror a few more natural phrasings users might say (e.g., 'Vercel project settings', 'Vercel DNS records') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete capability domains — 'manage deployments, domains, DNS, env vars, projects, and teams' — matching the anchor for several specific concrete actions.	3 / 3
Completeness	It clearly states what the skill does but provides no 'Use when…' clause or equivalent explicit trigger guidance, capping completeness per the judging guidelines.	2 / 3
Trigger Term Quality	It surfaces natural user vocabulary ('Vercel', 'deployments', 'domains', 'DNS', 'env vars', 'projects', 'teams') that a user would actually say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	It is tightly scoped to Vercel via Rube MCP (Composio), a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 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: davepoon/buildwithclaude
Commit: 366e45b

Reviewed: about 23 hours 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.