iblai-api-loginlisted

# iblai-api-login Connect an organization so the other `iblai-*` skills can call the ibl.ai platform. Every API call needs three things — your **org key**, your **username**, and a **Platform API Token** — and this skill collects all three and writes them to `.env`. Run it once per organization. ## What you are collecting | Value | Goes in `.env` as | Where it comes from | | ------------------ | ----------------- | ---------------------------------------------------- | | Org key | `IBLAI_ORG` | `login.iblai.app/me` → the **key** of the chosen org | | Username | `IBLAI_USERNAME` | `login.iblai.app/me` → account / profile | | Platform API Token | `IBLAI_API_KEY` | An Api-Token minted from the session — see step 2 | The base URL is fixed: `https://api.iblai.app`. Auth header on every request is `Authorization: Api-Token <IBLAI_API_KEY>`. ## Fastest path — org credentials (key + secret) If you already hold **organization credentials** — an **org key** and an **org secret** (issued for the org for automation/CI; the same pair the ibl.ai quickstarts use) — you can skip the browser entirely. The **org secret works directly as the Platform API Token**; there is nothing to mint: ```dotenv IBLAI_ORG=<org key> # e.g. acme IBLAI_API_KEY=<org secret> # used verbatim as: Authorization: Api-Token <secret> ``` The only value left is `IBLAI_USERNAME`. Read an admin username straight f