oauth-integration

Explain OAuth authentication flows and token management across provider integrations.

5|1|Updated Oct 14, 2025
One-click install
npx skills add https://github.com/seer-engg/seer --skill oauth-integration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oauth-integration
Source: https://github.com/seer-engg/seer/tree/main/.claude/skills/oauth-integration
Command: npx skills add https://github.com/seer-engg/seer --skill oauth-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Context about how OAuth authentication works in seer. Use when understanding OAuth flows, token management, scope validation, or debugging OAuth issues.

Core Features & Use Cases

  • Architecture overview and provider integration patterns for OAuth, including token exchange, scope handling, and lazy refresh.
  • Real-world use cases such as connecting Google, GitHub, Discord, LinkedIn, and Supabase providers, and managing user OAuth connections.

Quick Start

Initiate the OAuth connect flow for a provider, complete authorization, and store the resulting connection.

Frequently Asked Questions about oauth-integration

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

FAQPage Schema
How do OAuth authentication flows and token management work in Seer?▼

Yes, Seer supports OAuth provider integrations for Google, GitHub, Supabase, Discord, and LinkedIn. These integrations manage user OAuth connections by applying required scope handling and provider-specific API interactions during the token exchange process.

How do I initiate an OAuth connect flow for a provider?▼

To initiate an OAuth connect flow, you start the provider authorization process, complete the user authentication, and store the resulting connection. This flow relies on base64-encoded state for stateless callbacks to manage the token exchange.

What is lazy token refresh and how does it handle scope validation?▼

Lazy token refresh is a token management mechanism that updates authentication tokens on demand rather than proactively. Scope validation ensures that the requested authentication scopes match the required provider-specific API interactions during the token exchange.

Can I use base64-encoded state for stateless callbacks in OAuth token exchanges?▼

Yes, base64-encoded state is used for stateless callbacks during OAuth token exchanges. This approach allows the authentication flow to maintain state across the redirect without requiring server-side session storage for provider connections.

Why is my OAuth connection failing during provider-specific API interactions?▼

OAuth connection failures during provider-specific API interactions often stem from incorrect scope validation or improper token exchange parameters. Debugging requires verifying the lazy token refresh process and ensuring the base64-encoded state matches the stateless callback requirements.