Content
88%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.
The content is a strong, actionable runbook: concrete commands for every branch, an explicit decision tree, approval gating on the destructive push, and error-recovery guidance. Its only notable gaps are mild verbosity from duplicated environment-specific fallback sections and the absence of any split reference files for the longer peripheral material.
Suggestions
Consolidate the two near-identical no-auth fallback sections (claude.ai and Codex) into one parameterized section to reduce repetition and token cost.
Consider moving the Troubleshooting and Agent-Specific Notes into a separate reference file referenced from SKILL.md to improve progressive disclosure now that the body is long.
Tighten the repeated explanations of `vercel link` vs `vercel link --repo` so the rationale appears once rather than being restated across steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean commands and decision logic with no padding about concepts Claude already knows, though the two parallel no-auth fallback sections (claude.ai vs Codex) and some repeated linking explanations could be trimmed slightly. | 4 / 5 |
Actionability | It provides copy-paste-ready, executable bash commands for every path (git remote check, `vercel deploy -y --no-wait`, `vercel inspect <url>`, `vercel link --repo --scope`) covering the common cases with concrete examples. | 5 / 5 |
Workflow Clarity | The flow is clearly sequenced (gather state -> choose method by explicit conditions) with a validation checkpoint on the destructive git push ("Ask the user before pushing. Never push without explicit approval"), status verification via `vercel inspect`, and a troubleshooting section providing error-recovery feedback loops. | 5 / 5 |
Progressive Disclosure | No bundle files exist, so all content lives inline, but it is well-organized into clearly signaled sections (Step 1/2, Agent-Specific Notes, Output, Troubleshooting); the length and the inline troubleshooting/agent-notes material that could arguably be split keep it just below the top anchor. | 4 / 5 |
Total | 18 / 20 Passed |