Seven specialized agents for code review, debugging, testing, documentation, commits, and build verification.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondeveloper-toolboxExecute the skills CLI command in your project's root directory to begin installation:
Fetches developer-toolbox from jezweb/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate developer-toolbox. Access via /developer-toolbox in your agent's command palette.
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.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
697
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
697
stars
A collection of essential development workflow agents that integrate seamlessly with Claude Code.
| 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" |
| Rule | Purpose |
|---|---|
| agent-first-thinking | Behavioral interrupt - consider agents before manual work |
# Via marketplace
/plugin install developer-toolbox
# Or local development
/plugin install ./skills/developer-toolbox
After installation, restart Claude Code to load the agents.
"Help me write a commit message for these staged changes"
"My changes aren't appearing in production, verify the build output"
"Review this authentication code for security vulnerabilities"
"I'm getting TypeError: Cannot read property 'map' of undefined"
"Use TDD to implement this user validation function"
"Coordinate a refactor of the authentication system across 5 services"
"Create comprehensive API documentation for this REST endpoint"
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.
The included agent-first-thinking.md rule encourages using agents by default:
The Inversion:
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 |
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/
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
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
jezweb/claude-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
developer-toolbox fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added developer-toolbox from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
developer-toolbox has been reliable in day-to-day use. Documentation quality is above average for community skills.
developer-toolbox fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
developer-toolbox has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: developer-toolbox is focused, and the summary matches what you get after install.
developer-toolbox has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added developer-toolbox from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: developer-toolbox is focused, and the summary matches what you get after install.
developer-toolbox is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 60