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.

1.24x

Quality

89%

Does it follow best practices?

Impact

98%

1.24x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, highly actionable Next.js 16 static-shell reference with excellent code examples and clear workflows, but it presents as one large monolithic document rather than an overview pointing to one-level-deep reference files, which limits progressive disclosure.

Suggestions

Split the detailed cache mechanics and migration reference into separate files (e.g. CACHE.md, MIGRATION.md) and keep SKILL.md as a concise overview with one-level-deep links, which would lift progressive_disclosure and tighten conciseness.

Trim the repeated 'Why This Works' / explanatory bullets where the surrounding code and tables already make the rationale self-evident, to reduce token load.

Either reference assets/small-logo.svg somewhere in the body or remove it, so the bundle structure stays consistent with what the skill actually uses.

Dimension	Reasoning	Score
Conciseness	Dense, reference-grade content that assumes Claude's competence (no explanations of what Next.js/RSC are), but at ~580 lines some sections like the repeated 'Why This Works' bullets and inline migration reference could be trimmed or split out.	4 / 5
Actionability	Fully executable copy-paste TSX/TS examples throughout — cache profiles, invalidation, RSC boundary fixes, provider islands, preloading — covering the common cases with concrete code and decision tables.	5 / 5
Workflow Clarity	The 'Implementation Sequence' gives a clear 8-step ordered process with a measurement checkpoint (step 8), and the 'PR Acceptance Criteria' checklist plus 'Common Failure Modes + Fixes' provide error-recovery guidance, though the feedback loops live in separate sections rather than inline in the workflow.	4 / 5
Progressive Disclosure	Well-organized with clear section headers, but it is a ~580-line monolithic SKILL.md with no references to separate files — content that could be split (full cache mechanics reference, migration guide, decision matrices) is all inlined, and the only bundle asset (small-logo.svg) is unreferenced.	3 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: concrete capabilities, an explicit 'Use when' clause, comprehensive natural trigger terms, and a tight Next.js 16 niche that minimizes conflict risk. Third-person voice is maintained throughout with no padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'cached shells with dynamic slots, provider islands, use cache boundaries, and link preloading strategy' plus 'implementing use cache with dynamic personalization, splitting entry vs static renderers, scoping client providers, or tuning prefetch behavior' — comprehensive coverage of specific actions.	5 / 5
Completeness	Explicitly answers both what ('Static-first Next.js 16 architecture patterns: cached shells with dynamic slots, provider islands, use cache boundaries, and link preloading strategy') and when ('Use when building or refactoring Next.js routes... Triggers on...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Extensive natural trigger phrases a user would actually say: 'static shell', 'use cache pattern', 'dynamic slots', 'provider island', 'prefetch strategy', 'static first', 'cache boundary', 'route goes dynamic unexpectedly' — full coverage with synonyms.	5 / 5
Distinctiveness Conflict Risk	Narrowly scoped to Next.js 16 static-first cache-component architecture with highly specific triggers, minimal overlap risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: joelhooks/joelclaw
Path: skills/nextjs-static-shells/SKILL.md
Commit: d952451

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.