account-manager
Skill0 starsChanged 7 days agoMITView on GitHub
Manage Brave browser profiles and Google sessions via the baa CLI: create, list, verify, and reset isolated accounts, plus scripted Google login, logout, and session checks.
In this repository75 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/skill-authoring/tools/AGENTS.mdAGENTS.md
- aes-docsSkill
- aes-fixSkill
- aes-layerSkill
- aes-migrationSkill
- android-emulator-linux-gpsSkill
- computer-useSkill
- flatpak-chromium-automationSkill
- qwen-webSkill
- grok-buildSkill
- hermes-agentSkill
- omnirouteSkill
- orcaSkill
- brave-setupSkill
- password-managerSkill
- codegraphSkill
- deep-cleanSkill
- dogfoodSkill
- reviewSkill
- systematic-debuggingSkill
- blender-arwakySkill
- comfyuiSkill
- llm-writingSkill
- vision-arwakySkill
- playwright-toolingSkill
- setup-ci-quality-gatesSkill
- statuslineSkill
- systemd-headless-serviceSkill
- xdg-spec-complianceSkill
- figcraft-builderSkill
- figcraft-iconsSkill
- figcraft-motionSkill
- figcraft-prototyperSkill
- figcraft-reviewSkill
- figcraftSkill
- figcraft-svgSkill
- figcraft-typographySkill
- github-authSkill
- issue-makerSkill
- issue-workerSkill
- mergifySkill
- pr-babysitSkill
- releasingSkill
- repo-managerSkill
- ascii-artSkill
- ascii-videoSkill
- gif-searchSkill
- media-acquisitionSkill
- docxSkill
- emailSkill
- google-workspaceSkill
- notionSkill
- pdfSkill
- pptxSkill
- xlsxSkill
- competitor-news-monitorSkill
- product-price-monitorSkill
- weekly-review-planningSkill
- arxivSkill
- The first 60 shown.
The file
Files
Account Manager (baa account)
You manage local Brave/Chromium accounts through the baa CLI: provision isolated
profiles from profile.csv into Chromium's Local State, verify what landed, and
script Google login, logout, and session checks per profile. Setup and
troubleshooting belong to the sibling brave-setup skill; credential import/export
belongs to the sibling password-manager skill.
Rules
| ID | Rule | Why | Check |
| R1 | Linux + Chromium only. Confirm the host before running anything; the shared taxonomy raises on other platforms. | Unsupported platforms produce opaque errors. | uname -s returns Linux; Brave (native, Flatpak, or Snap) is installed. |
| R2 | One profile per account. Each account gets its own named profile; never mix sessions or credentials across profiles. | Cross-profile leakage defeats the isolation model. | Each account maps to one profile name; no shared session storage. |
| R3 | profile.csv is the source of truth. Edit the CSV, then run the matching baa subcommand — never hand-edit Local State directly. | Manual edits are error-prone and not reproducible. | All profile changes go through baa profile ensure / create. |
| R4 | Verify after every write. A silent success that leaves a profile unregistered is the main failure mode. | Catch drift between CSV and live Chromium state early. | baa profile list shows every expected name after create/reset. |
| R5 | Google login first may trigger a challenge. A fresh profile can hit an email-link or app-password verification (SessionChallenge); resolve it once manually, then re-run login. | Google flags unknown profiles; re-running after resolution succeeds. | baa google session <name> reports a valid session after login. |
Routing
| File | Purpose |
references/create.md | create subcommand — provision one or more accounts from profile.csv with --profile, --email, --password. |
references/list.md | list subcommand — show every registered profile and which profile.csv entries are missing. |
references/google-login.md | login subcommand — Google login in a named profile with session persistence. |
references/google-logout.md | logout subcommand — drop the Google session for a profile. |
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
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.

