← ClaudeAtlas

infolobbylisted

Use when the user wants to read, query, or modify their InfoLobby workspace data — list spaces and tables, get a table schema, create/update/delete/query records, post comments, or upload/download record attachments. Requires the user's InfoLobby API key, which the skill prompts for once and caches at ~/.infolobby/key.
andreas-globi/infolobby-skill · ★ 0 · Data & Documents · score 75
Install: claude install-skill andreas-globi/infolobby-skill
# InfoLobby Access an InfoLobby account from any agent using plain `curl`. No SDK. ## Setup The API key lives at `~/.infolobby/key` (one line, the raw token). **On every invocation**, first try to read it: ```bash INFOLOBBY_KEY="$(cat ~/.infolobby/key 2>/dev/null)" INFOLOBBY_API="https://infolobby.com/api" ``` If `~/.infolobby/key` does not exist, ask the user once for their InfoLobby API key (`il_live_…` or `il_user_…`), then write it. Do not log or echo the key back. - macOS / Linux: ```bash mkdir -p ~/.infolobby ( umask 077 && printf '%s' "<KEY>" > ~/.infolobby/key ) ``` - Windows (PowerShell): ```powershell New-Item -ItemType Directory -Force "$HOME\.infolobby" | Out-Null Set-Content -NoNewline "$HOME\.infolobby\key" '<KEY>' ``` Where the user gets a key: - **Account key** (`il_live_…`): InfoLobby → **Account → API Keys**. Account-owner only. Acts as the owner across all in-scope workspaces. - **Personal key** (`il_user_…`): InfoLobby → **Profile → Personal API Keys**. Acts as that user; cannot manage workspaces or table schemas. Send the key on every request as `Authorization: Bearer $INFOLOBBY_KEY`. ## Scope This skill covers data work only: - discover: list spaces, list tables, fetch a table schema - records: create, get, update, delete, batch-delete, **query with filters / saved views** - comments: list, post, attach files - files: upload, download, delete record attachments (base64 in JSON, 50 MB cap) This skill does **not** create/modif