adspower-browser
v1.0.9Manages AdsPower browser profiles, groups, and proxies via the adspower-browser CLI. Requires AdsPower desktop application to be already installed. Uses only...
⭐ 1· 472·0 current·0 all-time
byAdsPower Official@adspower
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the instructions and referenced docs: the skill only documents using the adspower-browser CLI and AdsPower Local API. No unrelated credentials, services, or binaries are requested.
Instruction Scope
SKILL.md stays within AdsPower/profile/proxy management and includes explicit guardrails (require AdsPower installed, check-status before use, present launch commands with --api-key to user). Minor inconsistency: the docs list API_KEY as settable via environment or flag, but guardrails emphasize the key must be explicitly provided by the user each session and not cached — this should be clarified (see user guidance).
Install Mechanism
No install spec or code is included; this skill is instruction-only and does not download or write code. It delegates install/usage to the user (npm package and AdsPower desktop app).
Credentials
No required environment variables are declared. The skill documents optional PORT and an API_KEY used only when AdsPower runs headless. Requesting an API key is proportionate, but the docs simultaneously allow env-based API_KEY and mandate explicit user-provisioning each session — a small tension that should be resolved in favor of explicit interactive input.
Persistence & Privilege
always:false and default invocation behavior. The skill does not request persistent system-wide privileges or modify other skills; it instructs user-driven launching of AdsPower and requires confirmation for privileged commands.
Assessment
This is an instruction-only skill that expects AdsPower (desktop) and the adspower-browser npm CLI to already be installed. It does not auto-install code. Before using: verify the npm package and AdsPower download URLs yourself; ensure AdsPower's Local API is reachable (adspower-browser check-status); do not store your AdsPower API key in logs or long-lived files. The skill mentions API_KEY can be set via environment, but its guardrails require you to provide the key explicitly each session — prefer entering the key interactively rather than relying on env vars to avoid accidental reuse or leakage. Confirm any launch command containing --api-key before running, and only allow the agent to run commands after you see the full command and explicitly approve it. Finally, be aware of the operational risk: AdsPower automates browsers, proxies, and fingerprinting features — only use it with accounts and systems you control and trust.Like a lobster shell, security has layers — review code before you run it.
latestvk972zaedf5dwg8qrgzxwsg2hcn82v17s
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
OSLinux · macOS · Windows