Skillzwave Logo
Skillzwave

nextjs-devtools

1 stars 2 forks
17
D

Next.js development tooling via MCP. Inspect routes, components, build info, and debug Next.js apps.Use when working on Next.js applications, debugging routing, or inspecting app structure.NOT for general React or non-Next.js projects.

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →
skilz install mjunaidca/mjs-agent-skills/nextjs-devtools
skilz install mjunaidca/mjs-agent-skills/nextjs-devtools --agent opencode
skilz install mjunaidca/mjs-agent-skills/nextjs-devtools --agent codex
skilz install mjunaidca/mjs-agent-skills/nextjs-devtools --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/mjunaidca/mjs-agent-skills
2. Copy the agent skill directory:
cp -r mjs-agent-skills/.claude/skills/nextjs-devtools ~/.claude/skills/
View on GitHub

Need detailed installation help? Check our platform-specific guides:

Claude Desktop Guide Claude Code Guide Troubleshooting

Related Agentic Skills

tailwind-shadcn-setup

by vanman2024

Setup Tailwind CSS and shadcn/ui component library for Next.js projects. Use when configuring Tailwind CSS, installing shadcn/ui, setting up design...

89
TECHjavascript
Marketplace

spanish-language-tutor

by sandraschi

Comprehensive Spanish language expert covering grammar, conversation, regional dialects, and language learning strategies

88
javascript
Marketplace

frontend-dev-guidelines

by diet103

Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organiz...

85
TECHjavascript
Marketplace

torch-geometric

by davila7

Graph Neural Networks (PyG). Node/graph classification, link prediction, GCN, GAT, GraphSAGE, heterogeneous graphs, molecular property prediction, ...

84
TECHjavascript
Marketplace

Agentic Skill Details

Owner
mjunaidca (GitHub)
Repository
mjs-agent-skills
Stars
1
Forks
2
Type
Technical
Meta-Domain
development
Primary Domain
javascript
Market Score
17
Agentic Skill Grades →

Agent Skill Grade

D
Score: 67/100 Click to see breakdown

Score Breakdown

Spec Compliance
12/15
PDA Architecture
20/30
Ease of Use
18/25
Writing Style
7/10
Utility
11/20
Modifiers: -1

Areas to Improve

  • Missing Referenced Scripts
  • No TOC for 103-Line File
  • No Validation or Feedback Loops

Recommendations

  • Focus on improving Utility (currently 11/20)
  • Address 3 high-severity issues first
  • Add trigger phrases to description for discoverability

Graded: 2026-01-24

Developer Feedback

I was curious how you'd handle integrating devtools into the Next.js ecosystem—the timing hints at solving some real pain points in the developer experience, but the implementation seems to be missing some structural decisions that would make it production-ready.

Links:

The TL;DR

You're at 67/100, which puts you in D territory. This is graded against Anthropic's skill best practices—specifically their Progressive Disclosure Architecture (PDA) standards. Your strongest area is Spec Compliance (12/15), but Utility is dragging you down hard at 11/20. The good news? You've got a solid foundation; you're just missing the structural pieces that would make this actually useful at scale.

What's Working Well

  • Spec compliance is solid — your frontmatter is valid YAML with all required fields, and the hyphen-case naming convention is correct
  • Clear trigger phrases — terms like "Next.js debugging," "inspect routes," and "component tree inspection" are discoverable and specific
  • Good troubleshooting table — having a dedicated section with common issues shows you're thinking about user pain points
  • Concrete command examples — you provide actual bash commands users can run, which is better than abstract explanations

The Big One: Missing Scripts and Layered Structure

Here's what's holding you back the most: you reference scripts (scripts/start-server.sh, scripts/mcp-client.py) that don't exist in your skill package, and everything lives in a single 103-line SKILL.md file with no supporting documentation.

Why it matters: Users can't actually run your examples. When they try bash scripts/start-server.sh, it fails. That breaks trust immediately.

The fix: Either include the actual s...

Browse Category

More development Agentic Skills

Report Security Issue

Found a security vulnerability in this agent skill?