Mcreate-agent

Automate creation, documentation, and registration of QE Framework background agents.

6|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/inho-team/qe-framework --skill mcreate-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Mcreate-agent
Source: https://github.com/inho-team/qe-framework/tree/main/skills/Mcreate-agent
Command: npx skills add https://github.com/inho-team/qe-framework --skill mcreate-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the creation, documentation, and registration of background agents within the QE Framework, ensuring consistent formats and discoverability.

Core Features & Use Cases

  • Agent lifecycle: define purpose, perform overlap checks, write agent specification, and register in plugin.json and QE_CONVENTIONS.md.
  • Quality gates: enforce boundary definitions (Will/Will Not) and structured output formats.
  • Use Case: When you need to add a new background capability that operates under the framework’s executor patterns and is discoverable by Claude Code.

Quick Start

To create a new background agent, run the agent creation workflow and fill out the required frontmatter, body sections, and registration steps.

Frequently Asked Questions about Mcreate-agent

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

FAQPage Schema
How do I automate background agent creation for the QE Framework?

You can automate background agent creation by using a workflow that defines the agent's purpose, performs overlap checks, and registers it in plugin.json and QE_CONVENTIONS.md. This enforces consistent formatting and discoverability for new capabilities.

What files need to be updated to register a new plugin agent?

To register a new plugin agent, you must update plugin.json for discovery and QE_CONVENTIONS.md for framework documentation. The agent creation process also enforces required frontmatter and body documentation standards.

How do I define boundaries for a new QE Framework agent?

You define agent boundaries by specifying Will and Will Not actions during the agent specification phase. This quality gate enforces structured output formats and ensures the background capability operates correctly under the framework's executor patterns.

Does the agent registration workflow check for overlap with existing agents?

Yes, the agent creation workflow evaluates overlap with existing agents before finalizing registration. This ensures new background capabilities do not duplicate existing functions and maintain distinct operational boundaries within the framework.