weegloo-service-login-github

Guides GitHub OAuth App registration to obtain clientId and clientSecret for Weegloo ServiceLogin.

1|2|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-service-login-github-weeglooapi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weegloo-service-login-github
Source: https://github.com/weeglooapi/weegloo-mcp-plugin/tree/main/plugins/weegloo/skills/weegloo-service-login-github
Command: npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-service-login-github-weeglooapi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up GitHub as a social login provider for Weegloo ServiceLogin requires exact GitHub console steps, the correct Authorization callback URL, and the clientId/clientSecret pair — mistakes here silently break sign-in. This Skill provides the precise GitHub-side procedure so the agent can walk the user through it without errors. ## Core Features & Use Cases - GitHub OAuth App walkthrough: Step-by-step instructions for registering an OAuth App under a personal account or organization, including which form fields matter and which do not exist on GitHub (no consent screen, no scope field). - Callback URL guidance: Supplies the exact deploy-independent Authorization callback URL (https://auth.weegloo.com/v1/spaces/{spaceId}/login/oauth2/code/github) and explains GitHub's single-callback-URL limitation. - Credential collection flow: Directs the agent to stop and ask the user for the Client ID and Client Secret (shown only once by GitHub) instead of marking sign-in as done prematurely. - Use Case: A developer building a Weegloo-hosted app chooses GitHub login; the agent uses this Skill to tell the user the callback URL up front, hand them the illustrated walkthrough, collect the credentials, and create the ServiceLogin. ## Quick Start Set up GitHub as the OAuth provider for my Weegloo ServiceLogin and walk me through registering the GitHub OAuth App.

Frequently Asked Questions about weegloo-service-login-github

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up GitHub OAuth login for Weegloo ServiceLogin?

Register a GitHub OAuth App under Settings → Developer settings → OAuth Apps, set the Authorization callback URL to https://auth.weegloo.com/v1/spaces/{spaceId}/login/oauth2/code/github, then copy the Client ID and generate a Client Secret. Provide both values to create the ServiceLogin with provider github.

What callback URL should I register in my GitHub OAuth App?

Register https://auth.weegloo.com/v1/spaces/{spaceId}/login/oauth2/code/github with your real spaceId substituted. GitHub OAuth Apps allow exactly one callback URL, and this value is known before deployment since it depends only on auth.weegloo.com, your spaceId, and the github provider.

Why does GitHub sign-in fail with a private email address?

Weegloo reads the member email only from GitHub's /user endpoint, which returns null for accounts with a private email, aborting sign-in with error WGL422056. The user must set a public profile email in GitHub settings; this failure happens server-side and cannot be intercepted by the SDK.

Can I use this Skill for Google or Kakao login setup?

No, this Skill covers only the GitHub provider. Google, Facebook, GitLab, Kakao, Naver, and LINE each have their own dedicated provider skills because their console registration steps differ, even though the overall ServiceLogin shape is the same.

Where do I find the GitHub OAuth App client secret after creation?

On the OAuth App's settings page, click Generate a new client secret next to Client secrets. GitHub displays the secret value only once, so copy it immediately; if lost, generate a new secret and update the ServiceLogin configuration.