CtrlK
BlogDocsLog inGet started
Tessl Logo

nextjs-framework

Explains how to configure App Router, implement server/client components, optimize data fetching, and secure routes. Use when the user mentions: 'add an authenticated route', 'migrate to App Router', 'optimize fetch caching', or 'fix RSC hydration'.

77

Quality

96%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

This is a strong, well-crafted skill that provides concrete, executable guidance for common Next.js App Router tasks. It excels at conciseness and actionability, with every section delivering copy-paste-ready code. The authenticated route checklist demonstrates excellent workflow clarity with explicit validation steps. The only weakness is that referenced files (REFERENCE.md) are not present in the bundle, making progressive disclosure harder to fully verify.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It doesn't explain what Next.js is, what Server Components are conceptually, or other things Claude already knows. Every section jumps straight to executable code or actionable checklists. The only minor note is the critical rule explanation is slightly verbose but justified given the subtlety of the gotcha.

3 / 3

Actionability

Every section provides fully executable, copy-paste-ready TypeScript/TSX code with realistic file paths and imports. The authenticated routes checklist gives specific commands (`tsc --noEmit`) and concrete validation criteria (302/307 redirect). Server actions, data fetching, and the dynamic import pattern are all concrete and complete.

3 / 3

Workflow Clarity

The 'Adding an Authenticated Route — Checklist' is a well-sequenced multi-step workflow with explicit validation checkpoints after each step (file exists, no render path when session is falsy, tsc passes, redirect confirmed). It includes a clear feedback loop at step 4 ('fix type errors') and the final step is an integration test.

3 / 3

Progressive Disclosure

The skill references `REFERENCE.md § Middleware examples` and `REFERENCE.md § Caching Details` for deeper content, which is good progressive disclosure. However, no bundle files are provided, so we cannot verify these references exist. The main content is well-structured with clear sections, but the reference to a non-provided REFERENCE.md slightly undermines navigation confidence.

2 / 3

Total

11

/

12

Passed

Description

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 a strong skill description that clearly communicates specific capabilities around Next.js App Router development and provides explicit trigger phrases that match natural user requests. It uses third person voice correctly, is concise without being vague, and carves out a distinct niche that would be easy to differentiate from other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'configure App Router', 'implement server/client components', 'optimize data fetching', and 'secure routes'. These are clear, actionable capabilities.

3 / 3

Completeness

Clearly answers both 'what' (configure App Router, implement server/client components, optimize data fetching, secure routes) and 'when' with an explicit 'Use when the user mentions...' clause listing specific trigger phrases.

3 / 3

Trigger Term Quality

Includes natural trigger phrases users would actually say: 'add an authenticated route', 'migrate to App Router', 'optimize fetch caching', 'fix RSC hydration'. These cover realistic user requests with specific terminology.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with Next.js App Router-specific terminology like 'RSC hydration', 'App Router', 'server/client components', and 'fetch caching'. These are niche enough to avoid conflicts with general web development or other framework skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
monkilabs/opencastle
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.