How do I choose the right template for my agent?

Match the agent's purpose to one of the templates: Review/Audit, Generate/Create, Fix/Modify, Test/Validate, Document, or Orchestrate. Then supply the necessary tools and a suitable model.

What models can I use and how do I set them?

Models supported are haiku, sonnet, and opus. Choose a model based on task complexity and desired style, and set it in the frontmatter.

Is linking another skill optional?

Yes. Linking a skill in the frontmatter is optional and can auto-load related capabilities if provided.

agent-template

Scanned

npx machina-cli add skill claude-world/director-mode-lite/agent-template --openclaw

Files (1)

SKILL.md

3.2 KB

Agent Template Generator

Generate a custom agent file based on requirements.

Usage: /agent-template [agent-name] [purpose]

Templates

Purpose	Template	Tools	Color	Model
Review/Audit	Reviewer	Read, Grep, Glob, Bash	yellow	sonnet
Generate/Create	Generator	Read, Write, Grep, Glob	cyan	sonnet
Fix/Modify	Fixer	Read, Write, Edit, Bash, Grep	red	sonnet
Test/Validate	Tester	Read, Bash, Grep, Glob	green	sonnet
Document	Documenter	Read, Write, Grep, Glob	cyan	sonnet
Orchestrate	Orchestrator	Read, Write, Bash, Grep, Glob, Task	cyan	haiku

Process

Gather Requirements
- Agent name (lowercase, hyphenated)
- Purpose
- Tools needed
- Model (haiku/sonnet/opus)
- Linked skill (if any)
Select Template based on purpose
Generate File at .claude/agents/[name].md
Validate with /agent-check

Frontmatter Reference

---
name: agent-name            # Required: lowercase, hyphenated, 3-50 chars
description: Brief desc     # Required: triggering conditions + <example> blocks
color: cyan                 # Required: yellow, red, green, blue, magenta, cyan
tools:                      # Optional: YAML list (omit = all tools)
  - Read
  - Write
  - Edit
  - Bash
  - Grep
  - Glob
  - Task
  - WebFetch
  - WebSearch
  - TodoWrite
  - NotebookEdit
model: sonnet               # Required: inherit, haiku, sonnet, opus, best, sonnet[1m], opus[1m], opusplan
# forkContext: "true"        # Optional: context isolation (string, not boolean)
# maxTurns: 20              # Optional: max agentic turns before stopping
skills:                     # Optional: skills to auto-load (array)
  - linked-skill
# memory:                   # Optional: CLAUDE.md access (array)
#   - user
#   - project
#   - local
# mcpServers:               # Optional: MCP servers (string ref or inline config)
#   - memory
#   - name: custom-server
#     type: stdio
#     command: npx
#     args: ["-y", "@example/server"]
hooks:                      # Optional: agent-scoped lifecycle hooks
  PreToolUse:
    - matcher: Write
      hooks:
        - type: command
          command: ./scripts/validate.sh
  PostToolUse:
    - matcher: Bash
      hooks:
        - type: command
          command: ./scripts/log.sh
  Stop:
    - hooks:
        - type: command
          command: ./scripts/check.sh
          once: true
permissionMode: default     # Optional: default, acceptEdits, bypassPermissions, plan, delegate, dontAsk
disallowedTools:            # Optional: explicit tool blocking
  - NotebookEdit
---

Reviewer Template Structure

---
name: [name]
description: [brief purpose]
color: yellow
tools:
  - Read
  - Grep
  - Glob
  - Bash
model: sonnet
skills:
  - linked-skill
---

# [Name] Agent

## Activation
When to trigger

## Review Checklist
- [ ] Check items

## Output Format
Report structure

Example

/agent-template security-scanner "scan code for vulnerabilities"

Output: Created .claude/agents/security-scanner.md

Source

git clone https://github.com/claude-world/director-mode-lite/blob/main/skills/agent-template/SKILL.mdView on GitHub

Overview

Agent-template generates a tailored agent file based on your chosen purpose and template. It guides you through requirements, template selection, and produces a ready to use .claude/agents/[name].md with validation via agent-check.

How This Skill Works

Provide the agent name and purpose via the /agent-template command. The system selects a matching template from the predefined list, assembles frontmatter with name, description, color, tools, and model, writes the agent file to .claude/agents/[name].md, and then you can validate readiness with /agent-check.

When to Use It

Need an audit or reviewer agent for code or content
Want to generate or create assets or code with a Generator template
Need a fixer or modifier to patch issues using the Fixer template
Set up a tester or validator agent for checks or tests with the Tester template
Document or orchestrate workflows with a Documenter or Orchestrator template

Quick Start

Step 1: /agent-template [agent-name] [purpose]
Step 2: Confirm frontmatter details such as color, tools, and model for the chosen template
Step 3: Review the result at .claude/agents/[name].md and run /agent-check

Best Practices

Use a lowercase hyphenated name for the agent to ensure URL-safe references
Align the chosen template with the agent's primary purpose
Include the necessary tools in the frontmatter or omit to default to all
Choose a model that fits task complexity and style preference
Validate the generated file with /agent-check before use

Example Use Cases

security-scanner: Audit code for vulnerabilities using the Reviewer template
api-doc-builder: Generate documentation with the Documenter template
bug-fixer: Patch issues in code using the Fixer template
test-runner: Validate features with the Tester template
project-orchestrator: Coordinate tasks with the Orchestrator template

Frequently Asked Questions

Add this skill to your agents