create-subagent

Create file-based and Task tool subagents for Claude Code with configuration templates.

5|3|Updated Oct 23, 2025

Search Tags:#automation #subagents #agents #system-prompt #Task tool

Ready to run

npx skills add https://github.com/Cygnusfear/claude-stuff --skill create-subagent-cygnusfear

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-subagent
Source: https://github.com/Cygnusfear/claude-stuff/tree/main/skills/create-subagent
Command: npx skills add https://github.com/Cygnusfear/claude-stuff --skill create-subagent-cygnusfear

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guidance for creating and configuring subagents (file-based or Task-tool-based) to handle specialized tasks with isolated contexts and tailored prompts.

Core Features & Use Cases

File-based Subagents – Persistent agents stored under .claude/agents/ with system prompts.
Task Tool Subagents – Dynamic, on-demand agents dispatched via Task tool.
Configuration – Tools, model, permissions, and skills per subagent.
Templates – Agent templates for common patterns (code-reviewer, tester, researcher, etc.).

Quick Start

Create a file-based agent with a role prompt and assign it to a targeted task, or dispatch a dynamic subagent via the Task tool with a tailored system prompt.

Frequently Asked Questions about create-subagent

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

FAQPage Schema

How do I create subagents to delegate specialized tasks in Claude Code?▼

Create subagents by defining a system prompt, name, and description, then store them as files under .claude/agents/ or dispatch them dynamically via the Task tool. Subagents isolate context and apply tailored configurations like tools, model selection, and permissions to handle focused work independently.

What's the difference between file-based and Task tool subagents?▼

File-based subagents persist under .claude/agents/ with stored system prompts for repeatable workflows. Task tool subagents are dynamic, created on-demand during execution with inline prompts. Choose file-based for stable roles; use Task tool for one-off specialized tasks requiring isolated context.

When should I use subagents instead of handling tasks directly?▼

Use subagents when tasks require specialized expertise, need isolated context to avoid interference, must follow repeatable workflows, or benefit from differentiated tool permissions. They prevent context pollution and enable parallel or sequential delegation with role-specific constraints.

What fields are required when configuring a subagent?▼

Name and description are required for all subagents. Optional fields include tools (which capabilities the subagent accesses), model (inference model), permissionMode (access controls), and skills (pre-built task patterns). Templates for common roles like code-reviewer and tester provide configuration starting points.

Can I assign specific tools and permissions to individual subagents?▼

Yes. Subagent configuration supports per-agent tool selection, permission modes, and skill assignment, allowing you to restrict access and tailor capabilities to the task. This prevents unnecessary tool exposure and enforces role-based workflows within delegated work.