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
96%
Does it follow best practices?
Impact
—
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 defines its scope around Next.js App Router functionality with specific capabilities and explicit trigger phrases. It uses third person voice correctly, is concise without being vague, and provides enough detail for Claude to distinguish it from other web development skills. The trigger terms are natural and cover both common tasks and specific pain points users would mention.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'configure App Router', 'implement server/client components', 'optimize data fetching', and 'secure routes'. These are all distinct, 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 niche triggers like 'App Router', 'RSC hydration', 'server/client components' that are specific to Next.js App Router patterns and unlikely to conflict with general web development or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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 delivers concise, actionable guidance for Next.js App Router patterns. The code examples are executable and realistic, and the authenticated route checklist demonstrates excellent workflow clarity with validation at each step. The main weakness is that REFERENCE.md is referenced but not provided in the bundle, making it impossible to verify the progressive disclosure chain.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows Next.js fundamentals and doesn't explain what Server Components or App Router are. Every section delivers actionable code or checklists without padding. | 3 / 3 |
Actionability | All sections provide fully executable, copy-paste-ready TypeScript/TSX code examples 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 error recovery (fix type errors) and a final integration test. The feedback loop of validate-fix-revalidate is well-represented. | 3 / 3 |
Progressive Disclosure | The skill references REFERENCE.md twice for deeper content (middleware examples, caching details), which is good progressive disclosure. However, no bundle files were provided, so we can't verify REFERENCE.md exists. The section-specific references use clear signaling ('§ Caching Details'), but the overall structure could benefit from a more explicit quick-start overview section separating it from the detailed sections. | 2 / 3 |
Total | 11 / 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
cc13aaf
- 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.