orquestra-conductor

What problem does it solve?

This skill solves the problem of orchestrating a complete Solana transaction workflow (research → account resolution → unsigned tx building → mandatory preflight simulation → signing) without letting an AI guess critical blockchain inputs.

Core Features & Use Cases

• Routes the full transaction pipeline: delegates to specialized sub-skills for discovery, PDA/account resolution, transaction construction, preflight simulation, and final signing.
• Enforces safety boundaries: requires simulation before signing, blocks tool cross-over between phases (Orquestra MCP tools vs signer-mcp), and prevents invented program IDs, instruction names, PDA seeds, or account/argument values.
• Handles missing inputs explicitly: stops when required seeds or fields are missing and asks the user for only the exact missing value.

Use Case: Ask for a transaction like “build instruction to derive a PDA and buy an item” and the conductor will discover the program, resolve PDAs/accounts, build an unsigned base64 wire transaction, simulate it to decode Anchor errors, then ask for explicit YES before signing.

Quick Start

Say: "Orquestra Conductor, build a Solana transaction to call the <instruction> on program <program_id> on <network> for fee payer <fee_payer_wallet>, and use signer <wallet/authority>—please ask me for any missing accounts or PDA seeds."