claude-code-subagents

Create and configure Claude Code subagents with templates and a helper script.

13|1|Updated Oct 18, 2025
One-click install
npx skills add https://github.com/emdashcodes/claude-code-plugins --skill claude-code-subagents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-code-subagents
Source: https://github.com/emdashcodes/claude-code-plugins/tree/main/plugins/claude-code-meta/skills/claude-code-subagents
Command: npx skills add https://github.com/emdashcodes/claude-code-plugins --skill claude-code-subagents

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

Claude Code subagents enable modular task delegation and specialized automation by separating responsibilities into isolated agents. This skill helps teams create, configure, and standardize subagents to improve automation, consistency, and knowledge sharing across projects and plugins.

Core Features & Use Cases

  • Template-driven subagent creation using assets and the helper script
  • Frontmatter-driven metadata (name, description, tools, model) for discovery and routing
  • Scoped deployment for project, user, and plugin environments, including marketplace integration

Quick Start

Start by running the helper script to generate a new subagent, for example: scripts/create_subagent.sh my-agent --project --template code-reviewer Then edit the resulting .md file to tailor the frontmatter and system prompt, and, if creating a plugin subagent, update .claude-plugin/marketplace.json accordingly.

Frequently Asked Questions about claude-code-subagents

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

FAQPage Schema
How do I create Claude Code subagents for modular task delegation?

To create Claude Code subagents, run the helper script with your desired agent name, scope, and template. This generates a markdown file where you configure frontmatter metadata and system prompts for isolated task automation.

What is frontmatter-driven metadata used for in workflow automation subagents?

Frontmatter-driven metadata defines the name, description, tools, and model for subagents. This structured metadata enables proper discovery and routing across project, user, and plugin scopes for consistent workflow automation.

Can I deploy subagents across project, user, and plugin scopes?

Yes, subagents support scoped deployment across project, user, and plugin environments. When creating plugin subagents, you update the marketplace.json file to ensure proper integration within the plugin marketplace.

What's the best way to standardize subagent creation across multiple projects?

The best way to standardize subagent creation is using template-driven generation. The included helper script and templates streamline subagent setup, ensuring frontmatter and system prompts are properly structured across all projects.

How does template-driven subagent creation streamline plugin development?

Template-driven subagent creation streamlines plugin development by providing pre-built structures for frontmatter and system prompts. You generate the base configuration via script, then tailor the markdown file and update marketplace.json for plugin integration.

Do I need to manually edit the system prompt after generating a subagent?

Yes, you need to manually edit the system prompt after generating a subagent. The helper script creates the base markdown file from a template, but you must tailor the frontmatter and system prompt to fit your specific automation requirements.