AdsPower profile operation via adspower-browser CLI. open/launch/start browser or profile, environment, config profile, AdsPower; create/update/delete/list profiles; groups, tags, proxies; kernel download/list; client patch; API check-status. User phrases like open environment or map to commands such as open-browser.
Detected risks:
This skill wraps the AdsPower `adspower-browser` command-line interface (installable via npm, with `adspower` and `ads` aliases) for operating AdsPower's anti-detect browser platform. It lets an assistant translate natural-language requests into concrete CLI commands to create, update, delete, and list browser profiles, open and close profile browsers, manage groups, tags, and proxies, download and list browser kernels, and check the local API status. It targets the AdsPower Local API (default port 50325) and supports both shorthand single-ID arguments and full JSON parameter forms.
Beyond basic profile management, the reference material documents extensive browser-fingerprint customization: custom or randomized user agents, canvas noise, WebGL vendor/renderer spoofing, timezone and geolocation overrides, language and screen-resolution settings, font lists, and even explicit TLS cipher-suite selection for the Chrome kernel. It also covers inline proxy configuration (HTTP/HTTPS/SOCKS5, third-party proxy providers, and per-profile proxy credentials). Authentication is handled through an official API key, passed with `--api-key` or the `ADS_API_KEY` environment variable, and headless launch is supported.
The intended users are people who legitimately manage many separate browser environments (multi-account operations, e-commerce, ad and social-media management, QA). However, the core purpose of the toolchain is browser-fingerprint and network anti-detection, which is dual-use: the same fingerprint spoofing, TLS-cipher customization, and proxy rotation that serve legitimate profile isolation can also be used to evade bot-detection and anti-fraud systems. The skill itself only documents and invokes the vendor's own CLI and does not exfiltrate data or install unofficial code.
Driving the AdsPower anti-detect browser through its adspower-browser CLI to manage profiles, groups, tags, proxies, and browser kernels, and to open or close profile browsers.
Install the CLI with npm (`npm install -g adspower-browser`), have the AdsPower client running (default port 50325), and provide an API key via `--api-key` or the ADS_API_KEY environment variable.
Either as a single shorthand value (one profile ID/number) or as a full JSON string of parameters, for example `ads open-browser '{"profile_id":"abc123"}'`.
User-agent, canvas, WebGL, timezone, geolocation, language, resolution, fonts, and Chrome TLS cipher suites, plus inline proxy configuration including third-party providers and SOCKS5.
Yes. AdsPower is anti-detect browser tooling. Fingerprint spoofing and proxy configuration are dual-use and can be misused to evade bot-detection or platform anti-fraud controls, so it should only be used within the target platforms' terms of service and applicable law.
Quick Setup:
.claude/skills/Repository
adspower/adspower-browser