nextjs-pathname-id-fetch

Focused pattern for fetching data using URL parameters in Next.js. Covers creating dynamic routes ([id], [slug]) and accessing route parameters in server components to fetch data from APIs. Use when building pages that display individual items (product pages, blog posts, user profiles) based on a URL parameter. Complements nextjs-dynamic-routes-params with a simplified, common-case pattern.

Quality

79%

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-pathname-id-fetch/SKILL.md

Quality

Content

71%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 body is highly actionable with runnable, well-chosen TypeScript examples and a clear pattern sequence, but it pays for it in conciseness and progressive disclosure: a duplicate full example and repeated boilerplate inflate the token budget, and everything lives in one inlined file. Trimming the redundancy and optionally externalizing variations would lift the weaker dimensions.

Suggestions

Consolidate the two near-identical product-page examples (lines 33-60 and 196-246) into a single canonical example to remove duplicated tokens; keep the richer one with error handling and drop the first.

In 'Key Rules' and 'Common Variations', show only the differing snippet (e.g. the param name/type) instead of re-listing the full async function and await boilerplate each time.

Move the extensive variations and complete examples into a separate reference file (e.g. references/variations.md) and signal it from SKILL.md so the overview stays lean, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Content is mostly useful and does not explain basic concepts Claude already knows, but it is noticeably redundant: a second near-complete product-page example (lines 196-246) largely repeats the first (lines 33-60), and the await/params boilerplate is re-shown across 'Key Rules' and 'Common Variations'. It could be tightened considerably, fitting anchor 3 rather than 4.	3 / 5
Actionability	Fully executable, copy-paste-ready TypeScript examples cover the common cases including different parameter names ([productId], [slug]), multiple parameters, and error handling with response.ok checks. Matches the anchor 5 example of covering common cases with runnable code.	5 / 5
Workflow Clarity	The core pattern is a clear 4-step sequence (create folder, access param, fetch, render) plus a Quick Checklist, but validation/error-handling appears only in one example rather than as an explicit checkpoint in the main workflow. This is a read-only fetch (not destructive/batch), so the cap-at-3 rule does not apply; minor validation gaps place it at 4.	4 / 5
Progressive Disclosure	The body is a single ~263-line file (well over the 50-line simple-skill exception) with clear section headers but no external reference files, and inlined duplicate examples/variations that could be split out. It has structure but is not optimally organized for navigation, fitting anchor 3.	3 / 5
	Total	15 / 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.

The description is strong: it concretely states what the skill does, gives explicit use-when triggers with realistic page examples, and cleanly distinguishes itself from a sibling skill. The only minor room for improvement is broader keyword synonyms and slightly more complete action coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('creating dynamic routes ([id], [slug])', 'accessing route parameters in server components to fetch data from APIs') but leaves minor gaps such as rendering and error handling. Fits anchor 4 rather than 5 because coverage of the full pattern is not exhaustive in the description itself.	4 / 5
Completeness	Explicitly answers both what ('Focused pattern for fetching data using URL parameters... Covers creating dynamic routes... and accessing route parameters in server components to fetch data from APIs') and when ('Use when building pages that display individual items... based on a URL parameter') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage including 'URL parameters', 'dynamic routes', '[id]', '[slug]', and concrete page types ('product pages, blog posts, user profiles'); a few natural synonyms (e.g. 'route params', 'query params') are absent, placing it at 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	Clear niche (simple pathname ID fetch) with distinct triggers and an explicit boundary statement ('Complements nextjs-dynamic-routes-params with a simplified, common-case pattern'), minimizing conflict risk with the related comprehensive skill.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: AzizBelhassan/timeverse
Path: .agents/skills/nextjs-pathname-id-fetch/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.