Content
65%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.
An excellent, dense API reference with fully executable examples, accurate cross-system distinctions, and concrete limits — its main weaknesses are the lack of pre-purge validation for destructive operations, marketing/date padding in the Observability section, and a monolithic single-file structure instead of split reference files.
Suggestions
Move the CLI Cache Commands, Next.js Integration, and CDN Cache Tags sections into separate reference files (e.g. cli.md, nextjs.md), keeping SKILL.md as a lean overview with clearly signaled one-level-deep links.
Add a validation step before destructive or batch purge operations — e.g. verify the affected tags against the limits table (16 tags per bulk REST call, 64 per item) and confirm the target scope before running `vercel cache purge` or `dangerouslyDeleteByTag`.
Trim the Observability section's dashboard release details and remove or relocate the "(March 5, 2026)" dated release information to a changelog reference, keeping only what is needed to monitor hit rates and storage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly a tight, non-obvious API reference with no explanation of concepts Claude already knows, but the Observability section pads with dashboard release marketing ("redesigned purging interface", "available on all plans and take effect instantly") and includes the time-sensitive date "(March 5, 2026)" outside any deprecated/old-patterns section, fitting anchor 3 rather than 4. | 3 / 5 |
Actionability | Fully executable, copy-paste-ready guidance throughout: complete getCache/set/get/delete/expireTag snippets, a full fetch-handler caching example, a server action, concrete CLI commands with flags (e.g. "vercel cache dangerously-delete --tag blog-posts --revalidation-deadline-seconds 3600"), and a limits table — matching anchor 5. | 5 / 5 |
Workflow Clarity | "When to Use" / "When NOT to Use" provide clear decision guidance and distinctions (e.g. "cache.expireTag() — operates on Runtime Cache only"), but destructive and batch operations ("vercel cache purge", "dangerouslyDeleteByTag") have no validation or verification steps before execution, so workflow clarity is capped at 3 per the rubric guideline. | 3 / 5 |
Progressive Disclosure | Section headers are clear, but this is a ~230-line monolith with no bundle files at all: CLI command reference, Next.js integration, and CDN cache tag sections are inlined content that belongs in separate reference files, matching anchor 3 ("content that should be separate is inline") rather than 4. | 3 / 5 |
Total | 14 / 20 Passed |