nextjs-static-shells
Static-first Next.js 16 architecture patterns: cached shells with dynamic slots, provider islands, 'use cache' boundaries, and link preloading strategy. Use when building or refactoring Next.js routes to maximize static rendering, implementing 'use cache' with dynamic personalization, splitting entry vs static renderers, scoping client providers, or tuning prefetch behavior. Triggers on 'static shell', 'use cache pattern', 'dynamic slots', 'provider island', 'prefetch strategy', 'static first', 'cache boundary', 'route goes dynamic unexpectedly', or any Next.js architecture work involving mixed static/dynamic rendering.
90
88%
Does it follow best practices?
Impact
98%
1.24xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines a specific niche (Next.js 16 static-first architecture), lists concrete capabilities, provides explicit 'Use when' guidance with multiple scenarios, and includes a comprehensive set of natural trigger terms. The description is well-structured with what/when/triggers sections and covers both technical patterns and user problem statements like 'route goes dynamic unexpectedly'. It uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and patterns: cached shells with dynamic slots, provider islands, 'use cache' boundaries, link preloading strategy, splitting entry vs static renderers, scoping client providers, and tuning prefetch behavior. | 3 / 3 |
Completeness | Clearly answers both 'what' (static-first Next.js 16 architecture patterns with specific techniques listed) and 'when' (explicit 'Use when...' clause with multiple scenarios, plus a 'Triggers on...' clause with specific keywords). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'static shell', 'use cache pattern', 'dynamic slots', 'provider island', 'prefetch strategy', 'route goes dynamic unexpectedly', and broader terms like 'Next.js architecture work involving mixed static/dynamic rendering'. These cover both specific jargon and natural problem descriptions. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on Next.js 16 static-first architecture patterns with 'use cache' boundaries and dynamic slots. The specificity of the framework version, the particular patterns (provider islands, cached shells), and problem-oriented triggers like 'route goes dynamic unexpectedly' make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, highly actionable skill with excellent executable examples, clear architectural patterns, and strong workflow guidance including failure modes and a PR checklist. Its main weakness is length — at ~400 lines it packs substantial reference material (cache API details, RSC rules, migration tables) that could be split into supporting files for better progressive disclosure. Some sections explain concepts Claude likely already knows (serialization rules, async client component restrictions).
Suggestions
Extract the Cache Components Setup & Mechanics section and RSC Boundary Rules into separate reference files (e.g., CACHE_API.md, RSC_RULES.md) and link from the main skill to reduce monolithic length.
Remove or significantly condense the RSC boundary rules section (async client components, non-serializable props) — Claude already knows these constraints and they're not specific to the static-first pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and code examples, but includes some sections Claude already knows well (RSC boundary rules, async client components being invalid, serialization constraints) and could be tightened. The 'Why This Works' bullet list and some explanatory text add modest bloat. | 2 / 3 |
Actionability | Excellent actionability throughout — fully executable code examples for every pattern, concrete config snippets, specific migration paths with before/after code, and a clear implementation sequence. The PR acceptance criteria checklist is directly usable. | 3 / 3 |
Workflow Clarity | The implementation sequence provides a clear ordered workflow. The decision trees, decision matrix, and common failure modes with fixes create effective feedback loops. The PR acceptance criteria serve as a validation checklist. The entry→static→slot pattern is explicitly sequenced with clear boundaries. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but it's a monolithic ~400-line document with no references to supporting files. Several sections (cache mechanics, RSC boundary rules, migration guide) could be split into separate reference files to keep the main skill leaner. No bundle files exist to offload detail. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (592 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- joelhooks/joelclaw
- Commit
03f0a59
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.