What problem does it solve? Integrating OAuth 2.0 social sign-in (Google, GitHub, Facebook, GitLab, LINE, Kakao, Naver) into a Weegloo product requires knowing the exact auth.weegloo.com endpoints, the token exchange flow, and pitfalls like the entry-URL vs redirect-URI confusion — this Skill provides the complete implementation layer so sign-in works on the first attempt. ## Core Features & Use Cases - OAuth Wire Protocol: Documents the exact HTTP endpoints on auth.weegloo.com for login entry, token exchange, refresh, and logout, usable from any HTTP client. - Browser SDK Integration: Covers the weegloo-service-user npm package with login redirect, callback handling, token storage, auto-refresh, and exchangeToken URL-stripping. - Native App Path: Explains registering deep links in allowedCallbackUrls and driving the flow with redirect_uri plus PKCE for Android and iOS apps. - Use Case: You are building a web app on a Weegloo Space and need "Sign in with GitHub" — this Skill walks you through creating the ServiceLogin, registering the provider redirect URI, and wiring the SDK callback page. ## Quick Start Add Weegloo ServiceLogin sign-in with the appropriate OAuth provider to my browser app using the weegloo-service-user SDK.