Fetches nextjs-server-navigation from wsimmonds/claude-nextjs-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/nextjs-server-navigation
Restart Cursor to activate nextjs-server-navigation. Access via /nextjs-server-navigation in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Server Components use DIFFERENT navigation methods than Client Components!
When requirements call for server-rendered navigation—for example, linking to other pages, redirecting after a check, or demonstrating routing patterns—prefer <Link> and redirect() within Server Components. You still avoid 'use client' unless a client-only API is involved.
The Pattern
Scenario: build a server component that demonstrates proper navigation patterns
✅ CORRECT Solution:
// app/page.tsx (Server Component - NO 'use client'!)import Link from'next/link';exportdefaultasyncfunctionPage(){return(<div><h1>Home</h1><Link href="/dashboard">Go to Dashboard</Link><Link href="/profile">View Profile</Link></div>);}
❌ WRONG Solution:
// app/page.tsx'use client';// ❌ NO! Server components don't need this for navigation!import{ useRouter }from'next/navigation';// ❌ Wrong for server componentsexportdefaultfunctionPage(){const router =useRouter();// ❌ This is client-side navigation// ...}
Server Navigation Methods
Method 1: Link Component (Recommended for Links)
// app/page.tsximport Link from'next/link';exportdefaultasyncfunctionPage(){// Can still fetch data - this is a server component!const data =awaitfetchData();return(<div><h1>Welcome</h1>{/* Simple navigation link */}<Link href="/about">About Us</Link>{/* Dynamic link */}<Link href={`/products/${data.productId}`}>View Product</Link>{/* Link with styling */}<Link href="/dashboard" className="btn-primary"> Dashboard
</Link></div>);}
Key Points:
✅ Works in Server Components (no 'use client' needed)
✅ Can be async function
✅ Can fetch data
✅ No hooks required
Method 2: redirect() Function (For Conditional Redirects)
// app/profile/page.tsximport{ redirect }from'next/navigation';import{ cookies }from'next/headers';exportdefaultasyncfunctionProfilePage(){// Check authenticationconst cookieStore =awaitcookies();const session = cookieStore.get('session');// Redirect if not authenticatedif(!session){redirect('/login');}// Fetch user dataconst user =awaitfetchUser(session.value);return<div>Welcome,{user.name}!</div>;}
// app/page.tsx - Demonstrates multiple navigation patternsimport Link from'next/link';import{ redirect }from'next/navigation';import{ headers }from'next/headers';exportdefaultasyncfunctionHomePage(){// Server-side logicconst headersList =awaitheaders();const userAgent = headersList.get('user-agent');// Conditional redirect exampleif(userAgent?.includes('bot')){redirect('/bot-page');}return(<div><h1>Welcome to Our App</h1>{/* Navigation Links */}<nav><Link href="/about">About</Link><Link href="/products">Products</Link><Link href="/contact">Contact</Link></nav>{/* Button-style link */}<Link href="/get-started" className="button"> Get Started
</Link>{/* Dynamic link */}<Link href={`/user/
Implementation Guide
Prerequisites
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
