fuego_skill

Overview

This skill provides a local Solana agent wallet and infrastructure for building, signing, and submitting transfers (SOL, USDC, USDT), performing Jupiter token swaps, and completing x402 purchases. It runs a localhost server and a CLI that keep private keys on your machine while exposing simple API endpoints for agent integration. The design favors local signing and predictable transaction building to support secure, automated agent workflows.

How this skill works

The CLI and local server build unsigned transactions with fresh blockhashes and return base64 payloads plus memos. Clients sign transactions locally using the wallet JSON and then call the server to submit the signed transaction to mainnet. Jupiter swaps require an API key configured in the local config; x402 purchases use a deliberate server-side signing step to satisfy external proof-of-payment requirements while minimizing key exposure.

When to use it

• When an agent needs to send SOL, USDC, or USDT from a local, agent-controlled wallet.
• When an agent must execute token swaps via Jupiter with pre-checkable quotes and slippage control.
• When integrating agents that must build transactions remotely but sign locally for security.
• When an agent must programmatically purchase items via x402/Purch.xyz and requires server-assisted signing.
• When you want a localhost-only wallet server compatible with common agent runtimes and CLI subprocess calls.

Best practices

• Keep wallet files permissioned (chmod 600) and back up the wallet-config and backup JSON to secure storage.
• Use the CLI for most workflows (fuego send, quote, swap) to get consistent error handling and explorer links.
• Always fetch and show a swap quote before executing to confirm price impact and route details.
• Limit x402 usage and audit logs because it performs one-time server-side signing for purchase flows.
• Run the server on localhost and firewall the machine to prevent remote access; treat the host as the security boundary.

Example use cases

• A shopping agent builds an x402 purchase request, triggers the local flow, and receives a confirmed on-chain purchase signature.
• A payout agent builds SPL token transfers, signs them locally, and submits them via the fuego server for mass disbursements.
• A trading agent queries Jupiter quotes, shows them to a user or decision logic, then executes swaps with slippage tolerance.
• A monitoring agent checks SOL, USDC, and USDT balances via the tokens endpoints to decide when to refill or pause operations.