[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M796FGJDC8NWMPFWC6HHJMZY":3,"skill-same:01M796FGJDC8NWMPFWC6HHJMZY":60},{"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":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M796FGJDC8NWMPFWC6HHJMZY","supabase-known-pitfalls",null,"Avoid and fix the most common Supabase mistakes: exposing service_role key\nin client bundles, forgetting to enable RLS, not using connection pooling\nin serverless, .single() throwing on empty results, missing .select() after\ninsert\u002Fupdate, not destructuring { data, error }, creating multiple client\ninstances, and not using generated types.\nUse when reviewing Supabase code, onboarding developers, auditing an\nexisting project, or debugging unexpected behavior.\nTrigger with phrases like \"supabase mistakes\", \"supabase anti-patterns\",\n\"supabase pitfalls\", \"supabase code review\", \"supabase gotchas\",\n\"supabase debugging\", \"what not to do supabase\", \"supabase common errors\".","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-known-pitfalls\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: supabase-known-pitfalls\ndescription: |\n  Avoid and fix the most common Supabase mistakes: exposing service_role key\n  in client bundles, forgetting to enable RLS, not using connection pooling\n  in serverless, .single() throwing on empty results, missing .select() after\n  insert\u002Fupdate, not destructuring { data, error }, creating multiple client\n  instances, and not using generated types.\n  Use when reviewing Supabase code, onboarding developers, auditing an\n  existing project, or debugging unexpected behavior.\n  Trigger with phrases like \"supabase mistakes\", \"supabase anti-patterns\",\n  \"supabase pitfalls\", \"supabase code review\", \"supabase gotchas\",\n  \"supabase debugging\", \"what not to do supabase\", \"supabase common errors\".\nallowed-tools: Read, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, supabase, anti-patterns, code-review, debugging, security, pitfalls]\n---\n\n# Supabase Known Pitfalls\n\n## Overview\n\nThe twelve most common Supabase mistakes, ranked by severity: **security** (service_role exposure, missing RLS, permissive policies), **data integrity** (ignoring `{ data, error }`, missing `.select()` after mutations, `.single()` on optional results), **performance** (`select('*')`, N+1 queries, missing FK indexes, synchronous auth checks), and **maintainability** (no generated types, multiple client instances, hardcoded connection strings). Each pitfall shows the broken code, explains why it fails, and provides the correct pattern using `createClient` from `@supabase\u002Fsupabase-js`.\n\n## Prerequisites\n\n- Access to a Supabase project codebase for review\n- `@supabase\u002Fsupabase-js` v2+ installed\n- Basic understanding of Row Level Security (RLS)\n\n## Step 1 — Security Pitfalls (Critical)\n\nThese mistakes can expose all your data to any user with browser dev tools.\n\n### Pitfall 1: Exposing service_role Key in Client Code\n\n```typescript\n\u002F\u002F BAD: service_role key in a NEXT_PUBLIC_ variable — shipped to every browser\nimport { createClient } from '@supabase\u002Fsupabase-js'\n\nconst supabase = createClient(\n  process.env.NEXT_PUBLIC_SUPABASE_URL!,\n  process.env.NEXT_PUBLIC_SUPABASE_SERVICE_ROLE_KEY!  \u002F\u002F CATASTROPHIC\n)\n\u002F\u002F This key bypasses ALL RLS. Anyone can:\n\u002F\u002F - Read every row in every table\n\u002F\u002F - Delete the entire database\n\u002F\u002F - Create admin users\n\u002F\u002F - Access every file in storage\n\n\u002F\u002F CORRECT: anon key on client, service_role only on server\n\u002F\u002F Client (browser):\nconst supabase = createClient(\n  process.env.NEXT_PUBLIC_SUPABASE_URL!,\n  process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!  \u002F\u002F respects RLS\n)\n\n\u002F\u002F Server only (API routes, server actions):\nconst supabaseAdmin = createClient(\n  process.env.NEXT_PUBLIC_SUPABASE_URL!,\n  process.env.SUPABASE_SERVICE_ROLE_KEY!,  \u002F\u002F NO NEXT_PUBLIC_ prefix\n  { auth: { autoRefreshToken: false, persistSession: false } }\n)\n```\n\n**Detection:**\n```bash\n# Find service_role references in client-side files\ngrep -rn 'SERVICE_ROLE' --include=\"*.tsx\" --include=\"*.jsx\" --include=\"*.ts\" src\u002F app\u002F components\u002F pages\u002F\n# Find NEXT_PUBLIC_ + SERVICE_ROLE combination\ngrep -rn 'NEXT_PUBLIC.*SERVICE_ROLE' .env* *.ts *.tsx\n```\n\n### Pitfall 2: Tables Without RLS Enabled\n\n```sql\n-- BAD: table created without enabling RLS\nCREATE TABLE public.medical_records (\n  id uuid PRIMARY KEY DEFAULT gen_random_uuid(),\n  patient_id uuid REFERENCES auth.users(id),\n  diagnosis text,\n  ssn text  -- PII fully exposed to anyone with the anon key!\n);\n-- With RLS disabled, the anon key can read EVERY row via the PostgREST API\n\n-- CORRECT: always enable RLS immediately after CREATE TABLE\nCREATE TABLE public.medical_records (\n  id uuid PRIMARY KEY DEFAULT gen_random_uuid(),\n  patient_id uuid REFERENCES auth.users(id),\n  diagnosis text,\n  ssn text\n);\nALTER TABLE public.medical_records ENABLE ROW LEVEL SECURITY;\n\n-- Then add policies for legitimate access\nCREATE POLICY \"patients_read_own\" ON public.medical_records\n  FOR SELECT USING (patient_id = auth.uid());\n```\n\n**Detection:**\n```sql\n-- Find all tables without RLS (run in SQL Editor)\nSELECT schemaname, tablename\nFROM pg_tables\nWHERE schemaname = 'public'\nAND rowsecurity = false\nAND tablename NOT LIKE '\\_%';\n```\n\n### Pitfall 3: Overly Permissive RLS Policies\n\n```sql\n-- BAD: lets any authenticated user read ALL messages\nCREATE POLICY \"anyone_can_read\" ON public.messages\n  FOR SELECT USING (auth.uid() IS NOT NULL);\n-- Every logged-in user sees every other user's private messages\n\n-- BAD: lets any authenticated user update ANY row\nCREATE POLICY \"anyone_can_update\" ON public.profiles\n  FOR UPDATE USING (auth.uid() IS NOT NULL);\n-- Users can edit each other's profiles\n\n-- CORRECT: scope to the user's own data\nCREATE POLICY \"read_own_messages\" ON public.messages\n  FOR SELECT USING (\n    sender_id = auth.uid() OR recipient_id = auth.uid()\n  );\n\nCREATE POLICY \"update_own_profile\" ON public.profiles\n  FOR UPDATE USING (id = auth.uid());\n```\n\n### Pitfall 4: Not Using Connection Pooling in Serverless\n\n```typescript\n\u002F\u002F BAD: direct connection string in a serverless function\n\u002F\u002F Each Lambda\u002FEdge invocation opens a new connection — exhausts pool in minutes\nconst connectionString = 'postgresql:\u002F\u002Fpostgres:pass@db.xxx.supabase.co:5432\u002Fpostgres'\n\n\u002F\u002F CORRECT: use the pooled connection string (Supavisor, port 6543)\nconst connectionString = 'postgresql:\u002F\u002Fpostgres.xxx:pass@aws-0-us-east-1.pooler.supabase.com:6543\u002Fpostgres'\n\u002F\u002F Transaction mode: shares connections across requests\n\u002F\u002F Required for serverless (Vercel, Netlify, Cloudflare Workers, AWS Lambda)\n```\n\n## Step 2 — Data Integrity Pitfalls (High)\n\nThese mistakes cause silent data loss, null pointer errors, and inconsistent state.\n\n### Pitfall 5: Not Handling { data, error }\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)\n\n\u002F\u002F BAD: destructuring only data — errors silently ignored\nconst { data } = await supabase.from('orders').insert(order).select().single()\nconsole.log(data.id)  \u002F\u002F TypeError: Cannot read property 'id' of null\n\u002F\u002F The insert failed (maybe RLS blocked it), data is null, error has the reason\n\n\u002F\u002F CORRECT: always check error before using data\nconst { data, error } = await supabase.from('orders').insert(order).select().single()\nif (error) {\n  console.error('Insert failed:', error.code, error.message, error.details)\n  throw new Error(`Order creation failed: ${error.message}`)\n}\n\u002F\u002F Now data is guaranteed to be non-null\nconsole.log(data.id)\n```\n\n### Pitfall 6: Missing .select() After Insert\u002FUpdate\u002FUpsert\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)\n\n\u002F\u002F BAD: insert without .select() returns NO data\nconst { data } = await supabase.from('todos').insert({ title: 'Buy milk' })\nconsole.log(data)  \u002F\u002F null! Not the inserted row.\n\u002F\u002F Supabase mutations return null by default (like SQL INSERT without RETURNING)\n\n\u002F\u002F CORRECT: chain .select() to get the inserted\u002Fupdated row back\nconst { data, error } = await supabase\n  .from('todos')\n  .insert({ title: 'Buy milk' })\n  .select('id, title, is_complete, created_at')  \u002F\u002F like SQL RETURNING\n  .single()\n\nif (error) throw new Error(`Insert failed: ${error.message}`)\nconsole.log(data)  \u002F\u002F { id: '...', title: 'Buy milk', is_complete: false, ... }\n```\n\n### Pitfall 7: .single() on Empty or Multiple Results\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)\n\n\u002F\u002F BAD: .single() throws PGRST116 when no rows match\nconst { data, error } = await supabase\n  .from('profiles')\n  .select('id, username, avatar_url')\n  .eq('username', searchTerm)\n  .single()\n\u002F\u002F error: { code: 'PGRST116', message: 'JSON object requested, multiple (or no) rows returned' }\n\u002F\u002F This is an ERROR, not just null — it breaks your flow\n\n\u002F\u002F BAD: .single() also throws when MULTIPLE rows match (PGRST200)\n\n\u002F\u002F CORRECT: use .maybeSingle() for 0-or-1 results\nconst { data, error } = await supabase\n  .from('profiles')\n  .select('id, username, avatar_url')\n  .eq('username', searchTerm)\n  .maybeSingle()\n\u002F\u002F data is null if no match (no error thrown)\n\u002F\u002F data is the row if exactly one match\n\u002F\u002F error only if 2+ rows match\n\n\u002F\u002F RULE OF THUMB:\n\u002F\u002F .single()      — use ONLY when you KNOW exactly 1 row exists (e.g., by primary key)\n\u002F\u002F .maybeSingle() — use when 0 or 1 rows might match (lookups by unique field)\n\u002F\u002F neither        — use when you expect an array of results\n```\n\n## Step 3 — Performance and Maintainability Pitfalls (Medium\u002FLow)\n\n### Pitfall 8: select('*') Everywhere\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)\n\n\u002F\u002F BAD: fetches ALL columns including large text\u002Fjsonb\u002Fbytea fields\nconst { data } = await supabase.from('posts').select('*')\n\u002F\u002F Problems:\n\u002F\u002F 1. Transfers unnecessary data (slower, more bandwidth)\n\u002F\u002F 2. May leak sensitive columns (SSN, internal notes, hashed passwords)\n\u002F\u002F 3. No TypeScript autocompletion — type is too broad\n\u002F\u002F 4. Cannot benefit from covering indexes\n\n\u002F\u002F CORRECT: specify only the columns you need\nconst { data } = await supabase\n  .from('posts')\n  .select('id, title, slug, excerpt, published_at, author:profiles(name, avatar_url)')\n\u002F\u002F Benefits: smaller payload, typed results, index-friendly, no data leakage\n```\n\n### Pitfall 9: N+1 Query Pattern\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)\n\n\u002F\u002F BAD: 1 query to get projects + N queries to get tasks per project\nconst { data: projects } = await supabase.from('projects').select('id, name')\n\nfor (const project of projects ?? []) {\n  const { data: tasks } = await supabase\n    .from('tasks')\n    .select('id, title, status')\n    .eq('project_id', project.id)\n  project.tasks = tasks  \u002F\u002F N additional queries!\n}\n\u002F\u002F Total: 1 + N queries (if you have 50 projects, that's 51 queries)\n\n\u002F\u002F CORRECT: use PostgREST embedded joins (single query)\nconst { data } = await supabase\n  .from('projects')\n  .select(`\n    id, name,\n    tasks (id, title, status)\n  `)\n\u002F\u002F Total: 1 query with automatic JOIN\n\u002F\u002F PostgREST detects the foreign key and embeds the related data\n\n\u002F\u002F ALSO CORRECT: batch with .in() for non-FK relationships\nconst projectIds = projects?.map(p => p.id) ?? []\nconst { data: allTasks } = await supabase\n  .from('tasks')\n  .select('id, title, status, project_id')\n  .in('project_id', projectIds)\n\u002F\u002F Total: 2 queries regardless of N\n```\n\n### Pitfall 10: Missing Indexes on Foreign Key Columns\n\n```sql\n-- BAD: foreign key without index\nCREATE TABLE public.comments (\n  id uuid PRIMARY KEY DEFAULT gen_random_uuid(),\n  post_id uuid REFERENCES public.posts(id),  -- no index!\n  author_id uuid REFERENCES auth.users(id),  -- no index!\n  body text,\n  created_at timestamptz DEFAULT now()\n);\n-- Every query filtering by post_id or author_id does a sequential scan\n-- RLS policies checking these columns also become slow\n\n-- CORRECT: always index foreign key columns\nCREATE TABLE public.comments (\n  id uuid PRIMARY KEY DEFAULT gen_random_uuid(),\n  post_id uuid REFERENCES public.posts(id),\n  author_id uuid REFERENCES auth.users(id),\n  body text,\n  created_at timestamptz DEFAULT now()\n);\nCREATE INDEX idx_comments_post_id ON public.comments(post_id);\nCREATE INDEX idx_comments_author_id ON public.comments(author_id);\n```\n\n**Detection:**\n```sql\n-- Find foreign keys without indexes\nSELECT\n  tc.table_name,\n  kcu.column_name,\n  'CREATE INDEX idx_' || tc.table_name || '_' || kcu.column_name\n    || ' ON public.' || tc.table_name || '(' || kcu.column_name || ');' AS fix\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 pi\n  ON pi.tablename = tc.table_name\n  AND pi.indexdef LIKE '%' || kcu.column_name || '%'\nWHERE tc.constraint_type = 'FOREIGN KEY'\nAND tc.table_schema = 'public'\nAND pi.indexname IS NULL;\n```\n\n### Pitfall 11: Creating Multiple Client Instances\n\n```typescript\n\u002F\u002F BAD: new client in every file — wastes memory, breaks auth state\n\u002F\u002F utils\u002Fauth.ts\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)  \u002F\u002F instance 1\n\n\u002F\u002F utils\u002Fdata.ts\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)  \u002F\u002F instance 2 — separate auth session!\n\n\u002F\u002F components\u002FProfile.tsx\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)  \u002F\u002F instance 3 — yet another session\n\n\u002F\u002F Problems:\n\u002F\u002F - Auth state is not shared between instances\n\u002F\u002F - Realtime subscriptions multiply\n\u002F\u002F - Memory overhead from duplicate GoTrue instances\n\u002F\u002F - Session refresh happens 3x unnecessarily\n\n\u002F\u002F CORRECT: singleton pattern — one instance, imported everywhere\n\u002F\u002F lib\u002Fsupabase.ts\nimport { createClient } from '@supabase\u002Fsupabase-js'\nimport type { Database } from '.\u002Fdatabase.types'\n\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 Every file imports the same instance:\n\u002F\u002F import { supabase } from '@\u002Flib\u002Fsupabase'\n```\n\n### Pitfall 12: Not Using Generated Types\n\n```typescript\n\u002F\u002F BAD: manual types that drift from the actual database schema\ninterface Todo {\n  id: number        \u002F\u002F wrong! Supabase uses uuid by default\n  title: string\n  done: boolean     \u002F\u002F wrong! Column is actually called is_complete\n  createdAt: string \u002F\u002F wrong! Column is actually called created_at\n}\n\n\u002F\u002F The compiler doesn't catch any of these mismatches.\n\u002F\u002F You get runtime errors instead of compile-time errors.\n\n\u002F\u002F CORRECT: generate types from your database schema\n\u002F\u002F Step 1: Generate\n\u002F\u002F npx supabase gen types typescript --linked > lib\u002Fdatabase.types.ts\n\n\u002F\u002F Step 2: Use the generated types\nimport type { Database } from '.\u002Fdatabase.types'\n\ntype Todo = Database['public']['Tables']['todos']['Row']\n\u002F\u002F { id: string, title: string, is_complete: boolean, created_at: string, user_id: string }\n\ntype TodoInsert = Database['public']['Tables']['todos']['Insert']\n\u002F\u002F { title: string, user_id?: string, is_complete?: boolean }\n\n\u002F\u002F Step 3: Pass the Database type to createClient\nimport { createClient } from '@supabase\u002Fsupabase-js'\n\nconst supabase = createClient\u003CDatabase>(url, key)\n\n\u002F\u002F Now all queries are fully typed:\nconst { data } = await supabase.from('todos').select('id, title, is_complete')\n\u002F\u002F data is typed as { id: string; title: string; is_complete: boolean }[] | null\n\n\u002F\u002F Automate type generation in CI:\n\u002F\u002F Add to package.json scripts: \"types:supabase\": \"supabase gen types typescript --linked > lib\u002Fdatabase.types.ts\"\n```\n\n## Output\n\n- Security pitfalls identified: service_role exposure, missing RLS, permissive policies, no connection pooling\n- Data integrity pitfalls fixed: `{ data, error }` handling, `.select()` after mutations, `.maybeSingle()` usage\n- Performance pitfalls resolved: column-specific selects, JOIN queries, FK indexes\n- Maintainability improved: singleton client, generated types\n- Detection commands for automated scanning of each pitfall\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| `PGRST116: JSON object requested, multiple (or no) rows returned` | Used `.single()` when 0 or 2+ rows match | Use `.maybeSingle()` for optional lookups |\n| `data` is `null` after insert | Missing `.select()` chain | Add `.select('column1, column2')` after `.insert()` |\n| `TypeError: Cannot read property of null` | Destructured only `data`, ignoring `error` | Always destructure `{ data, error }` and check error first |\n| `too many connections for role` | Direct connection from serverless | Use pooled connection string (port 6543) |\n| `permission denied for table` | RLS blocking access, no matching policy | Check RLS policies match the authenticated user's JWT claims |\n| `relation does not exist` | Table name typo, not caught at compile time | Use generated types for compile-time validation |\n\n## Examples\n\n### Quick Security Audit\n\n```bash\n# Check for all three critical security pitfalls in one pass\necho \"=== Pitfall 1: Service role in client code ===\"\ngrep -rn 'SERVICE_ROLE' --include=\"*.tsx\" --include=\"*.ts\" src\u002F app\u002F components\u002F 2>\u002Fdev\u002Fnull || echo \"Clean\"\n\necho \"=== Pitfall 2: Tables without RLS ===\"\n# Run in SQL Editor:\n# SELECT tablename FROM pg_tables WHERE schemaname = 'public' AND rowsecurity = false;\n\necho \"=== Pitfall 3: Overly permissive policies ===\"\n# Run in SQL Editor:\n# SELECT tablename, policyname FROM pg_policies WHERE qual = 'true' AND cmd != 'r';\n```\n\n### Code Review Checklist\n\n```markdown\n## Supabase PR Review Checklist\n\n### Security\n- [ ] No `SERVICE_ROLE_KEY` in client-side code or `NEXT_PUBLIC_*` vars\n- [ ] RLS enabled on all new tables\n- [ ] RLS policies scope to `auth.uid()` or org membership (no `USING (true)` for writes)\n\n### Data Integrity\n- [ ] All Supabase calls destructure `{ data, error }` and check error\n- [ ] `.select()` chained after `.insert()`, `.update()`, `.upsert()`\n- [ ] `.maybeSingle()` used for optional lookups (not `.single()`)\n\n### Performance\n- [ ] Column names specified in `.select()` (no `select('*')`)\n- [ ] No N+1 patterns (use embedded joins or `.in()`)\n- [ ] Foreign key columns have indexes\n\n### Maintainability\n- [ ] Single `createClient` instance (singleton pattern)\n- [ ] Generated types used (not manual interfaces)\n- [ ] Pooled connection string for serverless deployments\n```\n\n## Resources\n\n- [Supabase Auth: Securing Your Data](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fauth#securing-your-data)\n- [Row Level Security](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fpostgres\u002Frow-level-security)\n- [TypeScript Support](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fjavascript\u002Ftypescript-support)\n- [Connection Pooling](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fconnecting-to-postgres#connection-pooler)\n- [Supabase JavaScript Client Reference](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fjavascript\u002Fselect)\n- [PostgREST Error Codes](https:\u002F\u002Fpostgrest.org\u002Fen\u002Fstable\u002Freferences\u002Ferrors.html)\n\n## Next Steps\n\nThis completes the Supabase pitfalls reference. To start a new project with best practices from day one, see `supabase-hello-world`.\n","# Supabase Known Pitfalls\n\n## Overview\n\nThe twelve most common Supabase mistakes, ranked by severity: **security** (service_role exposure, missing RLS, permissive policies), **data integrity** (ignoring `{ data, error }`, missing `.select()` after mutations, `.single()` on optional results), **performance** (`select('*')`, N+1 queries, missing FK indexes, synchronous auth checks), and **maintainability** (no generated types, multiple client instances, hardcoded connection strings). Each pitfall shows the broken code, explains why it fails, and provides the correct pattern using `createClient` from `@supabase\u002Fsupabase-js`.\n\n## Prerequisites\n\n- Access to a Supabase project codebase for review\n- `@supabase\u002Fsupabase-js` v2+ installed\n- Basic understanding of Row Level Security (RLS)\n\n## Step 1 — Security Pitfalls (Critical)\n\nThese mistakes can expose all your data to any user with browser dev tools.\n\n### Pitfall 1: Exposing service_role Key in Client Code\n\n```typescript\n\u002F\u002F BAD: service_role key in a NEXT_PUBLIC_ variable — shipped to every browser\nimport { createClient } from '@supabase\u002Fsupabase-js'\n\nconst supabase = createClient(\n  process.env.NEXT_PUBLIC_SUPABASE_URL!,\n  process.env.NEXT_PUBLIC_SUPABASE_SERVICE_ROLE_KEY!  \u002F\u002F CATASTROPHIC\n)\n\u002F\u002F This key bypasses ALL RLS. Anyone can:\n\u002F\u002F - Read every row in every table\n\u002F\u002F - Delete the entire database\n\u002F\u002F - Create admin users\n\u002F\u002F - Access every file in storage\n\n\u002F\u002F CORRECT: anon key on client, service_role only on server\n\u002F\u002F Client (browser):\nconst supabase = createClient(\n  process.env.NEXT_PUBLIC_SUPABASE_URL!,\n  process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!  \u002F\u002F respects RLS\n)\n\n\u002F\u002F Server only (API routes, server actions):\nconst supabaseAdmin = createClient(\n  process.env.NEXT_PUBLIC_SUPABASE_URL!,\n  process.env.SUPABASE_SERVICE_ROLE_KEY!,  \u002F\u002F NO NEXT_PUBLIC_ prefix\n  { auth: { autoRefreshToken: false, persistSession: false } }\n)\n```\n\n**Detection:**\n```bash\n# Find service_role references in client-side files\ngrep -rn 'SERVICE_ROLE' --include=\"*.tsx\" --include=\"*.jsx\" --include=\"*.ts\" src\u002F app\u002F components\u002F pages\u002F\n# Find NEXT_PUBLIC_ + SERVICE_ROLE combination\ngrep -rn 'NEXT_PUBLIC.*SERVICE_ROLE' .env* *.ts *.tsx\n```\n\n### Pitfall 2: Tables Without RLS Enabled\n\n```sql\n-- BAD: table created without enabling RLS\nCREATE TABLE public.medical_records (\n  id uuid PRIMARY KEY DEFAULT gen_random_uuid(),\n  patient_id uuid REFERENCES auth.users(id),\n  diagnosis text,\n  ssn text  -- PII fully exposed to anyone with the anon key!\n);\n-- With RLS disabled, the anon key can read EVERY row via the PostgREST API\n\n-- CORRECT: always enable RLS immediately after CREATE TABLE\nCREATE TABLE public.medical_records (\n  id uuid PRIMARY KEY DEFAULT gen_random_uuid(),\n  patient_id uuid REFERENCES auth.users(id),\n  diagnosis text,\n  ssn text\n);\nALTER TABLE public.medical_records ENABLE ROW LEVEL SECURITY;\n\n-- Then add policies for legitimate access\nCREATE POLICY \"patients_read_own\" ON public.medical_records\n  FOR SELECT USING (patient_id = auth.uid());\n```\n\n**Detection:**\n```sql\n-- Find all tables without RLS (run in SQL Editor)\nSELECT schemaname, tablename\nFROM pg_tables\nWHERE schemaname = 'public'\nAND rowsecurity = false\nAND tablename NOT LIKE '\\_%';\n```\n\n### Pitfall 3: Overly Permissive RLS Policies\n\n```sql\n-- BAD: lets any authenticated user read ALL messages\nCREATE POLICY \"anyone_can_read\" ON public.messages\n  FOR SELECT USING (auth.uid() IS NOT NULL);\n-- Every logged-in user sees every other user's private messages\n\n-- BAD: lets any authenticated user update ANY row\nCREATE POLICY \"anyone_can_update\" ON public.profiles\n  FOR UPDATE USING (auth.uid() IS NOT NULL);\n-- Users can edit each other's profiles\n\n-- CORRECT: scope to the user's own data\nCREATE POLICY \"read_own_messages\" ON public.messages\n  FOR SELECT USING (\n    sender_id = auth.uid() OR recipient_id = auth.uid()\n  );\n\nCREATE POLICY \"update_own_profile\" ON public.profiles\n  FOR UPDATE USING (id = auth.uid());\n```\n\n### Pitfall 4: Not Using Connection Pooling in Serverless\n\n```typescript\n\u002F\u002F BAD: direct connection string in a serverless function\n\u002F\u002F Each Lambda\u002FEdge invocation opens a new connection — exhausts pool in minutes\nconst connectionString = 'postgresql:\u002F\u002Fpostgres:pass@db.xxx.supabase.co:5432\u002Fpostgres'\n\n\u002F\u002F CORRECT: use the pooled connection string (Supavisor, port 6543)\nconst connectionString = 'postgresql:\u002F\u002Fpostgres.xxx:pass@aws-0-us-east-1.pooler.supabase.com:6543\u002Fpostgres'\n\u002F\u002F Transaction mode: shares connections across requests\n\u002F\u002F Required for serverless (Vercel, Netlify, Cloudflare Workers, AWS Lambda)\n```\n\n## Step 2 — Data Integrity Pitfalls (High)\n\nThese mistakes cause silent data loss, null pointer errors, and inconsistent state.\n\n### Pitfall 5: Not Handling { data, error }\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)\n\n\u002F\u002F BAD: destructuring only data — errors silently ignored\nconst { data } = await supabase.from('orders').insert(order).select().single()\nconsole.log(data.id)  \u002F\u002F TypeError: Cannot read property 'id' of null\n\u002F\u002F The insert failed (maybe RLS blocked it), data is null, error has the reason\n\n\u002F\u002F CORRECT: always check error before using data\nconst { data, error } = await supabase.from('orders').insert(order).select().single()\nif (error) {\n  console.error('Insert failed:', error.code, error.message, error.details)\n  throw new Error(`Order creation failed: ${error.message}`)\n}\n\u002F\u002F Now data is guaranteed to be non-null\nconsole.log(data.id)\n```\n\n### Pitfall 6: Missing .select() After Insert\u002FUpdate\u002FUpsert\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)\n\n\u002F\u002F BAD: insert without .select() returns NO data\nconst { data } = await supabase.from('todos').insert({ title: 'Buy milk' })\nconsole.log(data)  \u002F\u002F null! Not the inserted row.\n\u002F\u002F Supabase mutations return null by default (like SQL INSERT without RETURNING)\n\n\u002F\u002F CORRECT: chain .select() to get the inserted\u002Fupdated row back\nconst { data, error } = await supabase\n  .from('todos')\n  .insert({ title: 'Buy milk' })\n  .select('id, title, is_complete, created_at')  \u002F\u002F like SQL RETURNING\n  .single()\n\nif (error) throw new Error(`Insert failed: ${error.message}`)\nconsole.log(data)  \u002F\u002F { id: '...', title: 'Buy milk', is_complete: false, ... }\n```\n\n### Pitfall 7: .single() on Empty or Multiple Results\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)\n\n\u002F\u002F BAD: .single() throws PGRST116 when no rows match\nconst { data, error } = await supabase\n  .from('profiles')\n  .select('id, username, avatar_url')\n  .eq('username', searchTerm)\n  .single()\n\u002F\u002F error: { code: 'PGRST116', message: 'JSON object requested, multiple (or no) rows returned' }\n\u002F\u002F This is an ERROR, not just null — it breaks your flow\n\n\u002F\u002F BAD: .single() also throws when MULTIPLE rows match (PGRST200)\n\n\u002F\u002F CORRECT: use .maybeSingle() for 0-or-1 results\nconst { data, error } = await supabase\n  .from('profiles')\n  .select('id, username, avatar_url')\n  .eq('username', searchTerm)\n  .maybeSingle()\n\u002F\u002F data is null if no match (no error thrown)\n\u002F\u002F data is the row if exactly one match\n\u002F\u002F error only if 2+ rows match\n\n\u002F\u002F RULE OF THUMB:\n\u002F\u002F .single()      — use ONLY when you KNOW exactly 1 row exists (e.g., by primary key)\n\u002F\u002F .maybeSingle() — use when 0 or 1 rows might match (lookups by unique field)\n\u002F\u002F neither        — use when you expect an array of results\n```\n\n## Step 3 — Performance and Maintainability Pitfalls (Medium\u002FLow)\n\n### Pitfall 8: select('*') Everywhere\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)\n\n\u002F\u002F BAD: fetches ALL columns including large text\u002Fjsonb\u002Fbytea fields\nconst { data } = await supabase.from('posts').select('*')\n\u002F\u002F Problems:\n\u002F\u002F 1. Transfers unnecessary data (slower, more bandwidth)\n\u002F\u002F 2. May leak sensitive columns (SSN, internal notes, hashed passwords)\n\u002F\u002F 3. No TypeScript autocompletion — type is too broad\n\u002F\u002F 4. Cannot benefit from covering indexes\n\n\u002F\u002F CORRECT: specify only the columns you need\nconst { data } = await supabase\n  .from('posts')\n  .select('id, title, slug, excerpt, published_at, author:profiles(name, avatar_url)')\n\u002F\u002F Benefits: smaller payload, typed results, index-friendly, no data leakage\n```\n\n### Pitfall 9: N+1 Query Pattern\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)\n\n\u002F\u002F BAD: 1 query to get projects + N queries to get tasks per project\nconst { data: projects } = await supabase.from('projects').select('id, name')\n\nfor (const project of projects ?? []) {\n  const { data: tasks } = await supabase\n    .from('tasks')\n    .select('id, title, status')\n    .eq('project_id', project.id)\n  project.tasks = tasks  \u002F\u002F N additional queries!\n}\n\u002F\u002F Total: 1 + N queries (if you have 50 projects, that's 51 queries)\n\n\u002F\u002F CORRECT: use PostgREST embedded joins (single query)\nconst { data } = await supabase\n  .from('projects')\n  .select(`\n    id, name,\n    tasks (id, title, status)\n  `)\n\u002F\u002F Total: 1 query with automatic JOIN\n\u002F\u002F PostgREST detects the foreign key and embeds the related data\n\n\u002F\u002F ALSO CORRECT: batch with .in() for non-FK relationships\nconst projectIds = projects?.map(p => p.id) ?? []\nconst { data: allTasks } = await supabase\n  .from('tasks')\n  .select('id, title, status, project_id')\n  .in('project_id', projectIds)\n\u002F\u002F Total: 2 queries regardless of N\n```\n\n### Pitfall 10: Missing Indexes on Foreign Key Columns\n\n```sql\n-- BAD: foreign key without index\nCREATE TABLE public.comments (\n  id uuid PRIMARY KEY DEFAULT gen_random_uuid(),\n  post_id uuid REFERENCES public.posts(id),  -- no index!\n  author_id uuid REFERENCES auth.users(id),  -- no index!\n  body text,\n  created_at timestamptz DEFAULT now()\n);\n-- Every query filtering by post_id or author_id does a sequential scan\n-- RLS policies checking these columns also become slow\n\n-- CORRECT: always index foreign key columns\nCREATE TABLE public.comments (\n  id uuid PRIMARY KEY DEFAULT gen_random_uuid(),\n  post_id uuid REFERENCES public.posts(id),\n  author_id uuid REFERENCES auth.users(id),\n  body text,\n  created_at timestamptz DEFAULT now()\n);\nCREATE INDEX idx_comments_post_id ON public.comments(post_id);\nCREATE INDEX idx_comments_author_id ON public.comments(author_id);\n```\n\n**Detection:**\n```sql\n-- Find foreign keys without indexes\nSELECT\n  tc.table_name,\n  kcu.column_name,\n  'CREATE INDEX idx_' || tc.table_name || '_' || kcu.column_name\n    || ' ON public.' || tc.table_name || '(' || kcu.column_name || ');' AS fix\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 pi\n  ON pi.tablename = tc.table_name\n  AND pi.indexdef LIKE '%' || kcu.column_name || '%'\nWHERE tc.constraint_type = 'FOREIGN KEY'\nAND tc.table_schema = 'public'\nAND pi.indexname IS NULL;\n```\n\n### Pitfall 11: Creating Multiple Client Instances\n\n```typescript\n\u002F\u002F BAD: new client in every file — wastes memory, breaks auth state\n\u002F\u002F utils\u002Fauth.ts\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)  \u002F\u002F instance 1\n\n\u002F\u002F utils\u002Fdata.ts\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)  \u002F\u002F instance 2 — separate auth session!\n\n\u002F\u002F components\u002FProfile.tsx\nimport { createClient } from '@supabase\u002Fsupabase-js'\nconst supabase = createClient(url, key)  \u002F\u002F instance 3 — yet another session\n\n\u002F\u002F Problems:\n\u002F\u002F - Auth state is not shared between instances\n\u002F\u002F - Realtime subscriptions multiply\n\u002F\u002F - Memory overhead from duplicate GoTrue instances\n\u002F\u002F - Session refresh happens 3x unnecessarily\n\n\u002F\u002F CORRECT: singleton pattern — one instance, imported everywhere\n\u002F\u002F lib\u002Fsupabase.ts\nimport { createClient } from '@supabase\u002Fsupabase-js'\nimport type { Database } from '.\u002Fdatabase.types'\n\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 Every file imports the same instance:\n\u002F\u002F import { supabase } from '@\u002Flib\u002Fsupabase'\n```\n\n### Pitfall 12: Not Using Generated Types\n\n```typescript\n\u002F\u002F BAD: manual types that drift from the actual database schema\ninterface Todo {\n  id: number        \u002F\u002F wrong! Supabase uses uuid by default\n  title: string\n  done: boolean     \u002F\u002F wrong! Column is actually called is_complete\n  createdAt: string \u002F\u002F wrong! Column is actually called created_at\n}\n\n\u002F\u002F The compiler doesn't catch any of these mismatches.\n\u002F\u002F You get runtime errors instead of compile-time errors.\n\n\u002F\u002F CORRECT: generate types from your database schema\n\u002F\u002F Step 1: Generate\n\u002F\u002F npx supabase gen types typescript --linked > lib\u002Fdatabase.types.ts\n\n\u002F\u002F Step 2: Use the generated types\nimport type { Database } from '.\u002Fdatabase.types'\n\ntype Todo = Database['public']['Tables']['todos']['Row']\n\u002F\u002F { id: string, title: string, is_complete: boolean, created_at: string, user_id: string }\n\ntype TodoInsert = Database['public']['Tables']['todos']['Insert']\n\u002F\u002F { title: string, user_id?: string, is_complete?: boolean }\n\n\u002F\u002F Step 3: Pass the Database type to createClient\nimport { createClient } from '@supabase\u002Fsupabase-js'\n\nconst supabase = createClient\u003CDatabase>(url, key)\n\n\u002F\u002F Now all queries are fully typed:\nconst { data } = await supabase.from('todos').select('id, title, is_complete')\n\u002F\u002F data is typed as { id: string; title: string; is_complete: boolean }[] | null\n\n\u002F\u002F Automate type generation in CI:\n\u002F\u002F Add to package.json scripts: \"types:supabase\": \"supabase gen types typescript --linked > lib\u002Fdatabase.types.ts\"\n```\n\n## Output\n\n- Security pitfalls identified: service_role exposure, missing RLS, permissive policies, no connection pooling\n- Data integrity pitfalls fixed: `{ data, error }` handling, `.select()` after mutations, `.maybeSingle()` usage\n- Performance pitfalls resolved: column-specific selects, JOIN queries, FK indexes\n- Maintainability improved: singleton client, generated types\n- Detection commands for automated scanning of each pitfall\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| `PGRST116: JSON object requested, multiple (or no) rows returned` | Used `.single()` when 0 or 2+ rows match | Use `.maybeSingle()` for optional lookups |\n| `data` is `null` after insert | Missing `.select()` chain | Add `.select('column1, column2')` after `.insert()` |\n| `TypeError: Cannot read property of null` | Destructured only `data`, ignoring `error` | Always destructure `{ data, error }` and check error first |\n| `too many connections for role` | Direct connection from serverless | Use pooled connection string (port 6543) |\n| `permission denied for table` | RLS blocking access, no matching policy | Check RLS policies match the authenticated user's JWT claims |\n| `relation does not exist` | Table name typo, not caught at compile time | Use generated types for compile-time validation |\n\n## Examples\n\n### Quick Security Audit\n\n```bash\n# Check for all three critical security pitfalls in one pass\necho \"=== Pitfall 1: Service role in client code ===\"\ngrep -rn 'SERVICE_ROLE' --include=\"*.tsx\" --include=\"*.ts\" src\u002F app\u002F components\u002F 2>\u002Fdev\u002Fnull || echo \"Clean\"\n\necho \"=== Pitfall 2: Tables without RLS ===\"\n# Run in SQL Editor:\n# SELECT tablename FROM pg_tables WHERE schemaname = 'public' AND rowsecurity = false;\n\necho \"=== Pitfall 3: Overly permissive policies ===\"\n# Run in SQL Editor:\n# SELECT tablename, policyname FROM pg_policies WHERE qual = 'true' AND cmd != 'r';\n```\n\n### Code Review Checklist\n\n```markdown\n## Supabase PR Review Checklist\n\n### Security\n- [ ] No `SERVICE_ROLE_KEY` in client-side code or `NEXT_PUBLIC_*` vars\n- [ ] RLS enabled on all new tables\n- [ ] RLS policies scope to `auth.uid()` or org membership (no `USING (true)` for writes)\n\n### Data Integrity\n- [ ] All Supabase calls destructure `{ data, error }` and check error\n- [ ] `.select()` chained after `.insert()`, `.update()`, `.upsert()`\n- [ ] `.maybeSingle()` used for optional lookups (not `.single()`)\n\n### Performance\n- [ ] Column names specified in `.select()` (no `select('*')`)\n- [ ] No N+1 patterns (use embedded joins or `.in()`)\n- [ ] Foreign key columns have indexes\n\n### Maintainability\n- [ ] Single `createClient` instance (singleton pattern)\n- [ ] Generated types used (not manual interfaces)\n- [ ] Pooled connection string for serverless deployments\n```\n\n## Resources\n\n- [Supabase Auth: Securing Your Data](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fauth#securing-your-data)\n- [Row Level Security](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fpostgres\u002Frow-level-security)\n- [TypeScript Support](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fjavascript\u002Ftypescript-support)\n- [Connection Pooling](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fconnecting-to-postgres#connection-pooler)\n- [Supabase JavaScript Client Reference](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fjavascript\u002Fselect)\n- [PostgREST Error Codes](https:\u002F\u002Fpostgrest.org\u002Fen\u002Fstable\u002Freferences\u002Ferrors.html)\n\n## Next Steps\n\nThis completes the Supabase pitfalls reference. To start a new project with best practices from day one, see `supabase-hello-world`.\n",{"name":5,"tags":24,"author":32,"license":15,"version":33,"description":34,"allowed-tools":35,"compatible-with":36},[25,26,27,28,29,30,31],"saas","supabase","anti-patterns","code-review","debugging","security","pitfalls","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Avoid and fix the most common Supabase mistakes: exposing service_role key\nin client bundles, forgetting to enable RLS, not using connection pooling\nin serverless, .single() throwing on empty results, missing .select() after\ninsert\u002Fupdate, not destructuring { data, error }, creating multiple client\ninstances, and not using generated types.\nUse when reviewing Supabase code, onboarding developers, auditing an\nexisting project, or debugging unexpected behavior.\nTrigger with phrases like \"supabase mistakes\", \"supabase anti-patterns\",\n\"supabase pitfalls\", \"supabase code review\", \"supabase gotchas\",\n\"supabase debugging\", \"what not to do supabase\", \"supabase common errors\".\n","Read, Grep","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--supabase-pack--supabase-known-pitfalls",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":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill supabase-known-pitfalls",{"tool":52,"command":53},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill supabase-known-pitfalls",{"tool":55,"command":56},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill supabase-known-pitfalls","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--supabase-pack--supabase-known-pitfalls\u002FSKILL.md",true,[],[61,68,75,82,89,97],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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",[],[]]