agent-builder

Create, improve, or troubleshoot Claude Code subagents with structured templates.

121|16|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/pr-pm/prpm --skill agent-builder-pr-pm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-builder
Source: https://github.com/pr-pm/prpm/tree/main/.claude/skills/agent-builder
Command: npx skills add https://github.com/pr-pm/prpm --skill agent-builder-pr-pm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the guesswork in creating effective Claude Code subagents by providing proven patterns and best practices.

Core Features & Use Cases

  • Agent Design: Expert guidance on system prompt engineering, tool configuration, and model selection.
  • Troubleshooting: Help with agent invocation issues, tool access problems, and output formatting.
  • Use Case: When your team needs to create a security-focused code reviewer agent, use this Skill to get the right structure, security checklists, and output formats.
  • Pattern Library: Access battle-tested templates for code reviewers, debuggers, data scientists, and test generators.

Quick Start

Use the agent-builder skill to create a new subagent for automated security scanning of TypeScript codebases.

Frequently Asked Questions about agent-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Claude Code subagent for a specific task?

Create a subagent by defining its system prompt with clear instructions, selecting the appropriate model, configuring tool access permissions, and establishing explicit output contracts. Start with a battle-tested template matching your use case—code reviewer, debugger, data scientist, or test generator—then customize scope, tool permissions, and output format for your workflow.

What's the best way to design a system prompt for an AI assistant?

System prompt engineering for AI assistants requires defining single responsibility, explicit output contracts, controlled tool permissions, and model configuration rules. Use proven patterns: state the agent's scope clearly, specify required and forbidden tools, define output format and structure, and document constraints to ensure reproducible, predictable behavior.

How do I configure tool access for a subagent?

Tool configuration for subagents involves explicitly granting or denying permissions to specific capabilities based on agent responsibility. Define which tools the agent can invoke, set access constraints, and validate that permissions align with the agent's scope to prevent unintended side effects and maintain security.

Why isn't my subagent producing the output format I need?

Output formatting issues stem from missing or ambiguous output contracts in the system prompt. Define exact output structure, field names, data types, and examples in your agent's instructions. Include failure cases and edge-case handling so the model knows precisely how to format every response.

Can I use subagent delegation patterns across development workflows?

Yes. Delegation patterns work across development, debugging, and optimization workflows by decomposing complex tasks into specialized agents with single responsibilities. Each agent handles one task, receives clear input contracts, and produces standardized outputs that feed into downstream agents or analysis steps.

What are common mistakes when setting up model selection for subagents?

Model selection mistakes include mismatching capability to task complexity, ignoring latency and cost trade-offs, and failing to test output quality for your specific prompt. Choose model size and capability based on task requirements, validate behavior with realistic test cases, and adjust system prompts if the model consistently underperforms.