ProxyClaw

ProxyClaw by IPLoop — Residential proxy access for AI agents. Route requests through 175M+ residential IPs across 195+ countries from real Android, Windows,...

This skill appears to do exactly what it says: route requests through IPLoop's residential proxies using curl and a single API key. Before installing/using it: 1) Treat IPLOOP_API_KEY as sensitive — avoid putting it in persistent shell profiles; prefer session-scoped exports or a secrets manager. 2) Be aware the proxy authentication (password) is sent to the proxy in plaintext and curl args may be visible to other users on the same host via process listings. 3) The service is designed for scraping and geo-targeting; ensure your usage complies with target sites' Terms of Service and applicable law. 4) Note the minor inconsistency between fetch.sh and setup.sh in how they supply proxy credentials (empty username vs 'user'); functionally both are plausible but you may want to standardize. 5) The registry metadata lacks a verified homepage entry — if you need stronger provenance, verify the upstream project (iploop.io / GitHub) before trusting long-term credentials or giving the skill autonomous, repeated access.

Type: OpenClaw Skill Name: proxyclaw Version: 2.4.8 The ProxyClaw skill bundle provides a legitimate interface for routing web requests through the IPLoop residential proxy service. The core logic in `fetch.sh` and `setup.sh` is transparent, featuring proper input validation for URLs and country codes, and includes proactive security warnings regarding the visibility of API keys in process listings. While the bundle mentions an optional Docker image for bandwidth sharing (a common but high-risk activity), the skill's code itself contains no evidence of data exfiltration, malicious execution, or harmful prompt injection.