agent-design
From the author
Scope an agent or subagent before it is built — the one job it owns, the smallest tool set that closes that job, what it must never do, and the evidence it has to return. Use when adding an agent, subagent or automated role to a system, when deciding which tools it gets, when an existing agent loops, over-reaches or reports work it did not do, or when reviewing someone else's agent design. Not for wording the prompt itself, not for deciding what occupies its context window, and it never grants an agent permission it did not already have.
Install
npx skills add nahid-sparktales/agent-dispatcher --skill agent-design -a claude-code
Installs to .claude/skills/agent-design/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- agent-securitynahid-sparktales/agent-dispatcherSecure an agent system as a permission surface — what authority each tool call runs under, where the confused deputy sits, which controls are enforced outside the model and which are only prompt text, and how far one bad call reaches. Use when granting an agent tools or credentials, wiring in MCP servers or subagents, reviewing an agent that acted beyond what the requester could have done, or before letting an agent touch a shared or production system. Not for wording the ingestion trust boundary in detail (prompt-injection-defense), not for scoping what an agent is for (agent-design), and it never grants an agent permission it did not already have.Security★ 59
- agent-interface-designNeeeophytee/finding-unknowns-skillsDesign tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples. Use when building an MCP server or tool definition, writing an agent-facing script, or when an agent keeps misusing a tool it already has.Design★ 353
- agent-team-designagentlas-ai/Agentlas-OSUse when designing a new multi-agent team, visible agents folder, role boundaries, handoff flow, PM Soul, Memory Curator, Policy Gate, or evaluation role. Use for agent-team repo creation even when the user only says they want a meta-agent or agent operating system.Design★ 1.6K
- agent-designeralirezarezvani/claude-skillsUse when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer).Design★ 28.7K
- agent-architecturegithub/awesome-copilotDesign AI agent architectures through requirements discovery, or audit and diagnose architectural flaws in existing agents. Architecture only; excludes implementation and general code review.Planning★ 40.4K
- agents-systemPaulRBerg/agent-skillsRedesign the assigned repository or repositories for agent understanding, control, and cumulative learning. Use when asked to make a system agent-intuitive, agent-ergonomic, or agent-accretive, then revise its design documents and plans.Design★ 101
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in