multi-model-agent

Route delegation tasks to the most specific mma-* skill.

5|4|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/zhixuan312/multi-model-agent --skill multi-model-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-model-agent
Source: https://github.com/zhixuan312/multi-model-agent/tree/main/packages/server/src/skills/multi-model-agent
Command: npx skills add https://github.com/zhixuan312/multi-model-agent --skill multi-model-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route delegation tasks to the most specific mma-* skill rather than performing inline labor, ensuring the main model retains judgment.

Core Features & Use Cases

  • Dynamic task routing: identifies the appropriate mma-* skill (mma-execute-plan, mma-audit, mma-review, mma-debug, mma-investigate, mma-explore, mma-delegate) for each task.
  • Consistent orchestration: reduces duplicate work and enforces the Skill map for reproducible results.
  • Use cases include code review, auditing, debugging, codebase investigation, and plan execution with structured outputs.

Quick Start

Describe the task you want delegated, and the system will route it to the most specific mma-* skill.

Frequently Asked Questions about multi-model-agent

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

FAQPage Schema
How do I route tasks across multiple LLM providers for code review and debugging?

To route tasks across multiple LLM providers, this skill directs code review and debugging tasks to the most specific mma-* skill, ensuring the main model retains judgment while returning structured task identifiers for orchestration.

What is multi-model orchestration for codebase investigation?

Multi-model orchestration for codebase investigation is the process of delegating specific tasks to dedicated skills instead of inline dispatch, reducing duplicate work and enforcing a reproducible Skill map across different models.

Why should I delegate tasks to specific skills instead of inline dispatch?

You should delegate tasks to specific skills instead of inline dispatch to ensure judgment remains with the main model, which enforces the Skill map and provides consistent orchestration for reproducible results.

How do I execute plans across multiple models without losing context?

To execute plans across multiple models without losing context, describe the task for delegation and the system routes it to the appropriate mma-execute-plan skill, returning structured task identifiers for consistent orchestration.

Can I use this skill for auditing and reviewing code in a multi-provider environment?

Yes, you can use this skill for auditing and reviewing code in a multi-provider environment, as it dynamically identifies the correct mma-audit or mma-review route to enforce the Skill map for your specific task.

What are the limitations of using a Skill map for task routing?

The limitation of using a Skill map for task routing is that tasks must match the predefined mma-* skill categories like debugging or investigating, meaning highly novel tasks may lack a specific route within the current orchestration map.