nextjs-advanced-routing

Guide for advanced Next.js App Router patterns including Route Handlers, Parallel Routes, Intercepting Routes, Server Actions, error boundaries, draft mode, and streaming with Suspense. CRITICAL for server actions (action.ts, actions.ts files, 'use server' directive), setting cookies from client components, and form handling. Use when requirements involve server actions, form submissions, cookies, mutations, API routes, `route.ts`, parallel routes, intercepting routes, or streaming. Essential for separating server actions from client components.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/nextjs-advanced-routing/SKILL.md

Quality

Content

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

The skill is highly actionable with excellent executable examples and a genuinely useful scoping workflow, but it is far too long and repetitive, inlining reference-grade material that should live in separate files. The lack of progressive disclosure and token efficiency are its main weaknesses.

Suggestions

Move the bulk of the code-example reference (route handlers, draft mode, streaming, advanced patterns) into separate reference files under ./references/ and keep SKILL.md as a concise overview with one-level-deep links, following the rubric's good-example pattern.

Consolidate the repeatedly-stated Server Actions return-type and file-naming rules into a single authoritative section; remove the duplicate re-statements spread across 'When to Use', 'CRITICAL' blocks, and 'File Organization'.

Add explicit validation/verification checkpoints (e.g., type-check after writing actions, verify cookie is set) to the destructive/batch operations so workflow clarity can reach its top anchor.

Dimension	Reasoning	Score
Conciseness	At ~1470 lines the body is heavily padded: the Server Actions return-type rule and file-naming guidance are each restated multiple times across overlapping sections, and basic concepts (HTTP method exports, what parallel routes are) are over-explained relative to what Claude already knows.	2 / 5
Actionability	Numerous copy-paste-ready, executable TypeScript/TSX examples cover route handlers, server actions, cookies, parallel/intercepting routes, error boundaries, draft mode, and streaming, spanning the common cases with concrete imports and signatures.	5 / 5
Workflow Clarity	The 'Step 0: Determine Parallel Route Scope' section gives a clear decision process with criteria and examples, and server-action patterns are explicitly sequenced; however batch/destructive operations (db deletes, cookie setting) lack explicit validation/verification checkpoints.	4 / 5
Progressive Disclosure	No bundle files exist and no external references are used; the entire API reference and pattern library is inlined into a monolithic wall of text, so content that clearly belongs in separate reference files is not split out.	2 / 5
	Total	13 / 20 Passed

Description

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

The description is detailed and trigger-rich, explicitly covering both capabilities and use-conditions with concrete file and directive keywords. It is slightly long and conflates capability statements with trigger guidance, which is the only thing keeping it from being perfect.

Suggestions

Tighten the description by separating capability statements ('Guides advanced App Router patterns...') from trigger conditions ('Use when...') to reduce redundancy.

Trim the CRITICAL sub-clauses; fold the most important trigger (server actions, 'use server') into the main 'Use when' clause rather than stacking multiple conditional sentences.

Dimension	Reasoning	Score
Specificity	Lists many concrete capabilities (Route Handlers, Parallel Routes, Intercepting Routes, Server Actions, error boundaries, draft mode, streaming) with specific file/directive triggers like `action.ts`, `'use server'`, and `route.ts`, though some are framed as triggers rather than pure capability actions.	4 / 5
Completeness	Explicitly answers both 'what' (advanced Next.js App Router patterns) and 'when' via a clear 'Use when requirements involve...' clause plus CRITICAL edge-case triggers.	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage including 'server actions', 'form submissions', 'cookies', 'mutations', 'API routes', `route.ts`, 'parallel routes', 'intercepting routes', and 'streaming', matching phrasings users would actually say.	5 / 5
Distinctiveness Conflict Risk	Clear niche (advanced App Router routing/server actions) with distinct triggers, but the breadth across many Next.js subsystems creates minor overlap risk with a general Next.js skill.	4 / 5
	Total	18 / 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 (1479 lines); consider splitting into references/ and linking	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	14 / 16 Passed

Repository: AzizBelhassan/timeverse
Path: .agents/skills/nextjs-advanced-routing/SKILL.md
Commit: 9dc2cb4

Reviewed: ~15 hours 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.