supabase-production-auditor
Skill7 starsChanged 7 days agoMITView on GitHub
Audit Supabase projects for production security, row level security, authentication, storage policies, service-role usage, Edge Functions, database design, indexes, performance, Realtime scaling, multi-tenancy, AI application data risks, cost, backups, observability, and production readiness. Use before launching SaaS, marketplaces, AI apps, mobile apps, internal tools, ecommerce, and learning platforms on Supabase.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- letscooktech-studio/ai-engineering-arsenalword for word, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- letscooktech-studio/ai-engineering-arsenal★ 7100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agentic-skill-pack-integratorSkill
- ai-agent-architecture-reviewerSkill
- ai-search-optimizerSkill
- competitor-analyzerSkill
- cost-explosion-detectorSkill
- cto-operating-systemSkill
- database-architectSkill
- nextjs-production-architecture-reviewerSkill
- nvidia-accelerated-ai-systems-operatorSkill
- production-ai-saas-builderSkill
- production-risk-labSkill
- security-auditorSkill
- seo-auditorSkill
- startup-validatorSkill
- system-architectSkill
- technical-debt-hunterSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 28
Every finding must include evidence, risk, affected asset, impact, fix, and verification.
- Distinctive: line 32
Do not approve production readiness without RLS coverage, backup posture, migration safety, secret handling, monitoring, and incident …
- Very specific: line 33
Do not recommend broad policies such as true predicates without explaining exact access scope.
- Distinctive: line 35
Treat service-role exposure, tenant leakage, and public bucket misuse as high-risk until proven safe.
≈ “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
Supabase Production Auditor
Developed by the LetsCookTech Open Source Team.
Apply the shared OutcomeLab skill standard for evidence, verification, risk, benchmarking, and improvement.
Audit Supabase as a production data, auth, storage, and operations system. Detect RLS weaknesses, data exposure, cost blowups, scalability limits, and operational gaps before deployment.
Workflow
- Classify the app type, expected scale, data sensitivity, tenancy model, auth flows, storage usage, Realtime usage, Edge Functions, and AI/RAG data patterns.
- Inventory database schemas, migrations, tables, constraints, indexes, policies, functions, storage buckets, API usage, service-role locations, and environment variables.
- Audit RLS coverage, policy logic, tenant isolation, anonymous/authenticated access, admin paths, service-role usage, and privilege escalation risks.
- Audit auth, storage, API, Edge Functions, Realtime, performance, backups, observability, migrations, cost, and disaster recovery.
- Red-team data theft, storage abuse, RLS bypass, bandwidth abuse, admin escalation, cost attacks, and growth failure.
- Score database design, security, RLS, auth, storage, API security, performance, Realtime, scalability, cost efficiency, production readiness, and maintainability.
- Produce prioritized fixes with SQL/policy direction, verification queries, operational owners, and 30/90-day remediation.
Output contract
Return executive summary, production readiness assessment, critical/high/medium/low findings, RLS findings, authentication findings, storage findings, performance findings, scalability findings, cost findings, production operations findings, recommended fixes, verification checks, 30-day remediation plan, and 90-day improvement plan.
Every finding must include evidence, risk, affected asset, impact, fix, and verification.
Quality gates
- Do not approve production readiness without RLS coverage, backup posture, migration safety, secret handling, monitoring, and incident recovery checks.
- Do not recommend broad policies such as
truepredicates without explaining exact access scope. - Flag missing artifacts as review gaps instead of guessing policy behavior.
- Treat service-role exposure, tenant leakage, and public bucket misuse as high-risk until proven safe.
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.