| name | agent-creator |
| description | Create AiderDesk agent profiles via interactive Q&A. |
Agent Profile Creator
Create agent profiles stored as config.json in ~/.aider-desk/agents/{name}/ (global) or {project}/.aider-desk/agents/{name}/ (project-level).
READ REFERENCES before proposing to ensure accuracy:
- Tool groups & schema:
references/agent-profile-schema.md - Tool approvals:
references/tool-approval-guide.md+references/agent-profile-schema.md - Subagent config:
references/subagent-guide.md - Examples:
references/profile-examples.md
Simplified Q&A Process
Step 1: Understand Purpose
Ask user: "Describe the agent's purpose and what it should do."
Based on their response, internally propose all properties:
- Name (derived from purpose)
- Max iterations (default 250)
- Tool groups (based on purpose)
- Custom instructions (if applicable)
- Subagent config (always enabled, contextMemory: "off" by default)
- Tool approvals (based on needs)
READ all reference files before proposing.
Step 2: Provider/Model
Ask: "Which provider/model? (format: provider/model, e.g., anthropic/claude-sonnet-4-5-20250929)"
- Split by first slash to get provider and model
- No validation - use as-is (correct obvious typos only)
Step 3: Optional Advanced Settings
ONLY ask if user specifically mentioned temperature, max tokens, rate limiting, or MCP servers:
- "What temperature should I use?" (0.1-1.0, optional)
- "Max tokens limit?" (optional)
- "Min time between tool calls in ms?" (optional)
- "Which MCP servers should be enabled?" (optional, default: none)
If not mentioned, skip this entire step.
Step 4: Location
Ask: "Global profile (all projects) or project-specific? (default: global)"
Step 5: Single Review & Confirm
Present one complete summary with all proposed properties. Ask:
"Here's your agent profile. Should I create it?"
Show:
- Name, provider/model
- Tool groups enabled
- Tool approvals summary (which are "never", which are "always")
- Subagent config
- Location
DO NOT ask for confirmations on individual items. Only one final approval.
Step 6: Create
On user confirmation, generate the profile.
READ references/profile-examples.md to verify structure before creating files.
Tool Group Reference
- Power Tools: File system, shell, search (for agents that read/write files)
- Aider Tools: AI code generation via Aider (NOT default - see note below)
- Power Search: Advanced code search (for analysis/docs)
- Todo Tools: Task list management (for agents that track work)
- Memory Tools: Persistent information storage (for learning agents)
- Skills Tools: Access to project-specific skills (for agents using custom skills)
- Subagents: Task delegation to specialized subagents (for agents that can call others)
Aider Tools Note: Specialized for AI code generation. Do NOT enable by default.
- If user wants coding: explain Aider (advanced refactoring) vs Power Tools (direct editing)
- Ask preference before enabling
Tool Approval Strategy
Keys: {group}---{tool} (three dashes)
Default is "ask". Only set:
- "never": Tools completely irrelevant (e.g.,
power---bashfor read-only agents) - "always": Safe, essential tools (e.g., read operations for reviewers)
READ references/tool-approval-guide.md to see all available tools and their purposes.
Only include tools that exist in reference docs.
Subagent Configuration
Every agent is a subagent (enabled: true)
READ references/subagent-guide.md for detailed guidance on context memory modes and configuration:
contextMemory: Default is"off"(fresh each time)- Use
"full-context"only for specialized analysis agents (code review, security audit) - Use
"last-message"for progressive builders (documentation, iterative tasks)
- Use
systemPrompt: Specialized for agent's purposeinvocationMode: automatic (specialized), on-demand (general)color: Relevant color (e.g., red=security, blue=power tools)description: Clear description for auto-invocation
File Structure
{profile-name}/
└── config.json
Validation
- Unique name
- Provider/model: Use as-is (correct obvious typos only)
- Tool keys:
{group}---{tool}format - Values: "always", "ask", or "never"
- Subagent enabled
- All tool keys from references
Resources
references/agent-profile-schema.md- Complete schemareferences/subagent-guide.md- Subagent configuration guide (context memory modes)references/profile-examples.md- Examplesreferences/tool-approval-guide.md- Tool approval configassets/templates/config.json.template- Templateassets/examples/sample-profile.json- Example