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 reasonably specific about capabilities and clearly scoped to Vercel automation via a particular MCP integration, making it distinctive. However, it lacks an explicit 'Use when...' clause, and some trigger terms could be more natural and varied to match how users would phrase requests.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Vercel deployments, domain management, DNS records, environment variables, or project/team configuration.'
Include common natural-language variations of trigger terms such as 'deploy', 'environment variables', 'hosting', 'domain setup', and 'DNS records' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: manage deployments, domains, DNS, env vars, projects, and teams. Also includes a procedural instruction ('Always 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, capping this at 2. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Vercel', 'deployments', 'domains', 'DNS', 'env vars', 'projects', and 'teams', but misses common user variations (e.g., 'deploy', 'environment variables', 'hosting', 'domain configuration'). 'Rube MCP (Composio)' is technical jargon unlikely to be used by most users. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Vercel' and 'Rube MCP (Composio)' creates a very clear niche. It is unlikely to conflict with other skills due to the specific platform and tooling references. | 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 well-organized workflow sections and useful pitfall callouts. Its main weaknesses are redundancy between sections (pitfalls repeated, quick reference duplicating workflows), lack of concrete executable examples showing actual MCP tool calls with sample inputs/outputs, and missing validation/verification steps for destructive operations.
Suggestions
Add concrete MCP call examples with sample input parameters and expected response snippets for at least the most common workflows (e.g., listing deployments, adding an env var).
Add explicit validation checkpoints before destructive operations (e.g., 'Verify the env var ID by listing first before deleting' or 'Confirm domain ownership before modifying DNS records').
Consolidate the per-workflow pitfalls and the 'Known Pitfalls' section to eliminate redundancy — either keep pitfalls only in workflows or only in the summary section.
Remove or significantly condense the quick reference table since it largely duplicates information already present in the workflow sections above it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but is quite long (~200 lines) with some redundancy. The 'Known Pitfalls' section repeats information already stated in per-workflow pitfall sections (e.g., secret env vars, deployment states). The quick reference table largely duplicates the workflow sections. Some tightening is possible, but it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides clear tool names, parameter lists, and sequenced steps, which is good. However, there are no executable code examples or concrete MCP call examples with actual input/output. The 'ID Resolution' patterns use pseudocode-style numbered lists rather than concrete call examples. The guidance is specific enough to follow but not copy-paste ready. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with labeled steps and prerequisite/required/optional annotations, which is helpful. 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. Deployment creation mentions polling but doesn't specify a feedback loop for error handling. | 2 / 3 |
Progressive Disclosure | The content is organized into logical sections with a clear hierarchy, but it's a monolithic document with no references to supporting files. The quick reference table, detailed pitfalls, and all six workflow sections are all inline. The domain/DNS, env var, and deployment sections could be split into separate reference files to keep the main skill leaner. However, with no bundle files provided, this is somewhat expected. | 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
d065ead
- 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.