[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M796GZKR0HFW37CNNND4VR4H":3,"skill-same:01M796GZKR0HFW37CNNND4VR4H":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M796GZKR0HFW37CNNND4VR4H","supabase-prod-checklist",null,"Execute Supabase production deployment checklist covering RLS, key hygiene,\nconnection pooling, backups, monitoring, Edge Functions, and Storage policies.\nUse when deploying to production, preparing for launch,\nor auditing a live Supabase project for security and performance gaps.\nTrigger with \"supabase production\", \"supabase go-live\",\n\"supabase launch checklist\", \"supabase prod ready\", \"deploy supabase\",\n\"supabase production readiness\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--supabase-pack--supabase-prod-checklist\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: supabase-prod-checklist\ndescription: |\n  Execute Supabase production deployment checklist covering RLS, key hygiene,\n  connection pooling, backups, monitoring, Edge Functions, and Storage policies.\n  Use when deploying to production, preparing for launch,\n  or auditing a live Supabase project for security and performance gaps.\n  Trigger with \"supabase production\", \"supabase go-live\",\n  \"supabase launch checklist\", \"supabase prod ready\", \"deploy supabase\",\n  \"supabase production readiness\".\nallowed-tools: Read, Write, Edit, Bash(npx supabase:*), Bash(curl:*), Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, supabase, deployment, production, security, rls]\n---\n\n# Supabase Production Deployment Checklist\n\n## Overview\n\nActionable 14-step checklist for taking a Supabase project to production. Covers RLS enforcement, key separation, connection pooling (Supavisor), backups\u002FPITR, network restrictions, custom domains, auth emails, rate limits, monitoring, Edge Functions, Storage policies, indexes, and migrations. Based on Supabase's official [production guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdeployment\u002Fgoing-into-prod).\n\n## Prerequisites\n\n- Supabase project on Pro plan or higher (required for PITR, network restrictions)\n- Separate production project (never share dev\u002Fprod)\n- `@supabase\u002Fsupabase-js` v2+ installed\n- Supabase CLI installed (`npx supabase --version`)\n- Domain and DNS configured for custom domain\n- Deployment platform ready (Vercel, Netlify, Cloudflare, etc.)\n\n## Instructions\n\n### Step 1: Enforce Row Level Security on ALL Tables\n\nRLS is the single most critical production requirement. Without it, any client with your anon key can read\u002Fwrite every row.\n\n```sql\n-- Audit: find tables WITHOUT RLS enabled\n-- This query MUST return zero rows before going live\nSELECT schemaname, tablename, rowsecurity\nFROM pg_tables\nWHERE schemaname = 'public' AND rowsecurity = false;\n```\n\n```sql\n-- Enable RLS on a table\nALTER TABLE public.profiles ENABLE ROW LEVEL SECURITY;\n\n-- Create a basic read policy (authenticated users see own rows)\nCREATE POLICY \"Users can view own profile\"\n  ON public.profiles\n  FOR SELECT\n  USING (auth.uid() = user_id);\n\n-- Create an insert policy\nCREATE POLICY \"Users can insert own profile\"\n  ON public.profiles\n  FOR INSERT\n  WITH CHECK (auth.uid() = user_id);\n\n-- Create an update policy\nCREATE POLICY \"Users can update own profile\"\n  ON public.profiles\n  FOR UPDATE\n  USING (auth.uid() = user_id)\n  WITH CHECK (auth.uid() = user_id);\n```\n\n- [ ] RLS enabled on every public table (zero rows from audit query above)\n- [ ] SELECT, INSERT, UPDATE, DELETE policies defined for each table\n- [ ] Policies tested with both authenticated and anonymous roles\n- [ ] No tables use `USING (true)` without intent (public read tables only)\n\n### Step 2: Enforce Key Separation — Anon vs Service Role\n\nThe `anon` key is safe for client-side code. The `service_role` key bypasses RLS entirely and must never leave server-side environments.\n\n```typescript\n\u002F\u002F Client-side — ONLY use anon key\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nconst supabase = createClient(\n  process.env.NEXT_PUBLIC_SUPABASE_URL!,\n  process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!  \u002F\u002F Safe for browsers\n);\n```\n\n```typescript\n\u002F\u002F Server-side only — service_role key (API routes, webhooks, cron jobs)\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nconst supabaseAdmin = createClient(\n  process.env.SUPABASE_URL!,\n  process.env.SUPABASE_SERVICE_ROLE_KEY!,  \u002F\u002F NEVER expose to client\n  { auth: { autoRefreshToken: false, persistSession: false } }\n);\n```\n\n- [ ] Anon key used in all client-side code (`NEXT_PUBLIC_` prefix)\n- [ ] Service role key used only in server-side code (API routes, Edge Functions)\n- [ ] Service role key not in any client bundle (verify with `grep -r \"service_role\" dist\u002F`)\n- [ ] Database password changed from the auto-generated default\n\n### Step 3: Configure Connection Pooling (Supavisor)\n\nSupabase uses Supavisor for connection pooling. Serverless functions (Vercel, Netlify, Cloudflare Workers) MUST use the pooled connection string to avoid exhausting the database connection limit.\n\n```\n# Direct connection (migrations, admin tasks only)\npostgresql:\u002F\u002Fpostgres:[PASSWORD]@db.[REF].supabase.co:5432\u002Fpostgres\n\n# Pooled connection via Supavisor (application code — USE THIS)\n# Port 6543 = Supavisor pooler (vs 5432 direct)\npostgresql:\u002F\u002Fpostgres.[REF]:[PASSWORD]@aws-0-us-east-1.pooler.supabase.com:6543\u002Fpostgres\n```\n\n```typescript\n\u002F\u002F For serverless environments — use pooled connection\nconst supabase = createClient(\n  process.env.SUPABASE_URL!,\n  process.env.SUPABASE_ANON_KEY!,\n  {\n    db: { schema: 'public' },\n    \u002F\u002F Supavisor handles pooling at port 6543\n    \u002F\u002F No need to configure pgBouncer settings in the client\n  }\n);\n```\n\n- [ ] Application code uses pooled connection string (port 6543)\n- [ ] Direct connection reserved for migrations and admin tasks only\n- [ ] Connection string in deployment platform env vars (not hardcoded)\n- [ ] Verified pool mode: `transaction` for serverless, `session` for long-lived connections\n\n### Step 4: Enable Database Backups\n\nSupabase provides automatic daily backups on Pro plan. Point-in-time recovery (PITR) enables granular restores.\n\n- [ ] Automatic daily backups enabled (Pro plan — verify in Dashboard > Database > Backups)\n- [ ] Point-in-time recovery configured (Dashboard > Database > Backups > PITR)\n- [ ] Tested restore procedure on a staging project (do not skip this)\n- [ ] Migration files committed to version control (`supabase\u002Fmigrations\u002F` directory)\n- [ ] `npx supabase db push` tested against a fresh project to verify migrations replay cleanly\n\n### Step 5: Configure Network Restrictions\n\nRestrict database access to known IP addresses. This prevents unauthorized direct database connections even if credentials leak.\n\n- [ ] IP allowlist configured (Dashboard > Database > Network Restrictions)\n- [ ] Only deployment platform IPs and team office IPs are allowed\n- [ ] Verified that application still connects after restrictions applied\n- [ ] Documented which IPs are allowed and why\n\n### Step 6: Configure Custom Domain\n\nA custom domain replaces the default `*.supabase.co` URLs with your brand domain for API and auth endpoints.\n\n- [ ] Custom domain configured (Dashboard > Settings > Custom Domains)\n- [ ] DNS CNAME record added and verified\n- [ ] SSL certificate provisioned and active\n- [ ] Application code updated to use custom domain URL\n- [ ] OAuth redirect URLs updated to use custom domain\n\n### Step 7: Customize Auth Email Templates\n\nDefault Supabase auth emails show generic branding. Customize them so users see your domain and brand.\n\n- [ ] Confirmation email template customized (Dashboard > Auth > Email Templates)\n- [ ] Password reset email template customized\n- [ ] Magic link email template customized\n- [ ] Invite email template customized\n- [ ] Custom SMTP configured (Dashboard > Auth > SMTP Settings) — avoids rate limits and improves deliverability\n- [ ] Email confirmation enabled (Dashboard > Auth > Settings)\n- [ ] OAuth redirect URLs restricted to production domains only\n- [ ] Unused auth providers disabled\n\n### Step 8: Understand Rate Limits Per Tier\n\nSupabase enforces rate limits that vary by plan. Hitting these in production causes 429 errors.\n\n| Resource | Free | Pro | Team |\n|----------|------|-----|------|\n| API requests | 500\u002Fmin | 1,000\u002Fmin | 5,000\u002Fmin |\n| Auth emails | 4\u002Fhour | 30\u002Fhour | 100\u002Fhour |\n| Realtime connections | 200 concurrent | 500 concurrent | 2,000 concurrent |\n| Edge Function invocations | 500K\u002Fmonth | 2M\u002Fmonth | 5M\u002Fmonth |\n| Storage bandwidth | 2GB\u002Fmonth | 250GB\u002Fmonth | Custom |\n| Database size | 500MB | 8GB | 50GB |\n\n- [ ] Rate limits documented for your plan tier\n- [ ] Client-side retry logic with exponential backoff for 429 responses\n- [ ] Auth email rate limits understood (use custom SMTP to increase)\n- [ ] Realtime connection limits planned for expected concurrent users\n\n### Step 9: Review Monitoring Dashboards\n\nSupabase provides built-in monitoring. Review these before launch to establish baselines.\n\n```typescript\n\u002F\u002F Health check endpoint — deploy this to your application\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nconst supabase = createClient(\n  process.env.SUPABASE_URL!,\n  process.env.SUPABASE_ANON_KEY!\n);\n\nexport async function GET() {\n  const start = Date.now();\n  const { data, error } = await supabase\n    .from('_health_check')  \u002F\u002F Create a small table for this\n    .select('id')\n    .limit(1);\n\n  const latency = Date.now() - start;\n\n  return Response.json({\n    status: error ? 'unhealthy' : 'healthy',\n    latency_ms: latency,\n    timestamp: new Date().toISOString(),\n    supabase_reachable: !error,\n  }, { status: error ? 503 : 200 });\n}\n```\n\n- [ ] Dashboard > Reports reviewed (API requests, auth, storage, realtime)\n- [ ] Dashboard > Logs > API checked for error patterns\n- [ ] Dashboard > Database > Performance Advisor reviewed and recommendations applied\n- [ ] Health check endpoint deployed and monitored (uptime service)\n- [ ] Error tracking configured (Sentry, LogRocket, etc.)\n- [ ] Alerts set for: error rate spikes, high latency, connection pool exhaustion\n\n### Step 10: Deploy Edge Functions with Proper Env Vars\n\nEdge Functions run on Deno Deploy. Environment variables must be set via the Supabase CLI or Dashboard, not hardcoded.\n\n```bash\n# Set secrets for Edge Functions\nnpx supabase secrets set STRIPE_SECRET_KEY=sk_live_...\nnpx supabase secrets set RESEND_API_KEY=re_...\n\n# List current secrets\nnpx supabase secrets list\n\n# Deploy all Edge Functions\nnpx supabase functions deploy\n\n# Deploy a specific function\nnpx supabase functions deploy process-webhook\n```\n\n```typescript\n\u002F\u002F supabase\u002Ffunctions\u002Fprocess-webhook\u002Findex.ts\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nDeno.serve(async (req) => {\n  const supabase = createClient(\n    Deno.env.get('SUPABASE_URL')!,\n    Deno.env.get('SUPABASE_SERVICE_ROLE_KEY')!  \u002F\u002F Available automatically\n  );\n\n  const body = await req.json();\n  \u002F\u002F Process webhook payload...\n\n  return new Response(JSON.stringify({ received: true }), {\n    headers: { 'Content-Type': 'application\u002Fjson' },\n  });\n});\n```\n\n- [ ] All Edge Functions deployed to production (`npx supabase functions deploy`)\n- [ ] Environment secrets set via `npx supabase secrets set` (not hardcoded)\n- [ ] `SUPABASE_URL` and `SUPABASE_SERVICE_ROLE_KEY` available automatically (no need to set)\n- [ ] Edge Functions tested with `npx supabase functions serve` locally before deploying\n- [ ] CORS headers configured for Edge Functions that receive browser requests\n\n### Step 11: Verify Storage Bucket Policies\n\nStorage buckets need explicit policies, similar to RLS on tables. Without policies, buckets are inaccessible (default deny).\n\n```sql\n-- Check storage bucket configurations\nSELECT id, name, public, file_size_limit, allowed_mime_types\nFROM storage.buckets;\n\n-- Check existing storage policies\nSELECT policyname, tablename, cmd, qual\nFROM pg_policies\nWHERE schemaname = 'storage';\n```\n\n```sql\n-- Example: Allow authenticated users to upload to their own folder\nCREATE POLICY \"Users can upload own files\"\n  ON storage.objects\n  FOR INSERT\n  WITH CHECK (\n    bucket_id = 'avatars'\n    AND auth.uid()::text = (storage.foldername(name))[1]\n  );\n\n-- Example: Allow public read access to a bucket\nCREATE POLICY \"Public read access\"\n  ON storage.objects\n  FOR SELECT\n  USING (bucket_id = 'public-assets');\n```\n\n- [ ] Each bucket has explicit SELECT\u002FINSERT\u002FUPDATE\u002FDELETE policies\n- [ ] Public buckets are intentionally public (not accidentally open)\n- [ ] File size limits set per bucket (`file_size_limit` in bucket config)\n- [ ] Allowed MIME types restricted per bucket (`allowed_mime_types`)\n- [ ] User upload paths scoped to `auth.uid()` to prevent overwrites\n\n### Step 12: Add Database Indexes on Frequently Queried Columns\n\nMissing indexes are the leading cause of slow queries after launch. Add indexes on foreign keys, filter columns, and sort columns.\n\n```sql\n-- Find missing indexes on foreign keys\nSELECT\n  tc.table_name, kcu.column_name,\n  CASE WHEN i.indexname IS NULL THEN '** MISSING INDEX **' ELSE i.indexname END AS index_status\nFROM information_schema.table_constraints tc\nJOIN information_schema.key_column_usage kcu\n  ON tc.constraint_name = kcu.constraint_name\nLEFT JOIN pg_indexes i\n  ON i.tablename = tc.table_name\n  AND i.indexdef LIKE '%' || kcu.column_name || '%'\nWHERE tc.constraint_type = 'FOREIGN KEY'\n  AND tc.table_schema = 'public';\n\n-- Find slow queries (requires pg_stat_statements extension)\nCREATE EXTENSION IF NOT EXISTS pg_stat_statements;\n\nSELECT query, calls, mean_exec_time::numeric(10,2) AS avg_ms,\n       total_exec_time::numeric(10,2) AS total_ms\nFROM pg_stat_statements\nORDER BY mean_exec_time DESC\nLIMIT 10;\n\n-- Check table bloat (dead tuples from updates\u002Fdeletes)\nSELECT relname, n_live_tup, n_dead_tup,\n       round(n_dead_tup::numeric \u002F greatest(n_live_tup, 1) * 100, 1) AS dead_pct\nFROM pg_stat_user_tables\nWHERE n_dead_tup > 1000\nORDER BY n_dead_tup DESC;\n```\n\n```sql\n-- Create indexes on commonly filtered columns\nCREATE INDEX idx_profiles_user_id ON public.profiles(user_id);\nCREATE INDEX idx_orders_created_at ON public.orders(created_at DESC);\nCREATE INDEX idx_posts_status ON public.posts(status) WHERE status = 'published';  -- Partial index\n\n-- Set query timeout for the authenticated role\nALTER ROLE authenticated SET statement_timeout = '10s';\n```\n\n- [ ] Indexes on all foreign key columns\n- [ ] Indexes on columns used in WHERE, ORDER BY, and JOIN clauses\n- [ ] `pg_stat_statements` enabled for ongoing query monitoring\n- [ ] Performance Advisor reviewed (Dashboard > Database > Performance)\n- [ ] `statement_timeout` set for authenticated role to prevent runaway queries\n- [ ] Table bloat checked — VACUUM if dead tuple percentage > 10%\n\n### Step 13: Apply Migrations with `npx supabase db push`\n\nAll schema changes must go through migration files, never manual Dashboard edits in production.\n\n```bash\n# Generate a migration from local changes\nnpx supabase db diff --use-migra -f add_indexes\n\n# Apply migrations to production (linked project)\nnpx supabase db push\n\n# Verify migration history\nnpx supabase migration list\n\n# If a migration fails, create a rollback\nnpx supabase migration new rollback_bad_change\n```\n\n- [ ] All schema changes in `supabase\u002Fmigrations\u002F` directory (version controlled)\n- [ ] `npx supabase db push` tested against a fresh project\n- [ ] Migration history matches between local and remote (`npx supabase migration list`)\n- [ ] Rollback migration prepared for risky schema changes\n- [ ] No manual schema edits in production Dashboard\n\n### Step 14: Pre-Launch Final Verification\n\n```bash\n# Verify RLS status one final time\nnpx supabase inspect db table-sizes --linked\n\n# Check that the project is linked to production\nnpx supabase status\n\n# Verify connection string works\nnpx supabase db ping --linked\n```\n\n- [ ] CORS settings match production domain (Dashboard > API > CORS)\n- [ ] Environment variables set correctly in deployment platform\n- [ ] Realtime enabled only on tables that need it (reduces connection usage)\n- [ ] Webhook endpoints registered and tested\n- [ ] Load test completed on staging (see `supabase-load-scale`)\n- [ ] SSL enforcement enabled (Dashboard > Database > Settings > SSL)\n- [ ] DNS and custom domain verified end-to-end\n\n## Output\n\n- All 14 checklist sections verified with zero unchecked items\n- RLS enforced on every public table with tested policies\n- Key separation verified (anon client-side, service_role server-side only)\n- Connection pooling via Supavisor (port 6543) for all application code\n- Backups, PITR, monitoring, Edge Functions, Storage policies, indexes all verified\n- Migrations applied cleanly via `npx supabase db push`\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| `403 Forbidden` on all API calls | RLS enabled but no policies created | Add SELECT\u002FINSERT\u002FUPDATE\u002FDELETE policies for each role |\n| `429 Too Many Requests` | Plan rate limit exceeded | Upgrade plan or implement client-side backoff with retry |\n| Connection timeout under load | Using direct connection in serverless | Switch to pooled connection string (port 6543) |\n| Auth emails not delivered | Default SMTP rate-limited | Configure custom SMTP provider (SendGrid, Resend, Postmark) |\n| `PGRST301` permission denied | Service role key used where anon expected | Check client initialization — use anon key for client-side |\n| Edge Function cold starts | First invocation after idle period | Pre-warm with scheduled pings or accept ~200ms cold start |\n| Storage upload fails | Missing bucket policy or size limit exceeded | Add INSERT policy and check `file_size_limit` on bucket |\n| Slow queries after launch | Missing indexes on filter\u002Fjoin columns | Run Performance Advisor and add indexes per Step 12 |\n| Migration conflicts | Manual Dashboard edits diverged from migration files | Run `npx supabase db diff` to capture drift, then commit |\n\n## Examples\n\n### Client Setup (Next.js)\n\n```typescript\n\u002F\u002F lib\u002Fsupabase\u002Fclient.ts — browser (anon key)\nimport { createClient } from '@supabase\u002Fsupabase-js';\nexport const supabase = createClient\u003CDatabase>(\n  process.env.NEXT_PUBLIC_SUPABASE_URL!,\n  process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!\n);\n\n\u002F\u002F lib\u002Fsupabase\u002Fserver.ts — server only (service role)\nexport const supabaseAdmin = createClient\u003CDatabase>(\n  process.env.SUPABASE_URL!,\n  process.env.SUPABASE_SERVICE_ROLE_KEY!,\n  { auth: { autoRefreshToken: false, persistSession: false } }\n);\n```\n\n### RLS Policy Pattern\n\n```sql\nALTER TABLE public.posts ENABLE ROW LEVEL SECURITY;\nCREATE POLICY \"Public read published\" ON public.posts\n  FOR SELECT USING (status = 'published');\nCREATE POLICY \"Authors manage own\" ON public.posts\n  FOR ALL USING (auth.uid() = author_id)\n  WITH CHECK (auth.uid() = author_id);\n```\n\n### Rollback\n\n```bash\nnpx supabase migration new rollback_bad_change  # Create reversal SQL\nnpx supabase db push                             # Apply rollback\n# For data: Dashboard > Database > Backups > PITR\n# For app: vercel rollback \u002F netlify deploy --prod\n```\n\nFor complete examples including health checks, storage policies, and Edge Functions, see [examples.md](references\u002Fexamples.md).\n\n## Resources\n\n- [Going to Production](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdeployment\u002Fgoing-into-prod) — Official production checklist\n- [Maturity Model](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdeployment\u002Fmaturity-model) — Project lifecycle stages\n- [Shared Responsibility Model](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdeployment\u002Fshared-responsibility-model) — What Supabase manages vs. what you manage\n- [Performance Advisor](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Finspect) — Built-in query analysis\n- [Connection Pooling](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fconnecting-to-postgres#connection-pooler) — Supavisor configuration\n- [RLS Guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fpostgres\u002Frow-level-security) — Policy patterns and examples\n- [Edge Functions](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Ffunctions) — Serverless Deno functions\n- [Storage](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fstorage) — File storage with policies\n- [`@supabase\u002Fsupabase-js` Reference](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fjavascript\u002Fintroduction) — Client SDK docs\n\n## Next Steps\n\n- For SDK version upgrades, see `supabase-upgrade-migration`\n- For load testing before launch, see `supabase-load-scale`\n- For monitoring in production, see `supabase-monitoring`\n- For Edge Function patterns, see `supabase-edge-functions`\n","# Supabase Production Deployment Checklist\n\n## Overview\n\nActionable 14-step checklist for taking a Supabase project to production. Covers RLS enforcement, key separation, connection pooling (Supavisor), backups\u002FPITR, network restrictions, custom domains, auth emails, rate limits, monitoring, Edge Functions, Storage policies, indexes, and migrations. Based on Supabase's official [production guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdeployment\u002Fgoing-into-prod).\n\n## Prerequisites\n\n- Supabase project on Pro plan or higher (required for PITR, network restrictions)\n- Separate production project (never share dev\u002Fprod)\n- `@supabase\u002Fsupabase-js` v2+ installed\n- Supabase CLI installed (`npx supabase --version`)\n- Domain and DNS configured for custom domain\n- Deployment platform ready (Vercel, Netlify, Cloudflare, etc.)\n\n## Instructions\n\n### Step 1: Enforce Row Level Security on ALL Tables\n\nRLS is the single most critical production requirement. Without it, any client with your anon key can read\u002Fwrite every row.\n\n```sql\n-- Audit: find tables WITHOUT RLS enabled\n-- This query MUST return zero rows before going live\nSELECT schemaname, tablename, rowsecurity\nFROM pg_tables\nWHERE schemaname = 'public' AND rowsecurity = false;\n```\n\n```sql\n-- Enable RLS on a table\nALTER TABLE public.profiles ENABLE ROW LEVEL SECURITY;\n\n-- Create a basic read policy (authenticated users see own rows)\nCREATE POLICY \"Users can view own profile\"\n  ON public.profiles\n  FOR SELECT\n  USING (auth.uid() = user_id);\n\n-- Create an insert policy\nCREATE POLICY \"Users can insert own profile\"\n  ON public.profiles\n  FOR INSERT\n  WITH CHECK (auth.uid() = user_id);\n\n-- Create an update policy\nCREATE POLICY \"Users can update own profile\"\n  ON public.profiles\n  FOR UPDATE\n  USING (auth.uid() = user_id)\n  WITH CHECK (auth.uid() = user_id);\n```\n\n- [ ] RLS enabled on every public table (zero rows from audit query above)\n- [ ] SELECT, INSERT, UPDATE, DELETE policies defined for each table\n- [ ] Policies tested with both authenticated and anonymous roles\n- [ ] No tables use `USING (true)` without intent (public read tables only)\n\n### Step 2: Enforce Key Separation — Anon vs Service Role\n\nThe `anon` key is safe for client-side code. The `service_role` key bypasses RLS entirely and must never leave server-side environments.\n\n```typescript\n\u002F\u002F Client-side — ONLY use anon key\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nconst supabase = createClient(\n  process.env.NEXT_PUBLIC_SUPABASE_URL!,\n  process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!  \u002F\u002F Safe for browsers\n);\n```\n\n```typescript\n\u002F\u002F Server-side only — service_role key (API routes, webhooks, cron jobs)\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nconst supabaseAdmin = createClient(\n  process.env.SUPABASE_URL!,\n  process.env.SUPABASE_SERVICE_ROLE_KEY!,  \u002F\u002F NEVER expose to client\n  { auth: { autoRefreshToken: false, persistSession: false } }\n);\n```\n\n- [ ] Anon key used in all client-side code (`NEXT_PUBLIC_` prefix)\n- [ ] Service role key used only in server-side code (API routes, Edge Functions)\n- [ ] Service role key not in any client bundle (verify with `grep -r \"service_role\" dist\u002F`)\n- [ ] Database password changed from the auto-generated default\n\n### Step 3: Configure Connection Pooling (Supavisor)\n\nSupabase uses Supavisor for connection pooling. Serverless functions (Vercel, Netlify, Cloudflare Workers) MUST use the pooled connection string to avoid exhausting the database connection limit.\n\n```\n# Direct connection (migrations, admin tasks only)\npostgresql:\u002F\u002Fpostgres:[PASSWORD]@db.[REF].supabase.co:5432\u002Fpostgres\n\n# Pooled connection via Supavisor (application code — USE THIS)\n# Port 6543 = Supavisor pooler (vs 5432 direct)\npostgresql:\u002F\u002Fpostgres.[REF]:[PASSWORD]@aws-0-us-east-1.pooler.supabase.com:6543\u002Fpostgres\n```\n\n```typescript\n\u002F\u002F For serverless environments — use pooled connection\nconst supabase = createClient(\n  process.env.SUPABASE_URL!,\n  process.env.SUPABASE_ANON_KEY!,\n  {\n    db: { schema: 'public' },\n    \u002F\u002F Supavisor handles pooling at port 6543\n    \u002F\u002F No need to configure pgBouncer settings in the client\n  }\n);\n```\n\n- [ ] Application code uses pooled connection string (port 6543)\n- [ ] Direct connection reserved for migrations and admin tasks only\n- [ ] Connection string in deployment platform env vars (not hardcoded)\n- [ ] Verified pool mode: `transaction` for serverless, `session` for long-lived connections\n\n### Step 4: Enable Database Backups\n\nSupabase provides automatic daily backups on Pro plan. Point-in-time recovery (PITR) enables granular restores.\n\n- [ ] Automatic daily backups enabled (Pro plan — verify in Dashboard > Database > Backups)\n- [ ] Point-in-time recovery configured (Dashboard > Database > Backups > PITR)\n- [ ] Tested restore procedure on a staging project (do not skip this)\n- [ ] Migration files committed to version control (`supabase\u002Fmigrations\u002F` directory)\n- [ ] `npx supabase db push` tested against a fresh project to verify migrations replay cleanly\n\n### Step 5: Configure Network Restrictions\n\nRestrict database access to known IP addresses. This prevents unauthorized direct database connections even if credentials leak.\n\n- [ ] IP allowlist configured (Dashboard > Database > Network Restrictions)\n- [ ] Only deployment platform IPs and team office IPs are allowed\n- [ ] Verified that application still connects after restrictions applied\n- [ ] Documented which IPs are allowed and why\n\n### Step 6: Configure Custom Domain\n\nA custom domain replaces the default `*.supabase.co` URLs with your brand domain for API and auth endpoints.\n\n- [ ] Custom domain configured (Dashboard > Settings > Custom Domains)\n- [ ] DNS CNAME record added and verified\n- [ ] SSL certificate provisioned and active\n- [ ] Application code updated to use custom domain URL\n- [ ] OAuth redirect URLs updated to use custom domain\n\n### Step 7: Customize Auth Email Templates\n\nDefault Supabase auth emails show generic branding. Customize them so users see your domain and brand.\n\n- [ ] Confirmation email template customized (Dashboard > Auth > Email Templates)\n- [ ] Password reset email template customized\n- [ ] Magic link email template customized\n- [ ] Invite email template customized\n- [ ] Custom SMTP configured (Dashboard > Auth > SMTP Settings) — avoids rate limits and improves deliverability\n- [ ] Email confirmation enabled (Dashboard > Auth > Settings)\n- [ ] OAuth redirect URLs restricted to production domains only\n- [ ] Unused auth providers disabled\n\n### Step 8: Understand Rate Limits Per Tier\n\nSupabase enforces rate limits that vary by plan. Hitting these in production causes 429 errors.\n\n| Resource | Free | Pro | Team |\n|----------|------|-----|------|\n| API requests | 500\u002Fmin | 1,000\u002Fmin | 5,000\u002Fmin |\n| Auth emails | 4\u002Fhour | 30\u002Fhour | 100\u002Fhour |\n| Realtime connections | 200 concurrent | 500 concurrent | 2,000 concurrent |\n| Edge Function invocations | 500K\u002Fmonth | 2M\u002Fmonth | 5M\u002Fmonth |\n| Storage bandwidth | 2GB\u002Fmonth | 250GB\u002Fmonth | Custom |\n| Database size | 500MB | 8GB | 50GB |\n\n- [ ] Rate limits documented for your plan tier\n- [ ] Client-side retry logic with exponential backoff for 429 responses\n- [ ] Auth email rate limits understood (use custom SMTP to increase)\n- [ ] Realtime connection limits planned for expected concurrent users\n\n### Step 9: Review Monitoring Dashboards\n\nSupabase provides built-in monitoring. Review these before launch to establish baselines.\n\n```typescript\n\u002F\u002F Health check endpoint — deploy this to your application\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nconst supabase = createClient(\n  process.env.SUPABASE_URL!,\n  process.env.SUPABASE_ANON_KEY!\n);\n\nexport async function GET() {\n  const start = Date.now();\n  const { data, error } = await supabase\n    .from('_health_check')  \u002F\u002F Create a small table for this\n    .select('id')\n    .limit(1);\n\n  const latency = Date.now() - start;\n\n  return Response.json({\n    status: error ? 'unhealthy' : 'healthy',\n    latency_ms: latency,\n    timestamp: new Date().toISOString(),\n    supabase_reachable: !error,\n  }, { status: error ? 503 : 200 });\n}\n```\n\n- [ ] Dashboard > Reports reviewed (API requests, auth, storage, realtime)\n- [ ] Dashboard > Logs > API checked for error patterns\n- [ ] Dashboard > Database > Performance Advisor reviewed and recommendations applied\n- [ ] Health check endpoint deployed and monitored (uptime service)\n- [ ] Error tracking configured (Sentry, LogRocket, etc.)\n- [ ] Alerts set for: error rate spikes, high latency, connection pool exhaustion\n\n### Step 10: Deploy Edge Functions with Proper Env Vars\n\nEdge Functions run on Deno Deploy. Environment variables must be set via the Supabase CLI or Dashboard, not hardcoded.\n\n```bash\n# Set secrets for Edge Functions\nnpx supabase secrets set STRIPE_SECRET_KEY=sk_live_...\nnpx supabase secrets set RESEND_API_KEY=re_...\n\n# List current secrets\nnpx supabase secrets list\n\n# Deploy all Edge Functions\nnpx supabase functions deploy\n\n# Deploy a specific function\nnpx supabase functions deploy process-webhook\n```\n\n```typescript\n\u002F\u002F supabase\u002Ffunctions\u002Fprocess-webhook\u002Findex.ts\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nDeno.serve(async (req) => {\n  const supabase = createClient(\n    Deno.env.get('SUPABASE_URL')!,\n    Deno.env.get('SUPABASE_SERVICE_ROLE_KEY')!  \u002F\u002F Available automatically\n  );\n\n  const body = await req.json();\n  \u002F\u002F Process webhook payload...\n\n  return new Response(JSON.stringify({ received: true }), {\n    headers: { 'Content-Type': 'application\u002Fjson' },\n  });\n});\n```\n\n- [ ] All Edge Functions deployed to production (`npx supabase functions deploy`)\n- [ ] Environment secrets set via `npx supabase secrets set` (not hardcoded)\n- [ ] `SUPABASE_URL` and `SUPABASE_SERVICE_ROLE_KEY` available automatically (no need to set)\n- [ ] Edge Functions tested with `npx supabase functions serve` locally before deploying\n- [ ] CORS headers configured for Edge Functions that receive browser requests\n\n### Step 11: Verify Storage Bucket Policies\n\nStorage buckets need explicit policies, similar to RLS on tables. Without policies, buckets are inaccessible (default deny).\n\n```sql\n-- Check storage bucket configurations\nSELECT id, name, public, file_size_limit, allowed_mime_types\nFROM storage.buckets;\n\n-- Check existing storage policies\nSELECT policyname, tablename, cmd, qual\nFROM pg_policies\nWHERE schemaname = 'storage';\n```\n\n```sql\n-- Example: Allow authenticated users to upload to their own folder\nCREATE POLICY \"Users can upload own files\"\n  ON storage.objects\n  FOR INSERT\n  WITH CHECK (\n    bucket_id = 'avatars'\n    AND auth.uid()::text = (storage.foldername(name))[1]\n  );\n\n-- Example: Allow public read access to a bucket\nCREATE POLICY \"Public read access\"\n  ON storage.objects\n  FOR SELECT\n  USING (bucket_id = 'public-assets');\n```\n\n- [ ] Each bucket has explicit SELECT\u002FINSERT\u002FUPDATE\u002FDELETE policies\n- [ ] Public buckets are intentionally public (not accidentally open)\n- [ ] File size limits set per bucket (`file_size_limit` in bucket config)\n- [ ] Allowed MIME types restricted per bucket (`allowed_mime_types`)\n- [ ] User upload paths scoped to `auth.uid()` to prevent overwrites\n\n### Step 12: Add Database Indexes on Frequently Queried Columns\n\nMissing indexes are the leading cause of slow queries after launch. Add indexes on foreign keys, filter columns, and sort columns.\n\n```sql\n-- Find missing indexes on foreign keys\nSELECT\n  tc.table_name, kcu.column_name,\n  CASE WHEN i.indexname IS NULL THEN '** MISSING INDEX **' ELSE i.indexname END AS index_status\nFROM information_schema.table_constraints tc\nJOIN information_schema.key_column_usage kcu\n  ON tc.constraint_name = kcu.constraint_name\nLEFT JOIN pg_indexes i\n  ON i.tablename = tc.table_name\n  AND i.indexdef LIKE '%' || kcu.column_name || '%'\nWHERE tc.constraint_type = 'FOREIGN KEY'\n  AND tc.table_schema = 'public';\n\n-- Find slow queries (requires pg_stat_statements extension)\nCREATE EXTENSION IF NOT EXISTS pg_stat_statements;\n\nSELECT query, calls, mean_exec_time::numeric(10,2) AS avg_ms,\n       total_exec_time::numeric(10,2) AS total_ms\nFROM pg_stat_statements\nORDER BY mean_exec_time DESC\nLIMIT 10;\n\n-- Check table bloat (dead tuples from updates\u002Fdeletes)\nSELECT relname, n_live_tup, n_dead_tup,\n       round(n_dead_tup::numeric \u002F greatest(n_live_tup, 1) * 100, 1) AS dead_pct\nFROM pg_stat_user_tables\nWHERE n_dead_tup > 1000\nORDER BY n_dead_tup DESC;\n```\n\n```sql\n-- Create indexes on commonly filtered columns\nCREATE INDEX idx_profiles_user_id ON public.profiles(user_id);\nCREATE INDEX idx_orders_created_at ON public.orders(created_at DESC);\nCREATE INDEX idx_posts_status ON public.posts(status) WHERE status = 'published';  -- Partial index\n\n-- Set query timeout for the authenticated role\nALTER ROLE authenticated SET statement_timeout = '10s';\n```\n\n- [ ] Indexes on all foreign key columns\n- [ ] Indexes on columns used in WHERE, ORDER BY, and JOIN clauses\n- [ ] `pg_stat_statements` enabled for ongoing query monitoring\n- [ ] Performance Advisor reviewed (Dashboard > Database > Performance)\n- [ ] `statement_timeout` set for authenticated role to prevent runaway queries\n- [ ] Table bloat checked — VACUUM if dead tuple percentage > 10%\n\n### Step 13: Apply Migrations with `npx supabase db push`\n\nAll schema changes must go through migration files, never manual Dashboard edits in production.\n\n```bash\n# Generate a migration from local changes\nnpx supabase db diff --use-migra -f add_indexes\n\n# Apply migrations to production (linked project)\nnpx supabase db push\n\n# Verify migration history\nnpx supabase migration list\n\n# If a migration fails, create a rollback\nnpx supabase migration new rollback_bad_change\n```\n\n- [ ] All schema changes in `supabase\u002Fmigrations\u002F` directory (version controlled)\n- [ ] `npx supabase db push` tested against a fresh project\n- [ ] Migration history matches between local and remote (`npx supabase migration list`)\n- [ ] Rollback migration prepared for risky schema changes\n- [ ] No manual schema edits in production Dashboard\n\n### Step 14: Pre-Launch Final Verification\n\n```bash\n# Verify RLS status one final time\nnpx supabase inspect db table-sizes --linked\n\n# Check that the project is linked to production\nnpx supabase status\n\n# Verify connection string works\nnpx supabase db ping --linked\n```\n\n- [ ] CORS settings match production domain (Dashboard > API > CORS)\n- [ ] Environment variables set correctly in deployment platform\n- [ ] Realtime enabled only on tables that need it (reduces connection usage)\n- [ ] Webhook endpoints registered and tested\n- [ ] Load test completed on staging (see `supabase-load-scale`)\n- [ ] SSL enforcement enabled (Dashboard > Database > Settings > SSL)\n- [ ] DNS and custom domain verified end-to-end\n\n## Output\n\n- All 14 checklist sections verified with zero unchecked items\n- RLS enforced on every public table with tested policies\n- Key separation verified (anon client-side, service_role server-side only)\n- Connection pooling via Supavisor (port 6543) for all application code\n- Backups, PITR, monitoring, Edge Functions, Storage policies, indexes all verified\n- Migrations applied cleanly via `npx supabase db push`\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| `403 Forbidden` on all API calls | RLS enabled but no policies created | Add SELECT\u002FINSERT\u002FUPDATE\u002FDELETE policies for each role |\n| `429 Too Many Requests` | Plan rate limit exceeded | Upgrade plan or implement client-side backoff with retry |\n| Connection timeout under load | Using direct connection in serverless | Switch to pooled connection string (port 6543) |\n| Auth emails not delivered | Default SMTP rate-limited | Configure custom SMTP provider (SendGrid, Resend, Postmark) |\n| `PGRST301` permission denied | Service role key used where anon expected | Check client initialization — use anon key for client-side |\n| Edge Function cold starts | First invocation after idle period | Pre-warm with scheduled pings or accept ~200ms cold start |\n| Storage upload fails | Missing bucket policy or size limit exceeded | Add INSERT policy and check `file_size_limit` on bucket |\n| Slow queries after launch | Missing indexes on filter\u002Fjoin columns | Run Performance Advisor and add indexes per Step 12 |\n| Migration conflicts | Manual Dashboard edits diverged from migration files | Run `npx supabase db diff` to capture drift, then commit |\n\n## Examples\n\n### Client Setup (Next.js)\n\n```typescript\n\u002F\u002F lib\u002Fsupabase\u002Fclient.ts — browser (anon key)\nimport { createClient } from '@supabase\u002Fsupabase-js';\nexport const supabase = createClient\u003CDatabase>(\n  process.env.NEXT_PUBLIC_SUPABASE_URL!,\n  process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!\n);\n\n\u002F\u002F lib\u002Fsupabase\u002Fserver.ts — server only (service role)\nexport const supabaseAdmin = createClient\u003CDatabase>(\n  process.env.SUPABASE_URL!,\n  process.env.SUPABASE_SERVICE_ROLE_KEY!,\n  { auth: { autoRefreshToken: false, persistSession: false } }\n);\n```\n\n### RLS Policy Pattern\n\n```sql\nALTER TABLE public.posts ENABLE ROW LEVEL SECURITY;\nCREATE POLICY \"Public read published\" ON public.posts\n  FOR SELECT USING (status = 'published');\nCREATE POLICY \"Authors manage own\" ON public.posts\n  FOR ALL USING (auth.uid() = author_id)\n  WITH CHECK (auth.uid() = author_id);\n```\n\n### Rollback\n\n```bash\nnpx supabase migration new rollback_bad_change  # Create reversal SQL\nnpx supabase db push                             # Apply rollback\n# For data: Dashboard > Database > Backups > PITR\n# For app: vercel rollback \u002F netlify deploy --prod\n```\n\nFor complete examples including health checks, storage policies, and Edge Functions, see [examples.md](references\u002Fexamples.md).\n\n## Resources\n\n- [Going to Production](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdeployment\u002Fgoing-into-prod) — Official production checklist\n- [Maturity Model](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdeployment\u002Fmaturity-model) — Project lifecycle stages\n- [Shared Responsibility Model](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdeployment\u002Fshared-responsibility-model) — What Supabase manages vs. what you manage\n- [Performance Advisor](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Finspect) — Built-in query analysis\n- [Connection Pooling](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fconnecting-to-postgres#connection-pooler) — Supavisor configuration\n- [RLS Guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fpostgres\u002Frow-level-security) — Policy patterns and examples\n- [Edge Functions](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Ffunctions) — Serverless Deno functions\n- [Storage](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fstorage) — File storage with policies\n- [`@supabase\u002Fsupabase-js` Reference](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fjavascript\u002Fintroduction) — Client SDK docs\n\n## Next Steps\n\n- For SDK version upgrades, see `supabase-upgrade-migration`\n- For load testing before launch, see `supabase-load-scale`\n- For monitoring in production, see `supabase-monitoring`\n- For Edge Function patterns, see `supabase-edge-functions`\n",{"name":5,"tags":24,"author":31,"license":15,"version":32,"description":33,"allowed-tools":34,"compatible-with":35},[25,26,27,28,29,30],"saas","supabase","deployment","production","security","rls","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute Supabase production deployment checklist covering RLS, key hygiene,\nconnection pooling, backups, monitoring, Edge Functions, and Storage policies.\nUse when deploying to production, preparing for launch,\nor auditing a live Supabase project for security and performance gaps.\nTrigger with \"supabase production\", \"supabase go-live\",\n\"supabase launch checklist\", \"supabase prod ready\", \"deploy supabase\",\n\"supabase production readiness\".\n","Read, Write, Edit, Bash(npx supabase:*), Bash(curl:*), Grep","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--supabase-pack--supabase-prod-checklist",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill supabase-prod-checklist",{"tool":51,"command":52},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill supabase-prod-checklist",{"tool":54,"command":55},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill supabase-prod-checklist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--supabase-pack--supabase-prod-checklist\u002FSKILL.md",true,[],[60,67,74,81,88,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]