CtrlK
BlogDocsLog inGet started
Tessl Logo

vercel-deployment

Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.

40

Quality

40%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/vercel-deployment/SKILL.md

The canonical home for this skill is vercel-deployment in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

22%Scale 1-5

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

This skill is essentially a skeleton or outline with no substantive content. While it identifies relevant topics for Vercel deployment (environment variables, edge vs serverless, build optimization), it provides zero executable guidance, no code examples, no concrete commands, and no actual deployment workflow. The Sharp Edges table lists important issues but truncates every solution, making it useless in practice.

Suggestions

Add concrete, executable code examples for each Pattern section — e.g., show actual vercel.json configuration, environment variable setup commands (`vercel env add`), and edge runtime route examples with `export const runtime = 'edge'`.

Complete the Sharp Edges solutions column with actual code snippets — e.g., show a proper CORS middleware implementation, a revalidation example, and a correct NEXT_PUBLIC_ vs server-side env var usage pattern.

Add a deployment workflow with explicit steps: 1) Configure env vars, 2) Set up vercel.json, 3) Run `vercel --prod`, 4) Verify deployment with health check, 5) Validate environment variables are loaded correctly.

Remove the 'Capabilities', 'Requirements', and 'When to Use This Skill' sections which duplicate frontmatter metadata and add no actionable value to the body content.

DimensionReasoningScore

Conciseness

The skill has some unnecessary sections like 'When to Use This Skill' that largely repeats the frontmatter description, and 'Capabilities'/'Requirements' sections that belong in metadata rather than body content. However, the sharp edges table and anti-patterns are reasonably concise. The 'core principles' list is somewhat generic but not egregiously verbose.

3 / 5

Actionability

The skill is almost entirely vague and abstract. The Patterns section lists topics ('Environment Variables Setup', 'Edge vs Serverless Functions') with no actual code, commands, or concrete guidance. The Sharp Edges table lists problems and promises solutions but the 'Solution' column contains incomplete fragments with no executable examples. There is zero copy-paste ready code anywhere in the skill.

1 / 5

Workflow Clarity

There is no workflow, no sequenced steps, and no validation checkpoints. Deployment is inherently a multi-step process involving configuration, building, and verification, yet the skill provides no process guidance whatsoever. The Patterns section has headings but no actual steps beneath them.

1 / 5

Progressive Disclosure

The content is structured with clear section headers and a table format for sharp edges, which provides some organization. However, there are no bundle files or external references to detailed content, and the Patterns section appears to be stubs that should either contain inline content or point to separate files. The structure exists but doesn't effectively organize or disclose content.

3 / 5

Total

8

/

20

Passed

Description

57%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 correctly identifies its niche (Vercel + Next.js deployment) and includes an explicit 'Use when' clause with trigger terms, which is good. However, it lacks specificity about what concrete actions or capabilities the skill provides—'expert knowledge' is vague and doesn't tell Claude what this skill actually does. The trigger terms are adequate but could include more natural user phrases.

Suggestions

Replace 'Expert knowledge for deploying' with specific actions like 'Configures Vercel deployments for Next.js apps, sets up environment variables, manages custom domains, and troubleshoots build errors.'

Expand trigger terms to include natural variations like 'ship', 'go live', 'publish', 'vercel.json', 'build errors', 'serverless functions', 'edge functions', 'preview deployments'.

DimensionReasoningScore

Specificity

Names the domain ('deploying to Vercel with Next.js') but provides no concrete actions beyond the vague 'expert knowledge for deploying.' No specific capabilities like configuring environment variables, setting up CI/CD, managing domains, etc. are mentioned.

2 / 5

Completeness

Has both a 'what' (deploying to Vercel with Next.js) and an explicit 'when' clause with trigger terms. However, the 'what' is vague ('expert knowledge') and the 'when' is a simple keyword list rather than describing concrete scenarios.

4 / 5

Trigger Term Quality

Includes relevant keywords like 'vercel', 'deploy', 'deployment', 'hosting', 'production', and 'Next.js', but misses natural variations users might say such as 'ship', 'go live', 'publish', 'CI/CD', 'environment variables', 'domain', or 'serverless'.

3 / 5

Distinctiveness Conflict Risk

Specifying both 'Vercel' and 'Next.js' makes it fairly distinct. There's minor overlap risk with a general Next.js skill or a general deployment skill, but the combination of platform and framework narrows the niche well.

4 / 5

Total

13

/

20

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.