Uniswap Setup Agent Wallet

Set up an agent wallet for Uniswap operations. Use when user needs to provision a wallet for an autonomous agent. Supports Privy (development), Turnkey (production), and Safe (maximum security). Configures spending limits, token allowlists, and funds the wallet for gas.

This skill wants to create, configure, and fund wallets — actions that need API keys, RPC endpoints, and a source wallet/private key. Before installing or enabling it, get answers to these questions: (1) Which exact environment variables or secrets will be required (provider API keys, RPC URLs, funding private key or source wallet)? (2) Where will secrets be stored and who has access? (3) How does the 'wallet-provisioner' subagent obtain/fund ETH/gas — does it require your private key or will you provide funding manually? (4) Where will the config file (.uniswap/agent-wallet.json) be written and what does it contain (avoid storing private keys there)? (5) Can spending limits and token allowlists be enforced on-chain (preferred) rather than relying on agent-side enforcement? If you cannot get clear, verifiable answers (ideally with explicit env var names and an audit of the provisioner), treat this skill as risky. For safe testing, use the Privy/dev mode on testnets with a throwaway funding account and never provide production private keys until you have audited the implementer and the delegated 'wallet-provisioner' agent.

Type: OpenClaw Skill Name: setup-agent-wallet Version: 0.1.0 The skill is designed to perform high-privilege operations, specifically provisioning and configuring cryptocurrency wallets, which inherently involves handling sensitive data and potentially accessing credentials (e.g., API keys from environment variables as indicated in SKILL.md). It delegates this task to a `wallet-provisioner` subagent, passing user-controlled parameters directly. While the skill itself does not contain explicit malicious code or prompt injection attempts, the sensitive nature of wallet management and the reliance on a subagent for execution introduce a significant attack surface. Any vulnerabilities in the `wallet-provisioner` subagent or improper sanitization of user inputs could lead to serious security risks, classifying it as suspicious due to the potential for exploitation of downstream vulnerabilities.