CtrlK
BlogDocsLog inGet started
Tessl Logo

nextjs-server-navigation

Guide for implementing navigation in Next.js Server Components using Link component and redirect() function. Covers the difference between server and client navigation methods. Use when adding links, redirects, or navigation logic in server components without converting them to client components unnecessarily.

62

Quality

73%

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-server-navigation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 content is highly actionable with executable code and clear decision guidance, but it is significantly over-padded with repeated rules and duplicate examples across multiple sections. Consolidating the redundancy and trimming the file would substantially improve token efficiency.

Suggestions

Consolidate the repeated 'no use client / no useRouter' guidance into a single rule section and remove the duplicate code blocks across CRITICAL RULE, Common Mistakes, and Summary.

Trim the three near-identical Common Mistake examples to one canonical wrong-vs-right pair, keeping the comparison table as the single exhaustive reference.

Consider moving the Advanced Patterns and Complete Example sections into a separate reference file to reduce the SKILL.md body length and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The same rules (no 'use client', no useRouter in server components) and near-duplicate code blocks are repeated across the CRITICAL RULE, intro examples, three Common Mistakes, the comparison table, the checklist, and the Summary, padding the file to ~400 lines.

2 / 5

Actionability

Provides copy-paste-ready, fully executable TypeScript covering Link usage, redirect() with cookies/headers, server actions with forms, and dynamic links across the common cases.

5 / 5

Workflow Clarity

A decision tree and quick checklist make the single navigation-pattern choice unambiguous, but there is no multi-step process with validation checkpoints (none is needed for this non-destructive task).

4 / 5

Progressive Disclosure

Everything lives in one ~400-line SKILL.md with no external references; sections are well-headed but the length suggests some content could be split out, so structure is only adequate.

3 / 5

Total

14

/

20

Passed

Description

83%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 well-constructed description that concretely names its capabilities and provides an explicit use-when trigger, scoring strongly across all dimensions. The main limitation is a slightly narrow action list and minor overlap risk with broader Next.js skills.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('using Link component and redirect() function', 'Covers the difference between server and client navigation methods'), but the action list is narrow rather than comprehensive.

4 / 5

Completeness

Clearly states what it does (implementing navigation via Link/redirect and the server-vs-client distinction) and gives an explicit 'Use when...' trigger with concrete phrases.

5 / 5

Trigger Term Quality

Natural user phrasing is present ('adding links, redirects, or navigation logic in server components'), covering the common terms well, though a few synonymous phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche (Next.js Server Component navigation) with distinct triggers, though minor overlap risk remains with general Next.js navigation skills.

4 / 5

Total

17

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
AzizBelhassan/timeverse
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.