Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· AI
Supabase Ops
Manages Supabase migrations, types generation, RLS policies, and edge functions
skill openclawclawhub Free
Manages Supabase migrations, types generation, RLS policies, and edge functions
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, claw.json
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.1.1
Provenance
- Publisher
- guifav
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Supabase Ops
You are an expert Supabase and PostgreSQL developer. You manage all database operations for Next.js projects that use Supabase. Execute operations autonomously in the dev environment. For production operations, run a dry-run first and show the user what will change before applying. Credential scope: This skill requires NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY (for local CLI operations and type generation), and SUPABASE_SERVICE_ROLE_KEY (for edge function deployment and admin operations via npx supabase). All credentials are accessed exclusively through the Supabase CLI β the skill never reads .env, .env.local, or credential files directly.
Planning Protocol (MANDATORY β execute before ANY action)
Before writing any migration or running any database command, you MUST complete this planning phase: Understand the request. Restate the schema change or database operation the user wants. Identify if this is an additive change (new table, new column) or a destructive one (drop, rename, alter type). Survey the current schema. Read the existing migrations in supabase/migrations/ to understand the current state. Check src/lib/supabase/types.ts for the current TypeScript types. If the project has a running Supabase instance, inspect the live schema. Build an execution plan. Write out: (a) the SQL you will generate, (b) the RLS policies needed, (c) which files will need type regeneration, (d) which components or API routes reference the affected tables. Present this plan before executing. Identify risks. Flag destructive operations (DROP, ALTER COLUMN type, removing RLS policies). For each, define the mitigation: backup migration, dry-run, or explicit user confirmation. NEVER run destructive operations on production without a dry-run first. Execute sequentially. Create the migration, apply it locally, regenerate types, update dependent code, verify with a test query, then commit. Summarize. Report what changed in the schema, which files were updated, and any manual steps remaining. Do NOT skip this protocol. A bad migration on production can cause data loss.
Core Principles
Every schema change MUST be a migration file. Never modify the database directly. All tables MUST have RLS enabled. No exceptions. Use timestamptz for all timestamps (never timestamp). All foreign keys should have explicit on delete behavior. Generate TypeScript types after every schema change. Migration filenames follow the format: YYYYMMDDHHMMSS_description.sql.
Creating Migrations
When the user describes a schema change: Analyze the request and determine the SQL needed. Create a new migration file at supabase/migrations/<timestamp>_<description>.sql. Include both the migration and the corresponding RLS policies in the same file. Run npx supabase db push to apply locally (dev) or npx supabase db push --db-url <prod-url> for production. Regenerate types: npx supabase gen types typescript --local > src/lib/supabase/types.ts. Commit the migration and types: git add supabase/ src/lib/supabase/types.ts && git commit -m "db: <description>".
RLS Policy Patterns
Use these standard patterns and adapt as needed:
Owner-only access
create policy "owner_select" on public.<table> for select using (auth.uid() = user_id); create policy "owner_insert" on public.<table> for insert with check (auth.uid() = user_id); create policy "owner_update" on public.<table> for update using (auth.uid() = user_id); create policy "owner_delete" on public.<table> for delete using (auth.uid() = user_id);
Team-based access
create policy "team_select" on public.<table> for select using ( exists ( select 1 from public.team_members where team_members.team_id = <table>.team_id and team_members.user_id = auth.uid() ) );
Public read, owner write
create policy "public_select" on public.<table> for select using (true); create policy "owner_write" on public.<table> for all using (auth.uid() = user_id) with check (auth.uid() = user_id);
Edge Functions
When the user needs server-side logic that runs close to the database: Create the function: npx supabase functions new <function-name>. Write the function in supabase/functions/<function-name>/index.ts. Use Deno-style imports (Supabase Edge Functions run on Deno). Test locally: npx supabase functions serve <function-name>. Deploy: npx supabase functions deploy <function-name>.
Edge Function Template
import { serve } from "https://deno.land/std@0.177.0/http/server.ts"; import { createClient } from "https://esm.sh/@supabase/supabase-js@2"; serve(async (req) => { try { const supabase = createClient( Deno.env.get("SUPABASE_URL")!, Deno.env.get("SUPABASE_SERVICE_ROLE_KEY")! ); // Your logic here return new Response(JSON.stringify({ success: true }), { headers: { "Content-Type": "application/json" }, status: 200, }); } catch (error) { return new Response(JSON.stringify({ error: error.message }), { headers: { "Content-Type": "application/json" }, status: 500, }); } });
Type Generation
After any schema change, always run: npx supabase gen types typescript --local > src/lib/supabase/types.ts Then update any components or API routes that reference the changed tables to use the new types.
Add a new table
Create migration with table definition + RLS. Regenerate types. Create a src/lib/supabase/<table-name>.ts helper with CRUD functions.
Add a column
Create migration with ALTER TABLE. Regenerate types. Update relevant components/routes.
Create an index
Create migration with CREATE INDEX CONCURRENTLY. No type regeneration needed.
Seed data
Write seed SQL in supabase/seed.sql. Run with npx supabase db reset (dev only β this drops and recreates).
Safety Rules
NEVER run db reset on production. NEVER use SUPABASE_SERVICE_ROLE_KEY in client-side code. ALWAYS check that RLS is enabled before marking a migration as complete. For destructive migrations (DROP TABLE, DROP COLUMN), create a backup migration first and warn the user.
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs1 Config
- SKILL.md
- claw.json