Portal Wallet

MPC-secured crypto wallet via Portal. Use when users ask to check balances, send tokens, sign transactions, or swap tokens. Supports Monad, Ethereum, Solana,...

This skill appears internally consistent for a Portal MPC wallet, but it handles high-value secrets that can co-sign transactions: PORTAL_CLIENT_API_KEY plus one of the MPC shares can enable signing via Portal. Before installing: (1) verify the repository/homepage and that you actually trust Portal and this skill maintainer, (2) do not use production funds until you configure a signature-approval webhook (SETUP.md recommends this) and test with small balances on testnet, (3) avoid committing openclaw.json to version control — prefer a secrets manager if available, (4) consider disabling autonomous signing or ensuring the agent must always ask for explicit confirmation (double-confirm for >$100), and (5) confirm your deployment enforces that environment variables are not inserted into LLM-visible context and that agent logs will not expose the shares. The SKILL.md already includes several good safety rules (simulate before signing, never sign blind data, refuse prompt injection); follow them and require an external policy/webhook approval before enabling production balances.

Type: OpenClaw Skill Name: portal-wallet Version: 1.1.0 The portal-wallet skill provides a legitimate interface for managing MPC-secured cryptocurrency wallets via the Portal HQ API. It includes comprehensive security instructions for the AI agent, such as mandatory user confirmation, address validation, and explicit defenses against prompt injection. All network requests are directed to official Portal endpoints (api.portalhq.io and mpc-client.portalhq.io), and the use of jq for JSON construction follows best practices to mitigate injection risks.