orquestra-pda-explorer

Resolve missing Solana PDA accounts by deriving addresses and fetching on-chain data.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of not knowing which Program Derived Address (PDA) to use or how to fetch the on-chain account data for it when you only have partial inputs or missing seeds.

Core Features & Use Cases

  • Deterministic PDA derivation and account fetching: Derives PDAs and retrieves their on-chain data using only Orquestra MCP tools.
  • Iterative missing-account resolution: Iteratively fills unresolved accounts by extracting new pubkeys from fetched PDA data.
  • Guardrailed safe workflow: Refuses to guess seed values and stops until required accounts are fully resolved before handing off to transaction-building.

Use cases include deriving a PDA from a wallet pubkey, finding a stake or vault PDA when you do not know the exact seeds, and resolving the full set of required accounts (and their data) for downstream workflows.

Quick Start

Ask the AI: "Derive the missing vault PDA and resolve all required PDA accounts for program <program id or name> using the wallet pubkey <wallet pubkey> and fetch the on-chain data."

Frequently Asked Questions about orquestra-pda-explorer

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

FAQPage Schema
How do I derive a Solana Program Derived Address when I only have a wallet pubkey?

To derive a Solana Program Derived Address (PDA) from a wallet pubkey, use the derive_pda tool to deterministically calculate the address, then use fetch_pda_data to retrieve its on-chain account data.

How do I resolve missing PDA seeds for a vault or stake account on Solana?

Resolving missing PDA seeds on Solana requires iterative account resolution: fetch known PDA data with fetch_pda_data, extract new pubkeys from the results, and repeat until all required accounts are filled.

Can I use Orquestra MCP tools to fetch on-chain data for program-owned accounts?

Yes, you can use Orquestra MCP tools to fetch on-chain data for program-owned accounts by applying list_pda_accounts and get_program_data to filter and inspect program-owned PDA data.

Why does my PDA resolution workflow stop before finding all required accounts?

PDA resolution workflows stop before finding all required accounts because the process forbids seed guessing and iterates only through extracted pubkeys until all required accounts are fully resolved.

What is the best way to resolve a full set of PDA accounts for a Solana transaction?

The best way to resolve a full set of PDA accounts for a Solana transaction is to iteratively derive addresses and fetch on-chain data, extracting dependent pubkeys from fetched accounts until the set is complete.