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 thorough without being padded, and the inclusion of problem-oriented triggers like 'route goes dynamic unexpectedly' demonstrates thoughtful consideration of how users would actually invoke this skill.
| 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 listing 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 framework-specific context ('Next.js 16') and common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on Next.js 16 static-first architecture patterns with mixed static/dynamic rendering. The combination of framework version, specific patterns (cached shells, provider islands, 'use cache'), and problem triggers ('route goes dynamic unexpectedly') makes 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, deeply actionable skill with excellent executable examples, clear workflow sequencing, and comprehensive coverage of Next.js 16 static-first patterns. Its main weakness is length — it tries to be both a quick-reference guide and a comprehensive manual in one file, which hurts conciseness and progressive disclosure. Some sections covering general RSC knowledge (async client components, serialization rules) could be trimmed or externalized.
Suggestions
Extract detailed subsections (cache mechanics, RSC boundary rules, migration guide) into separate reference files and link to them from the main skill to improve progressive disclosure and reduce token cost.
Trim sections that explain general React/RSC concepts Claude already knows (e.g., 'Client components cannot be async', serialization constraints) to brief reminders or remove them entirely.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive and mostly efficient, but some sections explain concepts Claude likely knows (RSC boundary rules, async client components being invalid, serialization constraints) and the document is quite long (~400 lines). Some tables and explanations could be tightened, though most content earns its place with Next.js 16-specific details. | 2 / 3 |
Actionability | Excellent actionability throughout — every pattern includes complete, executable TypeScript/TSX code examples, specific config snippets, concrete migration paths with before/after code, and a clear implementation sequence. The code is copy-paste ready and covers both correct and incorrect patterns. | 3 / 3 |
Workflow Clarity | The implementation sequence is clearly numbered, the decision trees and matrices provide unambiguous routing for different scenarios, and the PR acceptance criteria serve as a validation checklist. The common failure modes section provides explicit fix steps. The entry→static→slot pattern is well-sequenced with clear boundaries. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and logical progression, but it's a monolithic document (~400+ lines) with no references to external files for detailed subtopics. The cache mechanics, RSC boundary rules, and migration sections could be split into separate reference files to keep the main skill leaner. | 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
825972c
- 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.