orquestra-conductor

Orchestrate Solana transaction creation with discovery, simulation, and signing.

21|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/berkayoztunc/orquestra --skill orquestra-conductor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orquestra-conductor
Source: https://github.com/berkayoztunc/orquestra/tree/main
Command: npx skills add https://github.com/berkayoztunc/orquestra --skill orquestra-conductor

SYSTEM DOCUMENTATION & REQUIREMENTS

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."

Frequently Asked Questions about orquestra-conductor

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

FAQPage Schema
How do I safely build and sign a Solana transaction without guessing required accounts?

Orquestra Conductor orchestrates end-to-end Solana transaction creation by routing discovery, PDA resolution, unsigned instruction building, preflight simulation, and final signing without letting AI guess critical inputs.

Why does my AI try to sign Solana transactions before running preflight simulation?

AI might skip simulation due to missing safety guardrails. Enforcing phase-specific tool usage ensures a mandatory preflight simulation decodes Anchor errors and validates the unsigned transaction before any signing workflow is initiated.

What is the best way to resolve unknown PDA seeds for an Anchor instruction execution?

The best way to resolve unknown PDA seeds is to stop the transaction pipeline and explicitly ask the user for the exact missing values. This guarantees required inputs are satisfied safely without guessing during PDA derivation.

How do I prevent invented program IDs when building unsigned Solana wire transactions?

To prevent invented program IDs, apply safety boundaries that block tool cross-over between discovery and signing phases. The orchestrator routes program discovery and transaction construction sequentially to ensure all values are validated.

Can I use Anchor simulation to decode transaction errors before signing on Solana?

Yes, you can use mandatory preflight Anchor simulation to decode errors before signing. The orchestration workflow builds an unsigned base64 wire transaction, simulates it to catch Anchor errors, and requires explicit confirmation before signing.

What happens if required arguments are missing during Solana transaction building?

If required arguments are missing during Solana transaction building, the workflow stops and requests the exact missing seeds or values from the user. It never guesses critical blockchain inputs, ensuring the instruction execution request is resolved safely.