supabase-hosted-admin-oauth

Map nonstandard Supabase tokens and run hosted preflight checks before OAuth validation.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/pingqLIN/UniText --skill supabase-hosted-admin-oauth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase-hosted-admin-oauth
Source: https://github.com/pingqLIN/UniText/tree/main/runtime/skills/supabase-hosted-admin-oauth
Command: npx skills add https://github.com/pingqLIN/UniText --skill supabase-hosted-admin-oauth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams verify hosted Supabase admin OAuth readiness and ensure environment correctness before performing real sign-in tests, reducing false positives and misconfigurations.

Core Features & Use Cases

  • Normalize authentication context by mapping nonstandard token names to SUPABASE_ACCESS_TOKEN.
  • Separate hosted and local profiles and provide dedicated env templates to prevent accidental testing against the wrong environment.
  • Run a hosted preflight and compile a readiness report detailing what remains to be configured before real sign-in validation.

Quick Start

Run this skill to validate hosted Supabase admin OAuth readiness, map tokens to the hosted environment, and perform a preflight before real sign-in validation.

Frequently Asked Questions about supabase-hosted-admin-oauth

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

FAQPage Schema
How do I verify hosted Supabase admin OAuth readiness before testing?

Verify hosted Supabase admin OAuth readiness by running a preflight check that confirms hosted keys and admin email are present, ensuring the app points to the correct endpoints to prevent false validation errors.

Why does my Supabase OAuth validation return false positives during sign-in tests?

Supabase OAuth validation returns false positives when the app is pointed at local environments instead of hosted endpoints. Separating hosted and local profiles prevents accidental testing against the wrong environment.

How do I map nonstandard Supabase access tokens to the canonical environment variable?

Map nonstandard Supabase access tokens by renaming variables like SPB_Access_Token to the canonical SUPABASE_ACCESS_TOKEN. This normalizes the authentication context before running hosted preflight tests.

Does this preflight check separate hosted and local Supabase environments?

Yes, the preflight check identifies whether the repository uses hosted Supabase or local environments. It creates a dedicated hosted environment profile and reports local versus hosted status along with any configuration blockers.

What do I need to configure before attempting real Supabase OAuth sign-in validation?

Before real Supabase OAuth sign-in validation, you need to configure hosted keys and a verified admin email. A readiness report details exactly what remains to be configured to avoid misconfigurations during testing.