developer-toolbox▌
jezweb/claude-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Seven specialized agents for code review, debugging, testing, documentation, commits, and build verification.
- ›Includes commit-helper, build-verifier, code-reviewer, debugger, test-runner, orchestrator, and documentation-expert agents with auto-discovery triggers
- ›Each agent follows a \"MUST BE USED when\" pattern to trigger automatically based on user requests like \"code review\", \"TypeError\", \"write tests\", or \"document\"
- ›Agents can be chained together for multi-step workflows
Developer Toolbox
A collection of essential development workflow agents that integrate seamlessly with Claude Code.
What's Included
Agents (7)
| Agent | Purpose | Triggers On |
|---|---|---|
| commit-helper | Generate conventional commit messages | "commit message", "staged changes" |
| build-verifier | Verify dist/ matches source after builds | "changes not appearing", "verify build" |
| code-reviewer | Security audits and code quality reviews | "code review", "security audit", "OWASP" |
| debugger | Systematic debugging with root cause analysis | "error", "TypeError", "stack trace", "bug" |
| test-runner | TDD workflow and test creation | "write tests", "TDD", "coverage", "jest" |
| orchestrator | Coordinate complex multi-step projects | "coordinate", "multi-step", "complex feature" |
| documentation-expert | README, API docs, architecture diagrams | "document", "README", "API docs" |
Rules (1)
| Rule | Purpose |
|---|---|
| agent-first-thinking | Behavioral interrupt - consider agents before manual work |
Installation
# Via marketplace
/plugin install developer-toolbox
# Or local development
/plugin install ./skills/developer-toolbox
After installation, restart Claude Code to load the agents.
Usage Examples
Commit Helper
"Help me write a commit message for these staged changes"
Build Verifier
"My changes aren't appearing in production, verify the build output"
Code Reviewer
"Review this authentication code for security vulnerabilities"
Debugger
"I'm getting TypeError: Cannot read property 'map' of undefined"
Test Runner
"Use TDD to implement this user validation function"
Orchestrator
"Coordinate a refactor of the authentication system across 5 services"
Documentation Expert
"Create comprehensive API documentation for this REST endpoint"
Agent Design Philosophy
All agents follow the "MUST BE USED when" pattern for reliable auto-discovery:
description: |
[Role] specialist. MUST BE USED when: [trigger 1], [trigger 2], [trigger 3].
Use PROACTIVELY for [broad task category].
Keywords: keyword1, keyword2, error-message-fragment
This ensures Claude Code discovers and proposes the right agent automatically based on user requests.
Agent-First Thinking Rule
The included agent-first-thinking.md rule encourages using agents by default:
The Inversion:
- Wrong: "I'll do this manually unless it's big enough for agents"
- Right: "I'll use agents unless there's a reason not to"
Triggers:
| If about to... | Use instead... |
|---|---|
| grep/glob 3+ times | Explore agent |
| Read 5+ files | Explore agent |
| Same edit across files | Parallel agents |
| Audit multiple items | Parallel swarm |
Customization
Each agent can be extended by editing its markdown file after installation:
# Find installed agents
ls ~/.claude/plugins/cache/*/developer-toolbox/*/agents/
# Or copy to user-level for customization
cp [plugin-path]/agents/code-reviewer.md ~/.claude/agents/
Combining Agents
Agents work well together:
"Review this code for security issues, then write tests for the critical paths"
# → code-reviewer first, then test-runner
"Debug this failing test, document the root cause, and commit the fix"
# → debugger → documentation-expert → commit-helper
Version History
- 1.0.0 (2025-01-20): Initial release with 7 agents and 1 rule
How to use developer-toolbox on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add developer-toolbox
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches developer-toolbox from GitHub repository jezweb/claude-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate developer-toolbox. Access the skill through slash commands (e.g., /developer-toolbox) or your agent's skill management interface.
Security & Verification 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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★60 reviews- ★★★★★Arjun Gonzalez· Dec 28, 2024
developer-toolbox fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Omar Ramirez· Dec 16, 2024
We added developer-toolbox from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Kofi Desai· Dec 4, 2024
developer-toolbox has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Zara Chen· Nov 23, 2024
developer-toolbox fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Yuki Shah· Nov 19, 2024
developer-toolbox has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Layla Kapoor· Nov 7, 2024
Solid pick for teams standardizing on skills: developer-toolbox is focused, and the summary matches what you get after install.
- ★★★★★Kofi Dixit· Oct 26, 2024
developer-toolbox has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Omar Sanchez· Oct 14, 2024
We added developer-toolbox from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Arjun Diallo· Oct 10, 2024
Solid pick for teams standardizing on skills: developer-toolbox is focused, and the summary matches what you get after install.
- ★★★★★Daniel Srinivasan· Sep 25, 2024
developer-toolbox is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 60