CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

58

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/vercel-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

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

The content is well-structured and actionable, with concrete tool sequences and parameters for each Vercel workflow. Its main weaknesses are redundancy between the detailed sections and the Quick Reference, and missing validation checkpoints for destructive operations.

Suggestions

Add explicit validation/verification checkpoints to destructive workflows (e.g., confirm env var deletion by re-listing, verify DNS record propagation after create/update, confirm deployment READY before declaring success).

Remove the duplicate Quick Reference table or trim the per-workflow parameter lists to a single source of truth to reduce token redundancy.

Move duplicated pitfall content into one section (or the relevant workflow) rather than restating it in both per-workflow 'Pitfalls' and 'Known Pitfalls'.

DimensionReasoningScore

Conciseness

Mostly efficient reference style, but the Quick Reference table fully restates every workflow's tools and params already detailed above, and the 'Known Pitfalls' section duplicates the per-workflow 'Pitfalls' blocks, creating notable redundancy.

3 / 5

Actionability

Provides concrete tool names, specific parameters, and explicit numbered tool sequences per workflow; guidance is executable for an MCP-orchestration skill with only minor gaps (e.g., no example payload shapes).

4 / 5

Workflow Clarity

Each workflow has a clear numbered sequence, but destructive/batch operations (delete env var, create/update/delete DNS records, create deployments) lack explicit validation or verification checkpoints beyond polling GET_DEPLOYMENT, capping clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

Well-organized with clear section headers and a navigation table in a single appropriately-sized file; no bundle files exist so there is nothing to split out, though an external reference for the full tool catalog could tighten the body further.

4 / 5

Total

14

/

20

Passed

Description

75%Weight 40%Scale 1-5

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 specific and distinctive, clearly scoping Vercel platform automation, but it lacks an explicit trigger clause telling Claude when to invoke it. Adding a 'Use when…' phrase would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when…' trigger clause (e.g., 'Use when the user wants to manage Vercel deployments, domains, DNS, env vars, projects, or teams').

Include a couple of common synonyms or natural phrasings users might say (e.g., 'Vercel hosting', 'preview deployments', 'custom domains').

Drop or relocate the operational instruction 'Always search tools first for current schemas' from the description into the body prerequisites, since it is not a trigger.

DimensionReasoningScore

Specificity

Names the domain and lists six concrete action areas ('manage deployments, domains, DNS, env vars, projects, and teams'), giving comprehensive coverage of Vercel platform operations.

5 / 5

Completeness

Has a clear 'what' but the closing clause ('Always search tools first for current schemas') is a behavioral instruction, not a 'when to use' trigger; per the rubric a missing 'Use when…' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes good natural terms (deployments, domains, DNS, env vars, projects, teams) but lacks 'Use when…' trigger phrasing and common synonyms, sitting just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Scoped specifically to Vercel operations via Rube MCP (Composio), creating a distinct niche with minimal overlap risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
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.