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' and 'Triggers on' clauses, and includes both technical and problem-oriented trigger terms. The description is comprehensive yet focused, making it easy for Claude to distinguish this skill from general Next.js or React skills. The inclusion of the diagnostic trigger 'route goes dynamic unexpectedly' is particularly effective for matching real user problems.
| 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 covering multiple scenarios, plus a 'Triggers on...' clause with specific trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say, including both technical terms ('use cache pattern', 'dynamic slots', 'provider island', 'prefetch strategy') and problem-oriented phrases ('route goes dynamic unexpectedly'). Also includes the framework name 'Next.js' and version '16'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on Next.js 16 static-first architecture patterns with mixed static/dynamic rendering. The specificity of 'use cache', 'provider islands', and 'dynamic slots' makes it very unlikely to conflict with general Next.js or React 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 and clear workflow guidance for Next.js 16 static-first architecture. Its main weakness is length — at ~400 lines it packs substantial detail into a single file, and some sections cover concepts Claude would already know (serialization rules, async client component restrictions). Splitting reference-heavy sections into linked files would improve token efficiency and progressive disclosure.
Suggestions
Extract the Cache Components Setup & Mechanics section and RSC Boundary Rules into separate referenced files (e.g., CACHE_MECHANICS.md, RSC_RULES.md) to reduce the main skill's token footprint.
Remove or significantly condense explanations of concepts Claude already knows, such as why async client components are invalid, JSON serialization constraints, and basic Suspense mechanics — a brief reminder with the fix pattern is sufficient.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and code examples, but it's quite long (~400 lines) and includes some sections that explain concepts Claude likely knows (RSC boundary rules, async client components being invalid, serialization constraints). The migration section and some explanatory tables could be tightened. | 2 / 3 |
Actionability | Excellent actionability throughout — fully executable TypeScript/TSX code examples, specific config snippets, concrete before/after migration patterns, and copy-paste ready implementations for every pattern described. The code examples are complete and realistic. | 3 / 3 |
Workflow Clarity | The implementation sequence provides a clear 8-step workflow, the PR acceptance criteria serve as a validation checklist, and the decision trees/matrices guide routing decisions. The common failure modes section acts as a troubleshooting feedback loop with explicit cause→fix pairs. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and logical progression, but it's a monolithic document that could benefit from splitting detailed sections (cache mechanics, RSC boundary rules, migration guide) into separate referenced files. No external file references are used despite the document's substantial length. | 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
ce9ca8e
- 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.