user-feedback: prefer Management API for auth provider configuration
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- supabase
- Domain
- documentation
Research direction
Start in SKILL.md sections “Supabase CLI” and “Supabase Documentation”; inspect the installed CLI with --help and consult the current Supabase Management API provider documentation. Done means the guidance prefers an API or CLI write when authorized credentials are available, uses dashboard steps only when needed, and verifies provider state without exposing secrets.
Written by the indexing model from the issue text.
Description
What happened
Task: Configure Sign in with Apple for a Supabase-backed native macOS app that also ships a Developer ID build using Apple web OAuth.
Skill said: The skill requires current documentation and CLI discovery, but it does not explicitly route hosted Auth provider configuration through the Supabase Management API when an access token and project reference are already available. This allowed the workflow to default too early to manual dashboard instructions.
Expected: For hosted Auth provider settings, first inspect the installed CLI and current provider documentation, then prefer a repeatable Management API or CLI write when credentials are available. Reserve dashboard instructions for operations the API and CLI do not expose. Verification should read back the live provider configuration without printing secrets.
Source
File: SKILL.md
Section: Supabase CLI and Supabase Documentation
Fix suggestion
Add an API-first routing rule for project configuration: discover CLI support with --help; if the CLI lacks the required hosted setting, check current Management API documentation and use it when the user has authorized credentials. For social-auth providers, read back enabled state, client IDs, callback host, and secret presence in redacted form. Use dashboard steps only for unsupported operations.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 208
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/agent-skills
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
supabase/agent-skills#586 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#585 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
supabase/agent-skills#583 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
supabase/agent-skills#582 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#581 ·
All issues in supabase/agent-skills
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100