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'.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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 occupies a clear niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
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 |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that is concise, actionable, and well-structured. It provides executable code for all key patterns (dynamic imports, auth routes, server actions, data fetching), includes a thorough validation checklist for the primary workflow, and appropriately delegates detailed reference material to a separate file. No significant weaknesses identified.
| Dimension | Reasoning | Score |
|---|---|---|
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. | 3 / 3 |
Actionability | All sections provide fully executable, copy-paste-ready TypeScript/TSX code with correct imports and realistic patterns. The authenticated route checklist includes specific commands (`tsc --noEmit`) and concrete validation criteria. | 3 / 3 |
Workflow Clarity | The 'Adding an Authenticated Route — Checklist' provides a clear numbered sequence with explicit validation steps after each action, including specific commands and expected outcomes (e.g., exit code 0, 302/307 redirect). This is a well-structured workflow with feedback loops. | 3 / 3 |
Progressive Disclosure | The skill provides a concise overview with quick-start code examples inline, then clearly signals deeper content via one-level-deep references to REFERENCE.md with specific section anchors (e.g., '§ Caching Details', '§ Middleware examples'). | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- monkilabs/opencastle
- Commit
f5c8508
- 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.