Sign up
← all tools

cc-skill:supabase-migration-patterns

Claude Code skill · anthropic · active

0
last 30 days
0 calls
0 of 30 days active
explain like I am new to this
what it does

This skill generates Supabase database migrations that follow Jay's proven patterns. It creates idempotent SQL files with proper naming, tables with the right column types, row-level security policies, and indexes in one shot.

who it is for

Developers working on Jay's projects who need to create or modify Supabase database schemas without making common mistakes.

when it fires

When you mention Supabase migrations, creating tables, altering schemas, RLS policies, Postgres extensions, or any database structure changes.

say something like
  • "Write a Supabase migration to create a users table with RLS"
  • "Add a new column to the content_assets table using Supabase migration patterns"
  • "Create a migration that sets up RLS policies for a Clerk multi-user app"
what you might get back
A timestamped SQL file like `20260430120000_create_content_assets.sql` containing a CREATE TABLE statement with UUID primary key, TIMESTAMPTZ fields, JSONB metadata column, enabled RLS, appropriate indexes, and an auto-update trigger. The file is idempotent and ready to run locally first.
how to know it worked

The generated migration file has the correct timestamp format, uses IF NOT EXISTS clauses, includes RLS enabled, has sensible indexes on queryable columns, and is structured as append-only SQL that can safely run multiple times.

is this skill working for me
never used
cloud runs
0
0 deployments
local fires
0
Claude Code (optional)
posts published
0
from drafts
attributed
$0.00
signups + revenue
Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/supabase-migration-patterns/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when writing Supabase migrations, creating tables, altering schemas, defining RLS policies, or working with Postgres extensions in Jay's projects. Triggers on "Supabase migration", "create table", "alter table", "RLS policy", "Postgres

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/supabase-migration-patterns/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity
never used
2026-04-03today
cost model
unitincluded
capabilities
{
  "source": "global",
  "description": "Use this skill when writing Supabase migrations, creating tables, altering schemas, defining RLS policies, or working with Postgres extensions in Jay's projects. Triggers on \"Supabase migration\", \"create table\", \"alter table\", \"RLS policy\", \"Postgres migration\", \"schema change\", \"add column\", or any database structure work. Applies Jay's conventions for naming, defaults, indexes, and idempotency."
}
how it gets called
{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/supabase-migration-patterns/SKILL.md"
}
This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.