Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A dense, highly actionable reference with executable commands, complete CI pipelines for three providers, and useful decision guidance (promote vs deploy --prebuilt, OIDC scope). Its main weaknesses are minor verbosity and the absence of explicit post-deploy verification steps in the primary workflow.
Suggestions
Add an explicit verification checkpoint to the basic deploy flow (e.g. after 'vercel deploy', check deployment status is READY via 'vercel inspect <url>' before reporting success), which would also strengthen the rollback recovery loop.
Trim background prose Claude already knows, such as 'Preview deployments are created automatically for every push to a non-production branch... They provide a unique URL for testing', keeping only Vercel-specific behavior notes.
Consider moving the per-provider CI pipeline examples or the build-error table into a reference file to keep SKILL.md as a lean overview, since the body currently inlines all detail.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is command-first with annotated code blocks and mostly non-obvious guidance (e.g. 'promote is instant — it re-points the production alias without rebuilding'), but a few known-info asides like 'Preview deployments are created automatically for every push... They provide a unique URL for testing' could be trimmed. | 4 / 5 |
Actionability | Fully executable copy-paste-ready commands ('vercel deploy --prebuilt --prod --token=...') and complete CI YAML for GitHub Actions, GitLab, and Bitbucket, plus a concrete error-to-fix table covering cases like 'ERR_PNPM_OUTDATED_LOCKFILE ... Run pnpm install, commit lockfile'. | 5 / 5 |
Workflow Clarity | The pull → build → deploy --prebuilt sequence is shown per-provider, and the promote pattern gates on e2e tests via job dependencies ('needs: [deploy-preview, e2e-tests]'), but the basic deploy flow lacks an explicit post-deploy verification step and rollback is not tied into a recovery loop. | 4 / 5 |
Progressive Disclosure | No bundle files exist and the body is well-sectioned with clear headers and navigation, but content that could live in separate reference files (three full provider pipelines, the build-error table) is inlined, leaving minor organization gaps. | 4 / 5 |
Total | 17 / 20 Passed |