Solana Easy Swap

Swap any Solana token from chat. Say 'swap 1 SOL for USDC' and it handles everything — quoting, signing, sending, confirming. No API keys, no wallet extensions, no setup beyond a keypair. Powered by Jupiter. Use when a user wants to swap, trade, exchange, buy, or sell Solana SPL tokens, SOL, USDC, memecoins, or any token pair on Solana.

This skill is internally consistent and appears to be what it claims: it will read the keypair file you point it to, query Jupiter, build and sign transactions, and submit them to your chosen Solana RPC. That is expected behavior for an on-device swap tool, but be aware of the security implications: granting SOLANA_KEYPAIR_PATH means the skill (when run) can sign/spend from that wallet. Only use a keypair you trust the skill to access (consider a dedicated low-balance wallet for testing). Review the script (scripts/swap.mjs) yourself before installing, keep npm installs isolated (use a container or VM if unsure), and ensure the agent prompts you and never executes swaps without your explicit confirmation. If you need higher assurance, use a hardware wallet or a workflow that never exposes private key material to third-party code.

Type: OpenClaw Skill Name: solana-easy-swap Version: 1.0.1 This skill is designed to facilitate Solana token swaps and appears benign. It transparently declares its need to access the user's Solana keypair via `SOLANA_KEYPAIR_PATH` for signing transactions, and explicitly states it does not create, import, or manage keys. The `SKILL.md` and `examples/agent-prompt.md` files contain strong instructions for the AI agent to always seek explicit user confirmation before executing swaps, warn about high price impact, and never auto-retry failed on-chain transactions, indicating a focus on user safety and preventing prompt injection. The `scripts/swap.mjs` code uses standard Solana libraries, validates all user inputs (e.g., mint addresses, amounts), and stores temporary transaction data in a UUID-named file within a `.cache` directory, preventing path traversal or sensitive data exposure. No evidence of data exfiltration, unauthorized persistence, or other malicious intent was found.