Content
92%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 well-engineered overview skill: lean operational guidance with exact commands, an explicit pre-mutation validation workflow with stop conditions, and a clean decision-tree routing to 27 real one-level-deep reference files. The only notable improvement is consolidating the duplicated linking guidance between the Project Linking section and the Anti-Patterns list.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and operational throughout — stdout/stderr parsing rules, non-interactive JSON error protocol, linking semantics — with zero explanation of concepts Claude already knows. However, the "Critical: Project Linking" section and the "Anti-Patterns" section repeat the same points (wrong link type in monorepos, commands auto-linking, `whoami` not verifying the linked project), which is a minor trim opportunity. Anchor 4 ("efficient; minor instances ... that could be trimmed") fits better than 5 because of that deliberate but real duplication. | 4 / 5 |
Actionability | Every directive is paired with an exact, executable command or flag: `vercel project inspect --non-interactive`, `vercel whoami --format json`, `vercel link --repo`, `npm i -g vercel`, `vercel deploy --force` without `--with-cache`, `vercel curl`, `VERCEL_TOKEN`. The Quick Start is copy-paste ready and each anti-pattern names its corrective command, covering the common cases as in the anchor-5 example. Not 4 — there are no missing steps or gaps in the guidance the body chooses to give. | 5 / 5 |
Workflow Clarity | The Quick Start is a clear install → login → link → pull → dev → deploy sequence, and the body mandates an explicit pre-mutation validation checkpoint ("run `vercel project inspect --non-interactive` ... and confirm the reported owner and project") with stop conditions ("stop on `link_required` or a target mismatch") and error-recovery guidance via the JSON `status`/`reason`/`hint`/`next` protocol with safety constraints on follow-up commands. This matches anchor 5's explicit validation steps plus feedback loops; the destructive/batch cap does not apply because validation before consequential operations is explicitly required. | 5 / 5 |
Progressive Disclosure | The body is a true overview: a small amount of critical operating guidance, a Quick Start, and a well-signaled Decision Tree routing each topic to a verified, one-level-deep `references/*.md` file (all 27 referenced files exist in the bundle, and reference files only cross-link to siblings at the same level, never nesting 2+ levels). Content is appropriately split with easy navigation, matching anchor 5; anchor 4's "minor organization gaps" does not apply. | 5 / 5 |
Total | 19 / 20 Passed |