CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nextjs-app-router-patterns

Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components.

61

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/nextjs-app-router-patterns/SKILL.md

The canonical home for this skill is nextjs-app-router-patterns in wshobson/agents

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 well-organized, code-rich pattern catalog that is immediately actionable, but it functions as a monolithic reference duplicating much of what Claude already knows about Next.js App Router. Splitting patterns into reference files, trimming known-material sections, and adding pattern-selection guidance would raise quality across the board.

Suggestions

Split the eight patterns into one-level-deep reference files (e.g., references/routing-patterns.md, references/data-fetching.md, references/server-actions.md) and keep SKILL.md as a concise overview with clearly signaled links.

Remove or compress sections that restate Claude's existing knowledge — the rendering-modes table, file-conventions listing, and 'use client' basics — keeping only Next.js 14/15-specific gotchas (e.g., Promise-based params/searchParams, revalidateTag usage).

Add brief decision guidance for choosing among patterns (e.g., when to use intercepting routes vs. parallel routes, when streaming Suspense boundaries are worth it) so the catalog functions as a workflow rather than a lookup table.

DimensionReasoningScore

Conciseness

Mostly dense, code-first content with little prose padding, but substantial sections restate what Claude already knows (rendering-modes table, App Router file conventions, 'use client' basics, the metadata API), so it could be significantly tightened.

3 / 5

Actionability

Concrete, near copy-paste-ready TypeScript/JSX examples across all eight patterns, with minor gaps: many rely on undefined helpers (db, getAnalytics, processOrder, Providers) rather than being fully self-contained.

4 / 5

Workflow Clarity

A pattern catalog rather than a workflow: no multi-step sequence, decision guidance for choosing among patterns, or validation checkpoints. No destructive/batch operations, so the validation cap does not apply, but sequence and checkpoints are effectively absent.

3 / 5

Progressive Disclosure

Well-sectioned with clear headers, but everything is inlined in a single ~540-line SKILL.md with no bundle files or one-level-deep references; the pattern detail clearly belongs in separate reference files.

3 / 5

Total

13

/

20

Passed

Description

87%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.

A strong description: concrete capabilities, explicit use-when triggers with natural keywords, and a distinct niche. Minor room to tighten "Master...advanced" phrasing and add trigger synonyms like Pages Router migration or Server Actions.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ("Server Components, streaming, parallel routes, and advanced data fetching") though "Master" and "advanced" are mildly fluffy and coverage of the domain (caching, Server Actions, metadata) is incomplete.

4 / 5

Completeness

Explicitly answers both what ("Master Next.js 14+ App Router with Server Components, streaming, parallel routes...") and when ("Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components") with concrete trigger phrases; not 4 because the when-clause is already specific rather than needing more explicitness.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("Next.js applications", "SSR/SSG", "App Router", "React Server Components") that users would plausibly say; misses common variations like "Pages Router", "migrate to App Router", or "Server Actions".

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Next.js 14+ App Router) with distinct, framework-specific triggers that are unlikely to fire for other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (544 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

alpacapurpura/ap_sales_agent

Path

.agents/skills/nextjs-app-router-patterns/SKILL.md

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.