Sponge Wallet

Manages crypto wallets, transfers tokens, swaps on DEXes, checks balances, and accesses paid APIs (search, image gen, prediction markets, web scraping, document parsing, sales prospecting) via x402 micropayments. Use when the user asks about wallet balances, token transfers, swaps, blockchain payments, or paid API services.

What to consider before installing: - Trust boundary: this skill delegates wallet operations to a remote service (default API: https://api.wallet.paysponge.com). Anyone controlling that service or the API key can sign/submit transactions and perform micropayments. Only use it if you trust the provider and have verified their identity and policies. - Secrets: the skill uses an API key (SPONGE_API_KEY) and stores credentials at ~/.spongewallet/credentials.json. Do NOT put live/large-value keys into the environment or the skill until you vet the provider. Prefer testnet keys (sponge_test_*) when evaluating. - Transparency mismatch: the registry metadata declared no env vars/primary credential, but the code clearly uses SPONGE_API_KEY and SPONGE_API_URL. That omission reduces visibility — ask the publisher to correct the metadata before installing. - Automatic payments: paid-API calls (sponge/x402) default to auto_pay=true. If you do not want the skill to spend funds without explicit confirmation, set auto_pay to false or avoid using the sponge tool. Consider requiring manual payment signatures. - Data exfiltration risk: tasks like 'crawl', 'parse', and 'prospect' will send URLs, documents, or contact data to third-party providers (the sponge pipeline). Do not send sensitive documents or PII unless you understand where the data goes and have permission. - Practical checks: verify the code repository and API host (check GitHub repo/paysponge domain and who runs the service), audit the server-side policy for allowlisting/transfer approvals, and run the skill with test keys in an isolated environment first. If possible, require a least-privilege API key (read-only or limited signing scope) for evaluation. If you cannot verify the remote service or if you need strong local control over private keys, do not install or use live keys with this skill.

Type: OpenClaw Skill Name: sponge-wallet Version: 1.0.0 The skill is classified as suspicious due to its inherently high-risk capabilities, despite aligning with its stated purpose. It enables direct cryptocurrency transfers and swaps (`evm_transfer`, `solana_transfer`, `solana_swap`, `withdraw_to_main_wallet`), which carry significant financial risk. Furthermore, the `sponge` tool allows for web scraping (`task: "crawl"`), document parsing (`task: "parse"`), and sales prospecting (`task: "prospect"`) via external APIs, which could expose or process sensitive information. While these actions are explicitly declared functionalities, they represent broad permissions and powerful primitives that could lead to harm if the agent is compromised or misused. The `scripts/wallet.mjs` file also uses `execSync` for clipboard operations, a powerful primitive, though its use here appears benign with JSON-stringified input.