MuleSoft Agent Broker V1 to V2 Converter

Converts an Agent Network V1 project (schema 1.0.0) into V2 (schema 2.0.0) by producing a brand-new project folder. The conversion is intentionally simple: every V1 broker becomes a V2 broker backed by an Agent Script .agent file with exactly one orchestrator node. Routing, classification, and conditional logic that V1 stuffed into a single LLM prompt remain inside that orchestrator's system.instructions — the upgrade does not break the prompt apart into multiple nodes.

Preserve the user's wording. Do not improvise or "improve" the source instructions. Treat the V1 file as the source of truth and only change what V2 actually requires.

If the user wants a richer multi-node graph (split deterministic routing into router nodes, move side-effects into executor nodes, separate cheap summary work into generator nodes), point them at build-agent-broker-project as the natural next step.

When to use

• Convert / upgrade / migrate / port an Agent Network or Agent Broker from V1 to V2.
• The user mentions schemaVersion: 1.0.0 and wants agentNetwork: 2.0.0.
• Working folder contains a V1 agent-network.yaml and exchange.json.

For general V2 questions (without converting), point at the builder skill instead.

References