agentleFS
Sign inStart free
matthewdonsemail-labmatthewdonsemail-lab/log/skills/adsPower/SKILL.md

adsPower

Skill63 starsChanged yesterdayMITView on GitHub

Give every account on a browser platform its AdsPower profile, give profiles back, check the Local API, and keep the browser-driver rules (rules 35, 44)

  • Reads credentials

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run sync --apply through Monitor (rule 26): it prints one line per account as it goes.

    line 42
  2. Very specific:

    Write a BrowserDriver (src/browser/driver/types.ts): prepare, gate, start, selfCheck, stop.

    line 49
  3. Very specific:

    Add its name to BROWSER_DRIVERS.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

adsPower

Hard boundaries

  1. Twenty stays the source. An AdsPower profile is the browser for one socialAccounts row, linked by adsPowerProfileId. The Twenty row is never deleted; a DEACTIVATED account, or one whose home is not in LOG_ADSPOWER_HOMES, gives its profile back (deleted from AdsPower, adsPowerProfileId cleared).
  2. No secret in AdsPower at rest. Profiles are made with no proxy, password or 2FA key. python/browser/browserDriver.py puts the proxy on only to open, after the gate, and clears it at close.
  3. Same as Camoufox (rule 44). An AdsPower session goes through the same gate and self-check (rule 35), session HAR (rule 19), human mouse and scroll. docs/browsers.md lists what's built; bun run check:browsers keeps every browser in step.
  4. Camoufox stays. With browserDriver empty, an account with a linked profile opens on AdsPower and one without opens on Camoufox. Never remove it.
  5. Never print ADSPOWER_API_KEY. It lives in .env.local and the local-scope MCP config.

Environment

  • The AdsPower app is running here: log adsPower status says "up".
  • .env.local has ADSPOWER_HOST (default http://local.adspower.net:50325) and ADSPOWER_API_KEY.
  • AdsPower's MCP server (adspower-local-api) is added at local scope. AdsPower's own skill is reinstalled with npx skills add https://github.com/adspower/adspower-browser --skill adspower-browser (vendor kebab-case names, git-ignored by rule 1).

Commands

log adsPower status                 # the Local API answers
log adsPower profiles               # AdsPower's profiles, and the Twenty account of each
log adsPower sync                   # dry run: release / create / relink / linked / skip per account
log adsPower sync --apply           # give back DEACTIVATED and out-of-home profiles, make the missing ones, link them in Twenty
log adsPower sync --apply --homes US  # this run's homes (default LOG_ADSPOWER_HOMES)
log adsPower sync --apply --account <accountName>

Run sync --apply through Monitor (rule 26): it prints one line per account as it goes. A skip is a banned or dead account, one with no home country in HOME_COUNTRIES, or one outside the homes that holds no profile. What the sync must do: docs/specs/adsPower.md. A failed create usually means the plan's profile limit: the AdsPower plan must hold at least as many profiles as accounts.

Adding another browser

Write a BrowserDriver (src/browser/driver/types.ts): prepare, gate, start, selfCheck, stop. Add its name to BROWSER_DRIVERS. The machine already enforces the order, so the new browser can't skip the gate or the self-check. Details: docs/adsPower.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free