supabase-operations
Skill0 starsChanged 3 months agoMITView on GitHub
Design, deploy, and operate Supabase projects with explicit schema, migration, security, backup, and observability checks. Use for Supabase architecture, Postgres changes, auth, storage, edge functions, or deployment operations.
In this repository5 other files it gives its agents.
- code-intelligenceSkill
- engineering-deliverySkill
- engineeringSkill
- skill-security-auditSkill
- video-workbenchSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Prefer local or staging validation and repository migration history.
≈ “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 Operations
This TIKAZ Edition is designed, integrated, refactored, and continuously maintained by TIKAZ. Supabase documentation and the target project's migration history remain the source of truth.
Inputs and workflow
Inspect the existing schema and deployment model first. Plan reversible migrations, indexes, RLS policies, auth flows, storage rules, backups, environment separation, and rollback. Never expose service-role keys or production secrets. Validate migrations, permissions, representative queries, and application integration before declaring completion.
Output contract
Return the schema or operational change, migration order, RLS and permission impact, backup and rollback plan, validation queries, environment target, and remaining risk.
Validation and fallback
Prefer local or staging validation and repository migration history. If credentials or a safe target are unavailable, produce a reviewed migration plan without applying it. Never infer production success from local SQL alone.
Example and limits
Use supabase-operations to plan this schema and RLS change, validate it in the available non-production environment, and provide rollback SQL.Production migrations, destructive SQL, secret rotation, and billing changes require explicit authority.
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.