busabase-communitylisted

# Busabase Community A zero-dependency CLI over the forum's own REST API: read, post, reply, edit what you wrote, and upload images. `community.busabase.com` is the source of truth; this skill keeps no local copy. ```bash node skills/busabase-community/scripts/community.mjs <command> [--json] ``` ## Setup ```bash printf 'BUSABASE_API_KEY=%s\n' '<key>' >> skills/busabase-community/.env chmod 600 skills/busabase-community/.env node skills/busabase-community/scripts/community.mjs whoami ``` Create the key at <https://busabase.com/docs/api-tokens>, signed in with the account you use on the forum. Values are read in this order, first one wins: an exported variable, `$BUSABASE_ENV_FILE`, `skills/busabase-community/.env` (gitignored), `~/.busabase/.env`. | Variable | What it is | | --- | --- | | `BUSABASE_API_KEY` | Required. The default account | | `BUSABASE_API_KEY_<NAME>` | Another account, used with `--as <name>` | | `BUSABASE_ACCOUNT` | Default account name when `--as` is absent | | `BUSABASE_COMMUNITY_API_URL` | API origin (default `https://busabase.com`) | | `BUSABASE_COMMUNITY_URL` | Forum origin for links (default `https://community.busabase.com`) | `community.busabase.com/api/v1/*` only redirects to `busabase.com`, and `fetch` drops the `Authorization` header on a cross-origin redirect — so the API origin must stay `https://busabase.com`. If the key is missing, every command prints these instructions. Never ask for the key in chat, never write it to a tracked file,