sc-supabase
Skill13 starsChanged 2 months agoMITView on GitHub
(STUB / NOT IMPLEMENTED YET) Supabase backend as an alternative to self-hosted Convex. Create project, apply migrations from supabase/migrations, deploy Edge Functions, generate types. For projects where Postgres + Row-Level-Security is a better fit than Convex's reactive query model.
- Reads credentials
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- si-coderSkill
- sc-allSkill
- sc-axSkill
- sc-buildSkill
- sc-cfSkill
- sc-clerkSkill
- sc-convex-cloudSkill
- sc-convexSkill
- sc-dokploySkill
- sc-dokuSkill
- sc-dxSkill
- sc-feSkill
- sc-gitSkill
- sc-helpSkill
- sc-installSkill
- sc-n8nSkill
- sc-onboardingSkill
- sc-providerSkill
- sc-resendSkill
- scSkill
- sc-skillSkill
- sc-stripeSkill
- sc-syncSkill
- sc-uiSkill
- sc-uxSkill
- sc-vercelSkill
- use-si-coderSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Write NEXT_PUBLIC_SUPABASE_URL + NEXT_PUBLIC_SUPABASE_ANON_KEY to project .env.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/sc-supabase — Supabase (STUB)
Status: boilerplate only.
When to use
- Project needs Postgres (relational, complex joins, mature SQL tooling) more than Convex's reactive model.
- Project wants Supabase Auth's social providers without self-hosting JWKS.
- Project already has Supabase migrations.
Scope when implemented
- Provision a new Supabase project via the Management API.
- Apply
supabase/migrations/*.sqlin order. - Deploy Edge Functions from
supabase/functions/. - Generate TypeScript types:
supabase gen types typescript. - Write
NEXT_PUBLIC_SUPABASE_URL+NEXT_PUBLIC_SUPABASE_ANON_KEYto project.env.
Env vars
| Var | Purpose |
SUPABASE_ACCESS_TOKEN | Personal token, https://supabase.com/dashboard/account/tokens |
SUPABASE_ORG_ID | Org to create projects under |
Suggested file layout
sc-supabase/
├── SKILL.md
└── scripts/
├── project.js # create + capture project ref + db password
├── migrate.js # apply migrations
├── functions.js # deploy edge functions
└── types.js # generate TS typesImplementation notes
- API base:
https://api.supabase.com/v1 - Auth:
Authorization: Bearer <SUPABASE_ACCESS_TOKEN> - Project creation returns a DB password ONCE — capture it directly into the selected Supabase named connection as a private one-time credential.
- For migrations, the
supabaseCLI may be required as a sub-process — wrap it inlib/supabase.js(TODO).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

