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.

Install with Tessl CLI

npx tessl i github:davepoon/buildwithclaude --skill vercel-automation

What are skills?

1.88x

Quality

65%

Does it follow best practices?

Impact

100%

1.88x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/vercel-automation/SKILL.md

SKILL.md

Review

Evals

Discovery

67%

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 effectively communicates specific Vercel automation capabilities and is highly distinctive due to the platform-specific focus. However, it lacks an explicit 'Use when...' clause and relies on some technical jargon (Rube MCP, Composio) that users wouldn't naturally use as trigger terms.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Vercel deployments, hosting, or managing Vercel projects.'

Include more natural user trigger terms like 'deploy', 'hosting', 'environment variables', 'deploy to production', or 'Vercel settings'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'manage deployments, domains, DNS, env vars, projects, and teams' - these are distinct, actionable capabilities within the Vercel domain.	3 / 3
Completeness	Clearly answers 'what' (automate Vercel tasks, manage various resources) but lacks an explicit 'Use when...' clause. The 'when' is only implied by the domain mention, not explicitly stated.	2 / 3
Trigger Term Quality	Includes relevant keywords like 'Vercel', 'deployments', 'domains', 'DNS', 'env vars' but missing common user variations like 'deploy', 'environment variables', 'hosting', or file extensions. 'Rube MCP (Composio)' is technical jargon users wouldn't naturally say.	2 / 3
Distinctiveness Conflict Risk	Very clear niche targeting Vercel specifically via Rube MCP/Composio. The combination of platform (Vercel) and integration method (Rube MCP) makes it highly distinctive and unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Implementation

62%

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

This is a well-structured skill with excellent workflow clarity, providing clear tool sequences with required/optional markers and comprehensive pitfall documentation. However, it lacks executable code examples (relying on tool names and parameter lists instead), and the document is lengthy enough that some content could be split into separate reference files for better progressive disclosure.

Suggestions

Add concrete executable examples showing actual tool calls with sample input parameters and expected response structures, particularly for common operations like listing deployments or adding environment variables.

Consider splitting the detailed workflow sections (Deployments, Environment Variables, Domains, etc.) into separate reference files, keeping only quick-start summaries in the main SKILL.md.

Remove the Quick Reference table or move it to a separate REFERENCE.md file, as it largely duplicates information already present in the workflow sections.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundancy - the Quick Reference table duplicates information already covered in the Core Workflows sections. The pitfalls and patterns sections add value but could be more condensed.	2 / 3
Actionability	Provides clear tool sequences and parameter lists, but lacks executable code examples. The ID Resolution patterns use pseudocode-style numbered steps rather than actual API call examples with sample responses.	2 / 3
Workflow Clarity	Excellent workflow structure with clear numbered sequences, explicit [Required]/[Optional] markers, prerequisite steps, and detailed pitfalls for each workflow. The deployment state documentation and validation guidance is thorough.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but the document is quite long (200+ lines) and could benefit from splitting detailed workflow sections into separate files. The Quick Reference table at the end is helpful but the overall structure is somewhat monolithic.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

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