brave-setup
Skill0 starsChanged 7 days agoMITView on GitHub
Install the baa CLI, initialize its XDG workspace, verify prerequisites, and troubleshoot common Brave automation failures on Linux.
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
- account-managerSkill
- 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
Brave Setup (baa init)
You get the baa CLI running on a Linux host: install the CLI from the
tools/ project, initialize the XDG workspace, and repair common failures.
Profile provisioning, credential import/export, and Google session scripting
belong to the sibling account-manager and password-manager skills.
Rules
| ID | Rule | Why | Check |
| R1 | Linux + Chromium only. Confirm the host before running anything. | Unsupported platforms produce opaque errors. | uname -s returns Linux; Brave (native, Flatpak, or Snap) is installed. |
| R2 | Never use /tmp for state. Logs and sessions live under $XDG_STATE_HOME/baa and $XDG_DATA_HOME/baa; a reviewer must find output there. | XDG compliance; state survives across runs. | baa init output shows XDG paths; no writes to /tmp. |
| R3 | One workspace per host. baa init is idempotent; re-running it re-detects install paths without clobbering existing state. | Re-detection after a Brave move or upgrade. | baa init exits 0 and XDG dirs exist under $XDG_STATE_HOME/baa. |
| R4 | Verify with baa --help and baa profile list after install/init. A silent install that leaves the console script unresolvable is the main failure mode. | Catch drift between package install and CLI surface early. | Both commands print their trees; no ModuleNotFoundError. |
Routing
| File | Purpose |
references/install.md | Install the baa CLI from the tools/ project with uv and verify the console scripts. |
references/init.md | Initialize the XDG state/data workspace and configure profile.csv / passwords.csv. |
references/troubleshooting.md | CDP connection failures, Local State locks, Safe Storage key rotation, XDG path issues. |
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.