mt-create-subagent

Create structured SubAgent definitions with template-based configuration and review workflows.

Updated May 15, 2026
One-click install
npx skills add https://github.com/t-miura-024/tools --skill mt-create-subagent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mt-create-subagent
Source: https://github.com/t-miura-024/tools/tree/main/chezmoi/dot_config/opencode/skills/mt-create-subagent
Command: npx skills add https://github.com/t-miura-024/tools --skill mt-create-subagent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users create well-scoped SubAgent definitions without mixing roles, workflows, and configuration concerns, reducing ambiguity when extending AI agent capabilities.

Core Features & Use Cases

  • Guideline-Based Design: Evaluates whether a SubAgent is the right solution and separates it from Rules, Hooks, or Skills.
  • Interactive Configuration: Collects identity, scope, constraints, principles, and referenced skills needed for a complete SubAgent definition.
  • Template-Driven Creation: Guides generation of consistent SubAgent files using predefined templates and review workflows.

Quick Start

Use the mt-create-subagent skill to create a new SubAgent definition for a specific role and review its configuration quality.

Frequently Asked Questions about mt-create-subagent

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

FAQPage Schema
How do I create a focused AI subagent with clear responsibilities in Cursor?

Creating a focused AI subagent involves collecting identity, scope, constraints, and principles to generate a structured definition. This prevents role ambiguity by using template-based configuration generation and review workflows for AI development environments.

What is the difference between an AI subagent and a rule or hook?

An AI subagent is a specialized role designed for specific tasks, whereas rules and hooks handle broader workflow automation. Evaluating subagent suitability separates these concerns to prevent mixing roles, workflows, and configuration logic in AI environments.

How do I generate consistent configuration files for multiple AI agents?

Generating consistent configurations for AI agents requires template-driven creation and review workflows. By collecting identity, scope, and constraints through predefined fields, you maintain consistent SubAgent metadata and scope across multiple agent definitions.

When should I use a specialized AI agent instead of a general workflow?

Use a specialized AI agent when a workflow requires evaluating SubAgent suitability for distinct roles. If the task needs clear boundaries, constraints, and principles separated from general workflows, a SubAgent definition is the appropriate solution.

What configuration fields are required to define a complete AI subagent?

Defining a complete AI subagent requires collecting identity, scope, constraints, principles, and referenced skills. These configuration fields ensure the agent has clear responsibilities and boundaries for the AI development environment.

Does template-based configuration prevent role ambiguity in AI development environments?

Template-based configuration prevents role ambiguity by generating consistent SubAgent files with clear boundaries. It separates roles, workflows, and configuration concerns through a structured review process for AI development environments.