agent-finder

Select and delegate tasks to the best-fit Claude Code subagent.

Updated Jul 25, 2026
One-click install
npx skills add https://github.com/RorySullivan1/powerapp_taskmaster --skill agent-finder-rorysullivan1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-finder
Source: https://github.com/RorySullivan1/powerapp_taskmaster/tree/main/.claude/skills/agent-finder
Command: npx skills add https://github.com/RorySullivan1/powerapp_taskmaster --skill agent-finder-rorysullivan1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Choosing the wrong subagent — or doing everything in the main thread — floods the conversation context with verbose output and wastes turns. This Skill provides a disciplined four-step workflow (inventory, match, choose topology, delegate) for routing tasks to the right Claude Code subagent so bulky work stays out of the main context. ## Core Features & Use Cases - Agent inventory and inspection: List, search, and inspect built-in and custom agents (tools, model, scope) via a stdlib-only Python helper script. - Routing heuristics: Match tasks to the most specific agent by description, with default routings for Explore, Plan, and general-purpose. - Delegation patterns: Guidance on single agents, parallel fan-out, sequential chains, forks, and when to stay in the main thread, plus how to write a complete delegation prompt. - Use Case: You need to research how authentication, the database layer, and the API module work before a refactor. The Skill directs you to fan out three Explore agents in parallel, each returning only a summary, keeping search noise out of your main context. ## Quick Start Ask the assistant to find the right subagent for a task, for example: use the agent-finder skill to pick and delegate a codebase exploration of the auth module to the appropriate subagent.

Frequently Asked Questions about agent-finder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right Claude Code subagent for a task?▼

Match the task against each agent's description and prefer the most specific fit over general-purpose. Confirm the agent's tools and model actually suit the work, then delegate with a prompt containing the objective, inputs, constraints, and return contract.

How do I list available Claude Code subagents?▼

Run the helper script with python .claude/skills/agent-finder/scripts/agents.py list to show all custom agents plus the three built-ins. Use search with a keyword to filter by name, description, or tools, and show NAME to inspect one agent's full definition.

When should I use the Explore agent versus general-purpose?▼

Use Explore for read-only codebase search and file discovery since it runs on Haiku and is fast and cheap. Use general-purpose when the task needs both exploration and modification, or when no specialist agent matches the work.

When should I not delegate a task to a subagent?▼

Skip delegation for quick targeted changes, tasks needing tight back-and-forth, or work sharing significant context across phases. A fresh subagent pays startup cost re-gathering context, so a trivial one-line change is faster done in the main thread.

Why does a subagent not know my conversation context?▼

Non-fork subagents start fresh with no conversation history or previously read files. Everything the agent needs — objective, exact paths, constraints, and the expected return format — must be written into the delegation prompt.

How do I run multiple subagents in parallel in Claude Code?▼

Spawn independent subtasks together in one turn, such as researching separate modules concurrently. Cap the fan-out because every agent's result returns to the main context, and wide fan-outs with detailed returns can cost more context than they save.