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.
72
58%
Does it follow best practices?
Impact
100%
1.88xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/vercel-automation/SKILL.mdQuality
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 is strong on specificity and distinctiveness, clearly enumerating Vercel-related capabilities and naming the specific integration. However, it lacks an explicit 'Use when...' clause, which caps completeness, and the trigger terms could be more natural and comprehensive for user-facing queries.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Vercel deployments, hosting, domain configuration, or environment variable management.'
Include more natural user-facing trigger terms like 'deploy', 'hosting', 'environment variables', 'Vercel project settings' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: manage deployments, domains, DNS, env vars, projects, and teams. Also includes the operational instruction to search tools first for current schemas. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (automate Vercel tasks via Rube MCP), but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the domain keywords. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Vercel', 'deployments', 'domains', 'DNS', 'env vars', 'projects', and 'teams', but misses common user variations like 'deploy', 'environment variables', 'hosting', or 'Vercel API'. The mention of 'Rube MCP (Composio)' is technical jargon users wouldn't naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Very clearly scoped to Vercel tasks via a specific MCP integration (Rube/Composio). The combination of platform (Vercel) and tooling (Rube MCP) makes it highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive reference for Vercel automation via Rube MCP with good structural organization and useful pitfall documentation. Its main weaknesses are verbosity with duplicated information, lack of concrete executable examples showing actual MCP tool calls, and missing validation checkpoints in workflows involving destructive operations. The content would benefit from being more concise and including at least one end-to-end example with actual call syntax.
Suggestions
Add at least one concrete, end-to-end example showing actual MCP tool call syntax with input parameters and expected response structure (e.g., a complete 'deploy and verify' workflow).
Remove duplicated information — deployment states and secret env var behavior are each mentioned twice. Consolidate pitfalls into the 'Known Pitfalls' section and remove from individual workflows.
Add explicit validation/verification steps to destructive workflows (e.g., 'List env vars to confirm the target exists before deleting', 'Verify DNS record was created by re-listing records').
Consider splitting the detailed per-workflow parameter lists and pitfalls into a separate REFERENCE.md file, keeping SKILL.md as a leaner overview with the quick reference table and setup instructions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but quite verbose for what it conveys. There's significant repetition (e.g., pitfalls about secret env vars appear twice, deployment states are listed twice). The tool slug alternatives (e.g., 'VERCEL_LIST_ALL_DEPLOYMENTS or VERCEL_GET_DEPLOYMENTS') add ambiguity rather than clarity. The quick reference table at the end largely duplicates the workflow sections above it. | 2 / 3 |
Actionability | The skill provides clear tool sequences and parameter lists, which is good. However, there are no executable code examples or concrete MCP call examples with actual input/output. The 'Common Patterns' section uses pseudocode-style numbered lists rather than concrete call examples. Claude would benefit from seeing an actual RUBE_SEARCH_TOOLS call with expected response format. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with labeled steps and prerequisite markers, which is good. However, there are no explicit validation checkpoints or error recovery loops. For destructive operations like deleting env vars or DNS records, there's no 'verify before proceeding' step. The setup section has a good verification flow, but the core workflows lack similar validation gates. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a logical progression from setup to workflows to reference. However, with no bundle files, all content is monolithic in a single file. The document is quite long (~200+ lines) and the detailed parameter lists and pitfalls for each workflow could be split into separate reference files. The external link to Composio docs is helpful but insufficient for progressive disclosure. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%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 | |
- Repository
- davepoon/buildwithclaude
- Commit
c911a92
- 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.