custom-subagent

Coordinates a worker subagent with advisory channels to create Claude Code custom subagents.

Updated Oct 15, 2019
One-click install
npx skills add https://github.com/kkkaoru/dotfiles --skill custom-subagent-kkkaoru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: custom-subagent
Source: https://github.com/kkkaoru/dotfiles/tree/main/.claude/skills/custom-subagent
Command: npx skills add https://github.com/kkkaoru/dotfiles --skill custom-subagent-kkkaoru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating a well-designed Claude Code custom subagent requires balancing requirements, risks, and design tradeoffs, and doing it alone often misses strategic issues. This Skill orchestrates a dedicated worker subagent alongside independent advisory channels so agent definitions in .claude/agents directories are reviewed and validated before completion. ## Core Features & Use Cases - Coordinated advisory review: Combines the built-in advisor tool with a custom-advisor peer SubAgent for strategic guidance on requirements and design tradeoffs. - Worker delegation: Starts a custom-subagent worker that owns inspection, implementation, and validation with the full tool set and permission context. - Session reuse: Reuses existing custom-advisor sessions via SendMessage to preserve context instead of spawning redundant advisors. - Use Case: When you need a new project-level agent definition, invoke this Skill with the desired role, scope, capabilities, and constraints, and it reconciles worker output with advisor feedback into a finished, validated subagent. ## Quick Start Invoke /custom-subagent with the desired role, scope, capabilities, and constraints for the agent definition you want created.

Frequently Asked Questions about custom-subagent

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

FAQPage Schema
How do I create a custom subagent in Claude Code?

Invoke /custom-subagent with the desired role, scope, capabilities, and constraints as its argument. The Skill starts a custom-subagent worker that implements and validates the agent definition in a project or user-level .claude/agents directory.

What arguments does the custom-subagent skill require?

It requires the desired role, scope, capabilities, and constraints of the agent as its argument. If no requirements are supplied, it explains that these details are mandatory before proceeding.

How does the custom-advisor peer SubAgent work with the worker?

The custom-advisor runs as a same-level peer SubAgent using claude-opus-5 at medium effort, providing strategic advice on requirements and tradeoffs. The worker owns implementation, and neither spawns the other; peer SendMessage is reserved for advice that changes the work.

Can I disable the custom-advisor in the custom-subagent workflow?

Yes, set the CLAUDEX_CUSTOM_ADVISOR environment variable to 0, false, or off (case-insensitive) to skip the custom-advisor SubAgent. The built-in parameterless advisor tool still applies under its standard policy.

When should I start a new custom-advisor session instead of reusing one?

Start a new custom advisor only for true parallel or clean-room review, incompatible context, or an unavailable recipient. Otherwise, continue the first compatible session with SendMessage using the exact prior Agent/Task recipient.