create-agent

Create Agent

ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of metadata.changelog above — e.g. create-agent vX.Y — recent: <summary>. Then proceed.

Scaffold a complete Claude Code agent from scratch. The agent will be Trinity-compatible and ready for development with playbook-based skill creation.

---

STEP 1: Gather Agent Requirements

If the user provided a topic as an argument, use it as context. Otherwise, ask.

Use AskUserQuestion to gather the following (can be a single open-ended question if user already provided detail, or multiple focused questions):

1a. Agent Purpose

Question: "What should this agent do? Describe its purpose, who it serves, and what problems it solves."

Header: "Agent Purpose"

Get enough detail to write a meaningful CLAUDE.md. Push for specifics — not "a coding agent" but "an agent that reviews Python PRs for a data engineering team and checks for SQL injection, missing tests, and schema migration issues."

1b. Agent Name

Question: "What should the agent be called?"

Header: "Agent Name"

• Suggest a name based on the purpose (lowercase-with-hyphens, short, memorable)
• Let the user override
• This becomes the directory name and the agent identity

1c. Destination

Question: "Where should I create the agent?"

Header: "Location"

Options:

1. ~/[agent-name] — Home directory (recommended)
2. ./[agent-name] — Current directory
3. Custom path — Let me specify

Expand ~ to actual home directory:

echo "$HOME"

1d. Initial Skills

Question: "What should this agent be able to do from day one? List 2-4 key capabilities."

Header: "Starting Skills"

Examples based on the purpose — if it's a content agent, suggest: "generate blog posts, review drafts, manage editorial calendar." If it's an ops agent: "check service health, deploy updates, investigate incidents."

These will become the agent's first skills.