Content
78%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 highly actionable, well-sectioned reference: every section gives exact executable syntax for the Next.js 16 cache APIs, and the migration guidance with before/after code is exemplary. The main weaknesses are the fully inlined ~400-line body with no progressive disclosure into reference files, plus a redundant recap example that inflates token cost.
Suggestions
Split bulk material into one-level-deep reference files (e.g. references/migration.md for the unstable_cache walkthrough and config table, references/api.md for cache profiles and invalidation details), keeping SKILL.md as a concise overview with clearly signaled links.
Remove or shrink the "## Complete Example" section — it recombines patterns already demonstrated (static shell + cached Stats + dynamic Suspense Notifications) and adds ~40 lines of token cost with little new information.
Consolidate the three "use cache Directive" subsections (file/component/function level) into a single example with a one-line note that the directive applies at all three scopes, trimming repeated boilerplate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Code-dominant with tight prose ("Cache Components enable Partial Prerendering (PPR) - mix static, cached, and dynamic content in a single route") and no padding explaining concepts Claude already knows. Minor trimmable redundancy: the "## Complete Example" section largely recombines patterns already shown, keeping it just below the lean anchor 5. | 4 / 5 |
Actionability | Copy-paste-ready exact syntax throughout: the `cacheComponents: true` config block, `'use cache'` + `cacheLife('hours')`/`cacheTag('products')` usage, `updateTag` vs `revalidateTag(tag, "max")` distinction, and a full before/after `unstable_cache` migration pair with a config-mapping table. Covers the common cases completely; placeholders like `db` are app-specific stand-ins, not pseudocode. | 5 / 5 |
Workflow Clarity | The enable → categorize content → apply `use cache` → invalidate → migrate flow is clearly sequenced by section order, with explicit wrong/correct contrasts ("Wrong - runtime API inside use cache" vs "Correct - extract outside, pass as argument") and a migration table. Not anchor 5 because no explicit validation checkpoints exist, though no destructive or batch operations require them. | 4 / 5 |
Progressive Disclosure | Good internal structure with clear section headers, but the skill is ~400 lines in a single file with no reference files at all — migration walkthroughs, cache-profile API detail, and the complete example are inlined where a doc this size would benefit from one-level-deep references (e.g. MIGRATION.md, API.md). Matches the anchor for good structure with content that should be separate kept inline. | 3 / 5 |
Total | 16 / 20 Passed |