What problem does it solve? When an Overlens IDP integration fails with a cryptic status code — a 401 on token exchange, a 429 rate limit, a cookie that never gets set, or CORS that works locally but breaks in production — developers waste hours guessing. This Skill maps each symptom (status code, error field, response headers) directly to its known cause and fix. ## Core Features & Use Cases - Symptom-to-cause master table: Maps 401 invalid_client, 400 invalid_grant, 400 invalid_redirect_uri, 404 on Google login, 429 rate limits, Max-Age=0 cookies, and CORS failures to precise root causes and fixes. - Diagnostic recipes: Copy-paste curl and browser commands to capture the exact status code, JSON error field, and response headers before attempting any fix. - Production-only failure checklist: A prioritized walkthrough for the classic "works locally, breaks in prod" scenario covering env vars, CORS origins, cookie domains, and redirect URI registration. - Use Case: A developer gets 401 invalid_client on /auth/token after deploying. The Skill identifies a malformed Authorization: Basic header or an empty IDP_CLIENT_SECRET env var in production and provides the base64 verification command to confirm it. ## Quick Start Ask the assistant why your Overlens login returns a 401 invalid_client error on the token endpoint and have it diagnose the cause.
