Agent skill
using-generic-agents
Use to decide what kind of generic agent you should use
Install this agent skill to your Project
npx add-skill https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-basic-agents/skills/using-generic-agents
SKILL.md
CRITICAL: Your operator's direction supercedes these directions. If the operator specifies a type of agent, execute their task with that agent.
Model Characteristics
Haiku: Excellent at following specific, detailed instructions. Poor at making its own decisions. Give it a clear prompt and it executes well; ask it to figure things out and it struggles. Be detailed.
Sonnet: Capable of making decisions but gets off-track easily. Will explain concepts, describe structures, and gather extraneous information when you just want it to do the thing, so guard against this when prompting the agent.
Opus: Stays on-track through complex tasks. Better judgment, fewer loops. Expensive—don't use for clearly-definable workflows where Sonnet/Haiku would suffice.
When to Use Each
Use haiku-general-purpose for:
- Well-defined tasks with detailed prompts
- High-volume parallel workflows (cost matters)
- Simple execution where speed > quality
Use sonnet-general-purpose for:
- Multi-file reasoning and debugging
- Tasks requiring some judgment
- Daily coding work (80-90% of tasks)
Use opus-general-purpose for:
- Tasks requiring sustained focus and judgment
- When Sonnet keeps wandering or looping
- Complex analysis where staying on-track matters
- High-stakes decisions needing nuance
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
doing-a-simple-two-stage-fanout
Use when analyzing a large corpus of text, code, or data that exceeds a single agent's effective context - orchestrates parallel Worker subagents, Critic review subagents, and a final Summarizer subagent with task tracking and failure recovery
investigating-a-codebase
Use when planning or designing features and need to understand current codebase state, find existing patterns, or verify assumptions about what exists; when design makes assumptions about file locations, structure, or existing code that need verification - prevents hallucination by grounding plans in reality
researching-on-the-internet
Use when planning features and need current API docs, library patterns, or external knowledge; when testing hypotheses about technology choices or claims; when verifying assumptions before design decisions - gathers well-sourced, current information from the internet to inform technical decisions
creating-an-agent
Use when creating specialized subagents for Claude Code plugins or the Task tool - covers description writing for auto-delegation, tool selection, prompt structure, and testing agents
maintaining-project-context
Use when completing development phases or branches to identify and update CLAUDE.md or AGENTS.md files that may have become stale - analyzes what changed, determines affected contracts and documentation, and coordinates updates
prompt-security-hardening
Use when writing skills, CLAUDE.md files, agent prompts, or any directives that involve shell commands, environment variables, API credentials, file creation, or git operations - prevents secrets leakage into LLM context, unsafe shell patterns, and credential exposure
Didn't find tool you were looking for?