vercel-debug

Investigate Vercel deployment errors using Vercel CLI. Use when user shares a Vercel deployment error, build failure, or deployment URL that needs debugging.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

87%

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-crafted debugging skill that is concise, actionable, and appropriately scoped. The workflow progresses logically from authentication through log inspection. The main gap is the lack of a verification step after applying fixes from the common errors table.

Suggestions

Add a step 6 for verification: after applying a fix, re-run `vercel inspect` or trigger a new deployment to confirm the issue is resolved

Dimension	Reasoning	Score
Conciseness	Every line serves a purpose. No explanation of what Vercel is or how deployments work. Commands are direct with minimal commentary.	3 / 3
Actionability	All commands are copy-paste ready with proper flags and placeholders. The common errors table provides specific fixes, not vague suggestions.	3 / 3
Workflow Clarity	Steps are clearly sequenced for the debugging workflow, but lacks explicit validation checkpoints or feedback loops for error recovery after applying fixes.	2 / 3
Progressive Disclosure	For a focused debugging skill under 50 lines, the content is well-organized with clear sections. No need for external references given the scope.	3 / 3
	Total	11 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-structured skill description with strong trigger terms and clear 'Use when' guidance that makes it easy for Claude to select appropriately. The main weakness is the lack of specific concrete actions beyond the general 'Investigate' verb, which could be expanded to better communicate the skill's full capabilities.

Suggestions

Expand the capabilities section with specific actions like 'analyze build logs, check deployment configuration, inspect environment variables, review function errors'

Dimension	Reasoning	Score
Specificity	Names the domain (Vercel deployment errors) and the tool (Vercel CLI), but only describes one general action 'Investigate' rather than listing multiple specific concrete actions like 'analyze build logs, check environment variables, inspect deployment configuration'.	2 / 3
Completeness	Clearly answers both what ('Investigate Vercel deployment errors using Vercel CLI') and when ('Use when user shares a Vercel deployment error, build failure, or deployment URL that needs debugging') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'Vercel deployment error', 'build failure', 'deployment URL', 'debugging'. These are terms users naturally use when encountering Vercel issues.	3 / 3
Distinctiveness Conflict Risk	Very specific niche targeting Vercel-specific deployment issues. The combination of 'Vercel', 'deployment errors', 'build failure', and 'Vercel CLI' creates distinct triggers unlikely to conflict with general debugging or other deployment platform skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: yahsan2/static-admin
Commit: f734087

Reviewed: 5 months ago

Table of Contents

Discovery Implementation Validation

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.