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.
76
65%
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 does a good job listing specific Vercel-related capabilities and is clearly scoped to a distinct niche (Vercel via Rube MCP/Composio). However, it lacks an explicit 'Use when...' clause, which caps completeness, 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, hosting, domain configuration, or environment variable management.'
Include more natural user-facing trigger terms like 'deploy', 'environment variables', 'hosting', 'site configuration', and '.vercel' 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 mention. | 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 'Composio'. The term 'Rube MCP' is technical jargon that users wouldn't naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Very clearly scoped to Vercel tasks via a specific integration (Rube MCP / Composio), making 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 clear workflow sequences and useful pitfall documentation for Vercel automation. Its main weaknesses are the lack of concrete executable examples (actual MCP call syntax with parameters) and significant content redundancy between workflow sections, the Known Pitfalls section, and the quick reference table. The monolithic structure would benefit from progressive disclosure via external reference files.
Suggestions
Add at least one concrete, executable MCP call example showing the actual parameter format (e.g., a complete RUBE_SEARCH_TOOLS call and a VERCEL_LIST_PROJECTS call with real parameter structure and expected response shape).
Consolidate the Known Pitfalls section into the relevant workflow sections to eliminate duplication (e.g., env var secrets info appears twice).
Move the detailed workflow sections (2-6) into a separate WORKFLOWS.md file and keep SKILL.md as a concise overview with the setup, workflow 1 as an example, and the quick reference table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but quite long (~200 lines). The quick reference table at the end duplicates information already covered in the workflow sections. Some pitfalls sections repeat information (e.g., env var secrets mentioned in both workflow 3 and Known Pitfalls). The content could be tightened by removing redundancy. | 2 / 3 |
Actionability | Tool sequences are clearly named and ordered, and key parameters are listed, but there are no executable code/command examples showing actual MCP calls with real parameter structures. The 'ID Resolution' patterns use pseudocode-style numbered lists rather than concrete call examples with expected input/output shapes. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with labeled steps (Required/Optional/Prerequisite), explicit tool ordering, and pitfalls sections that serve as validation guidance. The setup section has a clear prerequisite verification flow. Deployment creation correctly notes the need to poll for status. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to external files for detailed information. The quick reference table helps navigation, but the 6 workflow sections plus common patterns plus known pitfalls could benefit from being split into separate referenced documents, keeping SKILL.md as a concise overview. | 2 / 3 |
Total | 9 / 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
7cc63f3
- 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.