cli-auth-telegramlisted

# CLI Auth via Telegram Use this skill whenever a user chatting over Telegram asks to connect, sign in, authenticate, or reconnect one of the CLI authentication flows covered here: Claude, Codex, Agy (Antigravity), or Grok Build. Do not use it for platform-account or billing login questions unrelated to these CLI credentials. ## Before you start 1. Confirm which CLI the user means. If ambiguous, ask — do not guess. 2. Check whether it is already authenticated by testing for its credential file before doing anything else: - Claude: `~/.claude/.credentials.json` - Codex: `~/.codex/auth.json` - Agy: `~/.gemini/antigravity-cli/antigravity-oauth-token` (fall back to `~/.gemini/oauth_creds.json` only if the primary file is absent) - Grok Build: `~/.grok/auth.json` (also accept `~/.config/grok/auth.json`, which Agent Bridge retains as a compatibility path) If the file exists and is non-empty, tell the user it looks already connected and ask whether they want to re-authenticate anyway before proceeding. For Grok, a non-empty `XAI_API_KEY` is only a candidate automation credential, not proof that Grok is connected. Agent Bridge's shared API-key auth path verifies it with a bounded native headless request before routing. Never print the value. If the user asked to connect their own Grok account, continue with device authentication instead of substituting the operator key. 3. Resolve the CLI binary with `command -v <cli>` (`claude`, `codex`, `agy`, or `grok`) rath