DeFi infrastructure

Make the requested agent capable of its first task through maintained provider tools. Separate installed software, available credentials, authenticated access, live reads and transaction authority; success at one does not prove the next.

Start with the requested task

Read task examples and user configuration for a completed example and recovery path. Apply only the workflow stages needed by the current request. Reuse supplied preferences and compatible tools; ask only for missing terms that affect this task. Public explanation or comparison does not require transaction fields. Keep any existing authorization within its exact scope.

Pick the needed plumbing

• RPC and Alchemy: read RPC and Alchemy to select a chain, verify node freshness and choose CLI or MCP transport.
• Wallet ownership and Coinbase: read Managed wallets before selecting custody, an isolated portfolio or an agent wallet. Existing exchange access is not an onchain signer.
• Paid APIs, sponsorship and scoped permissions: read Payments and authority. An HTTP 402 is a price offer, not approval to pay.
• Hermes installation and tool exposure: read Hermes wiring. Keep Hermes as the runtime; integrate its native skills, profiles and MCP configuration instead of maintaining a fork.
• CLI prompts, authentication failures or stalled sessions: use CLI recovery to distinguish missing access from transport and uncertain writes.
• Broken connectivity: use Readiness diagnostics for a bounded, read-only probe and a precise readiness report.

Start with the user's selected chain and task. Read-only research needs RPC or indexed data, not a newly created wallet. Reuse an existing compatible provider connection when its account and permissions match; do not install every wallet product. Keep seed phrases and private keys outside agent prompts, repository files and diagnostic logs.

Read primitive tool wiring for official MCP/SDK selection, progressive disclosure, schema changes and EVM/Solana transaction context.

First usable result

For example, given “Check whether my existing Base RPC is ready; do not create a wallet,” load the readiness reference, run its bounded chain and freshness check, and report the observed chain ID and block time. A response from a different chain or a stale node is a failed readiness check even when the connection succeeds. If the endpoint is missing, identify the required environment setting without requesting its secret value in chat.

Record the runtime/profile, provider, chain ID, tool or CLI version, authentication state, successful read with timestamp, and remaining limitation. For a signer also record its owner, active account, supported actions, spending/contract/chain limits, expiry and revocation path. Report unknown permission enforcement as unknown, rather than treating a prompt as a wallet policy.

A missing dependency or expired session should produce the exact relevant setup step. Authentication that creates an account, wallet, signer session or new spending permission requires the user's authorization for that action; installing a skill does not provide it. Preserve existing authorization when its scope still matches.

After onboarding, hand the verified chain/account/capabilities to the requested protocol, portfolio, payments, governance or data workflow if present. This pack supplies infrastructure procedures and diagnostics; it does not execute a trade, fund a wallet or implement a signer.

Named provider procedures

For Coinbase AgentKit readiness, use galleon-coinbase-agentkit-readiness when installed. This generic skill remains independently usable for setup and cross-provider work.