[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M796F4YFBEK1CYN7ZQREG972":3,"skill-same:01M796F4YFBEK1CYN7ZQREG972":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},"01M796F4YFBEK1CYN7ZQREG972","supabase-incident-runbook",null,"Execute Supabase incident response: dashboard health checks, connection pool status,\npg_stat_activity queries, RLS debugging, Edge Function logs, storage health, and escalation.\nUse when responding to Supabase outages, investigating production errors, debugging\nconnection issues, or preparing evidence for Supabase support escalation.\nTrigger: \"supabase incident\", \"supabase outage\", \"supabase down\", \"supabase on-call\",\n\"supabase emergency\", \"supabase broken\", \"supabase connection issues\".","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-incident-runbook\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: supabase-incident-runbook\ndescription: |\n  Execute Supabase incident response: dashboard health checks, connection pool status,\n  pg_stat_activity queries, RLS debugging, Edge Function logs, storage health, and escalation.\n  Use when responding to Supabase outages, investigating production errors, debugging\n  connection issues, or preparing evidence for Supabase support escalation.\n  Trigger: \"supabase incident\", \"supabase outage\", \"supabase down\", \"supabase on-call\",\n  \"supabase emergency\", \"supabase broken\", \"supabase connection issues\".\nallowed-tools: Read, Grep, Bash(npx supabase:*), Bash(supabase:*), Bash(curl:*), Bash(psql:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, supabase, incident-response, debugging, operations, runbook]\n---\n\n# Supabase Incident Runbook\n\n## Overview\n\nWhen a Supabase-backed application experiences failures, you need a structured response: verify the Supabase platform status, check your connection pool, inspect `pg_stat_activity` for stuck queries, debug RLS policies that silently filter data, review Edge Function execution logs, verify storage bucket health, and escalate to Supabase support with a complete evidence bundle. This runbook covers every layer from the SDK client through the database to platform services.\n\n**When to use:** Production errors involving Supabase, degraded API response times, connection pool exhaustion, silent data filtering from RLS, Edge Function cold start failures, or storage upload\u002Fdownload errors.\n\n## Prerequisites\n\n- Supabase project with dashboard access at [supabase.com\u002Fdashboard](https:\u002F\u002Fsupabase.com\u002Fdashboard)\n- `@supabase\u002Fsupabase-js` v2+ installed in your project\n- Supabase CLI installed for Edge Function log access\n- Direct database connection string (for `psql` diagnostics)\n- Access to [status.supabase.com](https:\u002F\u002Fstatus.supabase.com) for platform health\n\n## Instructions\n\n### Step 1: Triage — Platform vs. Application\n\nDetermine whether the issue is a Supabase platform incident or an application-level bug. Check platform status first, then verify your SDK client connectivity.\n\n**Check Supabase platform status:**\n\n```bash\n# Check official status page\ncurl -sf https:\u002F\u002Fstatus.supabase.com\u002Fapi\u002Fv2\u002Fstatus.json | jq '{\n  indicator: .status.indicator,\n  description: .status.description\n}'\n# Expected: { \"indicator\": \"none\", \"description\": \"All Systems Operational\" }\n\n# Check for active incidents\ncurl -sf https:\u002F\u002Fstatus.supabase.com\u002Fapi\u002Fv2\u002Fincidents\u002Funresolved.json | jq '.incidents[] | {\n  name: .name,\n  status: .status,\n  impact: .impact,\n  created_at: .created_at\n}'\n```\n\n**Verify SDK client connectivity from your application:**\n\n```typescript\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!\n);\n\n\u002F\u002F Quick health check — select 1 from a small table\nasync function healthCheck(): Promise\u003C{\n  status: 'healthy' | 'degraded' | 'down';\n  latencyMs: number;\n  error?: string;\n}> {\n  const start = performance.now();\n  try {\n    const { data, error } = await supabase\n      .from('_health_check')\n      .select('id')\n      .limit(1)\n      .maybeSingle();\n\n    const latencyMs = Math.round(performance.now() - start);\n\n    if (error) {\n      return { status: 'degraded', latencyMs, error: error.message };\n    }\n\n    return {\n      status: latencyMs > 2000 ? 'degraded' : 'healthy',\n      latencyMs,\n    };\n  } catch (err) {\n    return {\n      status: 'down',\n      latencyMs: Math.round(performance.now() - start),\n      error: err instanceof Error ? err.message : 'Unknown error',\n    };\n  }\n}\n\n\u002F\u002F Create a minimal health check table (run once)\n\u002F\u002F CREATE TABLE _health_check (id int PRIMARY KEY DEFAULT 1);\n\u002F\u002F INSERT INTO _health_check VALUES (1);\n\u002F\u002F ALTER TABLE _health_check ENABLE ROW LEVEL SECURITY;\n\u002F\u002F CREATE POLICY \"allow_anon_read\" ON _health_check FOR SELECT USING (true);\n```\n\n**Decision tree:**\n\n```\nIs status.supabase.com showing an incident?\n├─ YES → Supabase platform issue\n│   ├─ Enable fallback\u002Fcache layer\n│   ├─ Monitor status page for resolution\n│   └─ Skip to Step 3 for connection pool protection\n└─ NO → Application-level issue\n    ├─ Does healthCheck() return 'healthy'?\n    │   ├─ YES → Issue is in your queries\u002FRLS\u002FEdge Functions → Step 2\n    │   └─ NO → Connection or auth issue → Step 2 + Step 3\n    └─ Check error codes: 401=auth, 429=rate limit, 500=server error\n```\n\n### Step 2: Database Diagnostics with pg_stat_activity\n\nConnect directly to the database to inspect active connections, find stuck queries, and detect connection leaks. These queries run via `psql` or the Supabase SQL Editor.\n\n**Connection pool status:**\n\n```sql\n-- Current connections grouped by state\nSELECT state, count(*) AS connections,\n       max(extract(epoch FROM age(now(), state_change)))::int AS max_idle_seconds\nFROM pg_stat_activity\nWHERE datname = current_database()\nGROUP BY state\nORDER BY connections DESC;\n\n-- Expected healthy output:\n-- state  | connections | max_idle_seconds\n-- idle   | 3           | 12\n-- active | 1           | 0\n--        | 2           | (null)  ← background workers\n\n-- WARNING: If idle > 20 or idle_in_transaction > 0, you have a leak\n```\n\n**Find long-running and stuck queries:**\n\n```sql\n-- Queries running longer than 10 seconds\nSELECT pid, usename, state,\n       age(now(), query_start)::text AS duration,\n       wait_event_type, wait_event,\n       left(query, 120) AS query_preview\nFROM pg_stat_activity\nWHERE state = 'active'\n  AND query NOT LIKE '%pg_stat_activity%'\n  AND age(now(), query_start) > interval '10 seconds'\nORDER BY query_start;\n\n-- Idle-in-transaction connections (connection leak indicator)\nSELECT pid, usename,\n       age(now(), state_change)::text AS idle_duration,\n       left(query, 100) AS last_query\nFROM pg_stat_activity\nWHERE state = 'idle in transaction'\nORDER BY state_change;\n\n-- Kill a specific stuck query (use with caution)\n-- SELECT pg_cancel_backend(\u003Cpid>);       -- graceful cancel\n-- SELECT pg_terminate_backend(\u003Cpid>);    -- force kill\n```\n\n**Check connection limits:**\n\n```sql\n-- Are we near the connection limit?\nSELECT\n  max_conn,\n  used,\n  max_conn - used AS available,\n  round(100.0 * used \u002F max_conn, 1) AS pct_used\nFROM (SELECT count(*) AS used FROM pg_stat_activity) t,\n     (SELECT setting::int AS max_conn FROM pg_settings WHERE name = 'max_connections') s;\n\n-- If pct_used > 80%, you need connection pooling via Supavisor\n-- Dashboard → Project Settings → Database → Connection Pooling\n```\n\n**Application-side connection monitoring:**\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nconst supabase = createClient(\n  process.env.NEXT_PUBLIC_SUPABASE_URL!,\n  process.env.SUPABASE_SERVICE_ROLE_KEY!,\n  { auth: { autoRefreshToken: false, persistSession: false } }\n);\n\n\u002F\u002F Monitor connection health from the application\nasync function getConnectionStats() {\n  const { data, error } = await supabase.rpc('get_connection_stats');\n  if (error) throw error;\n  return data;\n}\n\n\u002F\u002F Create this function in your database:\n\u002F\u002F CREATE OR REPLACE FUNCTION get_connection_stats()\n\u002F\u002F RETURNS json AS $$\n\u002F\u002F   SELECT json_build_object(\n\u002F\u002F     'active', (SELECT count(*) FROM pg_stat_activity WHERE state = 'active'),\n\u002F\u002F     'idle', (SELECT count(*) FROM pg_stat_activity WHERE state = 'idle'),\n\u002F\u002F     'idle_in_tx', (SELECT count(*) FROM pg_stat_activity WHERE state = 'idle in transaction'),\n\u002F\u002F     'total', (SELECT count(*) FROM pg_stat_activity WHERE datname = current_database()),\n\u002F\u002F     'max', (SELECT setting::int FROM pg_settings WHERE name = 'max_connections')\n\u002F\u002F   );\n\u002F\u002F $$ LANGUAGE sql SECURITY DEFINER;\n```\n\n### Step 3: RLS Debugging, Edge Functions, and Storage\n\nDebug silent data filtering from Row Level Security policies, inspect Edge Function execution, and verify storage bucket health.\n\n**RLS policy debugging:**\n\n```sql\n-- List all RLS policies on a table\nSELECT policyname, cmd, permissive,\n       pg_get_expr(qual, polrelid) AS using_expression,\n       pg_get_expr(with_check, polrelid) AS with_check_expression\nFROM pg_policy\nJOIN pg_class ON pg_class.oid = polrelid\nWHERE relname = 'your_table_name';\n\n-- Test as a specific user (simulates their JWT in SQL Editor)\nSET request.jwt.claim.sub = 'target-user-uuid';\nSET request.jwt.claim.role = 'authenticated';\n\n-- Run the query that's failing\nSELECT * FROM your_table_name WHERE user_id = 'target-user-uuid';\n-- If empty but data exists → RLS is filtering incorrectly\n\n-- Verify what auth.uid() resolves to\nSELECT auth.uid();\nSELECT auth.jwt();\n\n-- Compare with service role (bypasses RLS)\n-- Use service_role key in createClient to confirm data exists\n\n-- Reset after testing\nRESET request.jwt.claim.sub;\nRESET request.jwt.claim.role;\n```\n\n**RLS debugging from the SDK:**\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\n\u002F\u002F Anon client — respects RLS\nconst anonClient = createClient(url, anonKey);\n\n\u002F\u002F Service role client — bypasses RLS\nconst adminClient = createClient(url, serviceRoleKey, {\n  auth: { autoRefreshToken: false, persistSession: false },\n});\n\nasync function debugRLS(table: string, userId: string) {\n  \u002F\u002F Query with RLS (what the user sees)\n  const { data: rlsData, error: rlsError } = await anonClient\n    .from(table)\n    .select('*')\n    .eq('user_id', userId);\n\n  \u002F\u002F Query without RLS (what actually exists)\n  const { data: adminData, error: adminError } = await adminClient\n    .from(table)\n    .select('*')\n    .eq('user_id', userId);\n\n  console.log('With RLS:', rlsData?.length ?? 0, 'rows', rlsError?.message ?? 'OK');\n  console.log('Without RLS:', adminData?.length ?? 0, 'rows', adminError?.message ?? 'OK');\n\n  if ((adminData?.length ?? 0) > (rlsData?.length ?? 0)) {\n    console.warn('RLS is filtering rows — check policies on', table);\n  }\n}\n```\n\n**Edge Function log inspection:**\n\n```bash\n# View recent Edge Function logs\nnpx supabase functions logs my-function --project-ref \u003Cproject-ref>\n\n# Tail logs in real-time during debugging\nnpx supabase functions serve my-function --debug --env-file .env.local\n\n# Check function deployment status\nnpx supabase functions list --project-ref \u003Cproject-ref>\n\n# Common Edge Function issues:\n# - Cold starts > 1s: function needs warm-up or is too large\n# - WORKER_LIMIT error: function exceeded memory\u002FCPU\n# - ImportError: missing dependency in import_map.json\n```\n\n**Edge Function health check from SDK:**\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nconst supabase = createClient(url, anonKey);\n\nasync function checkEdgeFunction(functionName: string) {\n  const start = performance.now();\n  const { data, error } = await supabase.functions.invoke(functionName, {\n    body: { action: 'health-check' },\n  });\n  const duration = Math.round(performance.now() - start);\n\n  console.log(`Edge Function \"${functionName}\":`, {\n    status: error ? 'error' : 'ok',\n    durationMs: duration,\n    coldStart: duration > 1000,\n    error: error?.message,\n  });\n}\n```\n\n**Storage bucket health:**\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nconst supabase = createClient(url, serviceRoleKey, {\n  auth: { autoRefreshToken: false, persistSession: false },\n});\n\nasync function checkStorageHealth() {\n  \u002F\u002F List all buckets\n  const { data: buckets, error: listError } = await supabase.storage.listBuckets();\n  if (listError) {\n    console.error('Cannot list buckets:', listError.message);\n    return;\n  }\n\n  for (const bucket of buckets ?? []) {\n    \u002F\u002F Try listing files in each bucket\n    const { data: files, error: filesError } = await supabase.storage\n      .from(bucket.name)\n      .list('', { limit: 1 });\n\n    console.log(`Bucket \"${bucket.name}\":`, {\n      public: bucket.public,\n      accessible: !filesError,\n      error: filesError?.message,\n    });\n  }\n\n  \u002F\u002F Test upload\u002Fdownload cycle\n  const testFile = new Blob(['health-check'], { type: 'text\u002Fplain' });\n  const testPath = `_health_check\u002F${Date.now()}.txt`;\n\n  const { error: uploadError } = await supabase.storage\n    .from('test-bucket')\n    .upload(testPath, testFile);\n\n  if (!uploadError) {\n    await supabase.storage.from('test-bucket').remove([testPath]);\n    console.log('Storage upload\u002Fdownload: OK');\n  } else {\n    console.error('Storage upload failed:', uploadError.message);\n  }\n}\n```\n\n## Output\n\nAfter running this incident runbook, you will have:\n\n- **Platform status assessment** — confirmed whether the issue is Supabase-side or application-side\n- **SDK health check** — latency measurement and connectivity verification via `createClient`\n- **Connection pool analysis** — `pg_stat_activity` showing active, idle, and leaked connections\n- **Long-running query identification** — stuck queries with PIDs ready for cancellation\n- **RLS policy diagnosis** — side-by-side comparison of anon vs. service role query results\n- **Edge Function status** — deployment status, cold start detection, and log inspection\n- **Storage health report** — bucket accessibility and upload\u002Fdownload verification\n- **Evidence bundle** — complete diagnostic data for Supabase support escalation\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `FetchError: request failed` | Supabase API unreachable | Check status.supabase.com; verify network\u002FDNS |\n| `connection refused` on port 5432 | Direct DB access blocked or wrong credentials | Use pooler URL (port 6543) or check dashboard connection strings |\n| `too many clients already` | Connection pool exhausted | Kill idle-in-transaction connections; enable Supavisor pooling |\n| `permission denied for table` | RLS blocking or wrong role | Check policies with `pg_policy`; verify JWT claims |\n| `WORKER_LIMIT` in Edge Function | Memory\u002FCPU exceeded | Reduce function payload size; optimize imports |\n| `JWT expired` | Token not refreshing | Verify `autoRefreshToken: true` in `createClient` options |\n| `storage\u002Fobject-not-found` | File deleted or wrong path | Check bucket policies; verify path with service role client |\n| `rate limit exceeded` (429) | Too many API requests | Implement exponential backoff; contact Supabase for limit increase |\n\n## Examples\n\n**Example 1 — Quick triage script:**\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nasync function triageSupabase() {\n  const supabase = createClient(\n    process.env.NEXT_PUBLIC_SUPABASE_URL!,\n    process.env.SUPABASE_SERVICE_ROLE_KEY!,\n    { auth: { autoRefreshToken: false, persistSession: false } }\n  );\n\n  \u002F\u002F 1. Database connectivity\n  const { error: dbError } = await supabase.from('_health_check').select('id').limit(1);\n  console.log('Database:', dbError ? `ERROR: ${dbError.message}` : 'OK');\n\n  \u002F\u002F 2. Auth service\n  const { data: authData, error: authError } = await supabase.auth.getSession();\n  console.log('Auth service:', authError ? `ERROR: ${authError.message}` : 'OK');\n\n  \u002F\u002F 3. Storage service\n  const { error: storageError } = await supabase.storage.listBuckets();\n  console.log('Storage:', storageError ? `ERROR: ${storageError.message}` : 'OK');\n\n  \u002F\u002F 4. Realtime service\n  const channel = supabase.channel('health');\n  channel.subscribe((status) => {\n    console.log('Realtime:', status);\n    channel.unsubscribe();\n  });\n}\n```\n\n**Example 2 — Connection leak detector:**\n\n```sql\n-- Run this during an incident to find leaked connections\nWITH connection_summary AS (\n  SELECT usename, state,\n         count(*) AS conn_count,\n         max(age(now(), state_change)) AS max_age\n  FROM pg_stat_activity\n  WHERE datname = current_database()\n  GROUP BY usename, state\n)\nSELECT usename, state, conn_count,\n       max_age::text AS max_idle_time,\n       CASE\n         WHEN state = 'idle in transaction' THEN 'LEAK - kill these'\n         WHEN state = 'idle' AND max_age > interval '10 minutes' THEN 'STALE - review'\n         ELSE 'OK'\n       END AS assessment\nFROM connection_summary\nORDER BY conn_count DESC;\n```\n\n**Example 3 — Escalation evidence bundle:**\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nasync function buildEvidenceBundle() {\n  const supabase = createClient(url, serviceRoleKey, {\n    auth: { autoRefreshToken: false, persistSession: false },\n  });\n\n  const evidence = {\n    timestamp: new Date().toISOString(),\n    projectRef: process.env.SUPABASE_PROJECT_REF,\n    symptoms: [],\n    diagnostics: {},\n  };\n\n  \u002F\u002F Collect connection stats\n  const { data: connStats } = await supabase.rpc('get_connection_stats');\n  evidence.diagnostics['connections'] = connStats;\n\n  \u002F\u002F Collect recent errors from your error tracking\n  evidence.symptoms.push('Describe the user-facing symptoms here');\n\n  \u002F\u002F Include request IDs from failed API calls\n  \u002F\u002F The x-request-id header from Supabase responses identifies specific requests\n\n  console.log('Evidence bundle for Supabase support:');\n  console.log(JSON.stringify(evidence, null, 2));\n  \u002F\u002F Submit at: https:\u002F\u002Fsupabase.com\u002Fdashboard\u002Fsupport\n}\n```\n\n## Resources\n\n- [Supabase Status Page](https:\u002F\u002Fstatus.supabase.com)\n- [Supabase Support Portal](https:\u002F\u002Fsupabase.com\u002Fdashboard\u002Fsupport)\n- [Database Health — Supabase Docs](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Finspect)\n- [RLS Debugging — Supabase Docs](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Ftroubleshooting\u002Frls-simplified-BJTcS8)\n- [Edge Functions Logs — Supabase Docs](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Ffunctions\u002Flogging)\n- [Connection Pooling with Supavisor](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fconnecting-to-postgres#connection-pooler)\n- [pg_stat_activity — PostgreSQL Docs](https:\u002F\u002Fwww.postgresql.org\u002Fdocs\u002Fcurrent\u002Fmonitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW)\n\n## Next Steps\n\n- For GDPR compliance and data handling, see `supabase-data-handling`\n- For performance tuning and query optimization, see `supabase-performance-tuning`\n- For observability and monitoring setup, see `supabase-observability`\n- For common error patterns and fixes, see `supabase-common-errors`\n","# Supabase Incident Runbook\n\n## Overview\n\nWhen a Supabase-backed application experiences failures, you need a structured response: verify the Supabase platform status, check your connection pool, inspect `pg_stat_activity` for stuck queries, debug RLS policies that silently filter data, review Edge Function execution logs, verify storage bucket health, and escalate to Supabase support with a complete evidence bundle. This runbook covers every layer from the SDK client through the database to platform services.\n\n**When to use:** Production errors involving Supabase, degraded API response times, connection pool exhaustion, silent data filtering from RLS, Edge Function cold start failures, or storage upload\u002Fdownload errors.\n\n## Prerequisites\n\n- Supabase project with dashboard access at [supabase.com\u002Fdashboard](https:\u002F\u002Fsupabase.com\u002Fdashboard)\n- `@supabase\u002Fsupabase-js` v2+ installed in your project\n- Supabase CLI installed for Edge Function log access\n- Direct database connection string (for `psql` diagnostics)\n- Access to [status.supabase.com](https:\u002F\u002Fstatus.supabase.com) for platform health\n\n## Instructions\n\n### Step 1: Triage — Platform vs. Application\n\nDetermine whether the issue is a Supabase platform incident or an application-level bug. Check platform status first, then verify your SDK client connectivity.\n\n**Check Supabase platform status:**\n\n```bash\n# Check official status page\ncurl -sf https:\u002F\u002Fstatus.supabase.com\u002Fapi\u002Fv2\u002Fstatus.json | jq '{\n  indicator: .status.indicator,\n  description: .status.description\n}'\n# Expected: { \"indicator\": \"none\", \"description\": \"All Systems Operational\" }\n\n# Check for active incidents\ncurl -sf https:\u002F\u002Fstatus.supabase.com\u002Fapi\u002Fv2\u002Fincidents\u002Funresolved.json | jq '.incidents[] | {\n  name: .name,\n  status: .status,\n  impact: .impact,\n  created_at: .created_at\n}'\n```\n\n**Verify SDK client connectivity from your application:**\n\n```typescript\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!\n);\n\n\u002F\u002F Quick health check — select 1 from a small table\nasync function healthCheck(): Promise\u003C{\n  status: 'healthy' | 'degraded' | 'down';\n  latencyMs: number;\n  error?: string;\n}> {\n  const start = performance.now();\n  try {\n    const { data, error } = await supabase\n      .from('_health_check')\n      .select('id')\n      .limit(1)\n      .maybeSingle();\n\n    const latencyMs = Math.round(performance.now() - start);\n\n    if (error) {\n      return { status: 'degraded', latencyMs, error: error.message };\n    }\n\n    return {\n      status: latencyMs > 2000 ? 'degraded' : 'healthy',\n      latencyMs,\n    };\n  } catch (err) {\n    return {\n      status: 'down',\n      latencyMs: Math.round(performance.now() - start),\n      error: err instanceof Error ? err.message : 'Unknown error',\n    };\n  }\n}\n\n\u002F\u002F Create a minimal health check table (run once)\n\u002F\u002F CREATE TABLE _health_check (id int PRIMARY KEY DEFAULT 1);\n\u002F\u002F INSERT INTO _health_check VALUES (1);\n\u002F\u002F ALTER TABLE _health_check ENABLE ROW LEVEL SECURITY;\n\u002F\u002F CREATE POLICY \"allow_anon_read\" ON _health_check FOR SELECT USING (true);\n```\n\n**Decision tree:**\n\n```\nIs status.supabase.com showing an incident?\n├─ YES → Supabase platform issue\n│   ├─ Enable fallback\u002Fcache layer\n│   ├─ Monitor status page for resolution\n│   └─ Skip to Step 3 for connection pool protection\n└─ NO → Application-level issue\n    ├─ Does healthCheck() return 'healthy'?\n    │   ├─ YES → Issue is in your queries\u002FRLS\u002FEdge Functions → Step 2\n    │   └─ NO → Connection or auth issue → Step 2 + Step 3\n    └─ Check error codes: 401=auth, 429=rate limit, 500=server error\n```\n\n### Step 2: Database Diagnostics with pg_stat_activity\n\nConnect directly to the database to inspect active connections, find stuck queries, and detect connection leaks. These queries run via `psql` or the Supabase SQL Editor.\n\n**Connection pool status:**\n\n```sql\n-- Current connections grouped by state\nSELECT state, count(*) AS connections,\n       max(extract(epoch FROM age(now(), state_change)))::int AS max_idle_seconds\nFROM pg_stat_activity\nWHERE datname = current_database()\nGROUP BY state\nORDER BY connections DESC;\n\n-- Expected healthy output:\n-- state  | connections | max_idle_seconds\n-- idle   | 3           | 12\n-- active | 1           | 0\n--        | 2           | (null)  ← background workers\n\n-- WARNING: If idle > 20 or idle_in_transaction > 0, you have a leak\n```\n\n**Find long-running and stuck queries:**\n\n```sql\n-- Queries running longer than 10 seconds\nSELECT pid, usename, state,\n       age(now(), query_start)::text AS duration,\n       wait_event_type, wait_event,\n       left(query, 120) AS query_preview\nFROM pg_stat_activity\nWHERE state = 'active'\n  AND query NOT LIKE '%pg_stat_activity%'\n  AND age(now(), query_start) > interval '10 seconds'\nORDER BY query_start;\n\n-- Idle-in-transaction connections (connection leak indicator)\nSELECT pid, usename,\n       age(now(), state_change)::text AS idle_duration,\n       left(query, 100) AS last_query\nFROM pg_stat_activity\nWHERE state = 'idle in transaction'\nORDER BY state_change;\n\n-- Kill a specific stuck query (use with caution)\n-- SELECT pg_cancel_backend(\u003Cpid>);       -- graceful cancel\n-- SELECT pg_terminate_backend(\u003Cpid>);    -- force kill\n```\n\n**Check connection limits:**\n\n```sql\n-- Are we near the connection limit?\nSELECT\n  max_conn,\n  used,\n  max_conn - used AS available,\n  round(100.0 * used \u002F max_conn, 1) AS pct_used\nFROM (SELECT count(*) AS used FROM pg_stat_activity) t,\n     (SELECT setting::int AS max_conn FROM pg_settings WHERE name = 'max_connections') s;\n\n-- If pct_used > 80%, you need connection pooling via Supavisor\n-- Dashboard → Project Settings → Database → Connection Pooling\n```\n\n**Application-side connection monitoring:**\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nconst supabase = createClient(\n  process.env.NEXT_PUBLIC_SUPABASE_URL!,\n  process.env.SUPABASE_SERVICE_ROLE_KEY!,\n  { auth: { autoRefreshToken: false, persistSession: false } }\n);\n\n\u002F\u002F Monitor connection health from the application\nasync function getConnectionStats() {\n  const { data, error } = await supabase.rpc('get_connection_stats');\n  if (error) throw error;\n  return data;\n}\n\n\u002F\u002F Create this function in your database:\n\u002F\u002F CREATE OR REPLACE FUNCTION get_connection_stats()\n\u002F\u002F RETURNS json AS $$\n\u002F\u002F   SELECT json_build_object(\n\u002F\u002F     'active', (SELECT count(*) FROM pg_stat_activity WHERE state = 'active'),\n\u002F\u002F     'idle', (SELECT count(*) FROM pg_stat_activity WHERE state = 'idle'),\n\u002F\u002F     'idle_in_tx', (SELECT count(*) FROM pg_stat_activity WHERE state = 'idle in transaction'),\n\u002F\u002F     'total', (SELECT count(*) FROM pg_stat_activity WHERE datname = current_database()),\n\u002F\u002F     'max', (SELECT setting::int FROM pg_settings WHERE name = 'max_connections')\n\u002F\u002F   );\n\u002F\u002F $$ LANGUAGE sql SECURITY DEFINER;\n```\n\n### Step 3: RLS Debugging, Edge Functions, and Storage\n\nDebug silent data filtering from Row Level Security policies, inspect Edge Function execution, and verify storage bucket health.\n\n**RLS policy debugging:**\n\n```sql\n-- List all RLS policies on a table\nSELECT policyname, cmd, permissive,\n       pg_get_expr(qual, polrelid) AS using_expression,\n       pg_get_expr(with_check, polrelid) AS with_check_expression\nFROM pg_policy\nJOIN pg_class ON pg_class.oid = polrelid\nWHERE relname = 'your_table_name';\n\n-- Test as a specific user (simulates their JWT in SQL Editor)\nSET request.jwt.claim.sub = 'target-user-uuid';\nSET request.jwt.claim.role = 'authenticated';\n\n-- Run the query that's failing\nSELECT * FROM your_table_name WHERE user_id = 'target-user-uuid';\n-- If empty but data exists → RLS is filtering incorrectly\n\n-- Verify what auth.uid() resolves to\nSELECT auth.uid();\nSELECT auth.jwt();\n\n-- Compare with service role (bypasses RLS)\n-- Use service_role key in createClient to confirm data exists\n\n-- Reset after testing\nRESET request.jwt.claim.sub;\nRESET request.jwt.claim.role;\n```\n\n**RLS debugging from the SDK:**\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\n\u002F\u002F Anon client — respects RLS\nconst anonClient = createClient(url, anonKey);\n\n\u002F\u002F Service role client — bypasses RLS\nconst adminClient = createClient(url, serviceRoleKey, {\n  auth: { autoRefreshToken: false, persistSession: false },\n});\n\nasync function debugRLS(table: string, userId: string) {\n  \u002F\u002F Query with RLS (what the user sees)\n  const { data: rlsData, error: rlsError } = await anonClient\n    .from(table)\n    .select('*')\n    .eq('user_id', userId);\n\n  \u002F\u002F Query without RLS (what actually exists)\n  const { data: adminData, error: adminError } = await adminClient\n    .from(table)\n    .select('*')\n    .eq('user_id', userId);\n\n  console.log('With RLS:', rlsData?.length ?? 0, 'rows', rlsError?.message ?? 'OK');\n  console.log('Without RLS:', adminData?.length ?? 0, 'rows', adminError?.message ?? 'OK');\n\n  if ((adminData?.length ?? 0) > (rlsData?.length ?? 0)) {\n    console.warn('RLS is filtering rows — check policies on', table);\n  }\n}\n```\n\n**Edge Function log inspection:**\n\n```bash\n# View recent Edge Function logs\nnpx supabase functions logs my-function --project-ref \u003Cproject-ref>\n\n# Tail logs in real-time during debugging\nnpx supabase functions serve my-function --debug --env-file .env.local\n\n# Check function deployment status\nnpx supabase functions list --project-ref \u003Cproject-ref>\n\n# Common Edge Function issues:\n# - Cold starts > 1s: function needs warm-up or is too large\n# - WORKER_LIMIT error: function exceeded memory\u002FCPU\n# - ImportError: missing dependency in import_map.json\n```\n\n**Edge Function health check from SDK:**\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nconst supabase = createClient(url, anonKey);\n\nasync function checkEdgeFunction(functionName: string) {\n  const start = performance.now();\n  const { data, error } = await supabase.functions.invoke(functionName, {\n    body: { action: 'health-check' },\n  });\n  const duration = Math.round(performance.now() - start);\n\n  console.log(`Edge Function \"${functionName}\":`, {\n    status: error ? 'error' : 'ok',\n    durationMs: duration,\n    coldStart: duration > 1000,\n    error: error?.message,\n  });\n}\n```\n\n**Storage bucket health:**\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nconst supabase = createClient(url, serviceRoleKey, {\n  auth: { autoRefreshToken: false, persistSession: false },\n});\n\nasync function checkStorageHealth() {\n  \u002F\u002F List all buckets\n  const { data: buckets, error: listError } = await supabase.storage.listBuckets();\n  if (listError) {\n    console.error('Cannot list buckets:', listError.message);\n    return;\n  }\n\n  for (const bucket of buckets ?? []) {\n    \u002F\u002F Try listing files in each bucket\n    const { data: files, error: filesError } = await supabase.storage\n      .from(bucket.name)\n      .list('', { limit: 1 });\n\n    console.log(`Bucket \"${bucket.name}\":`, {\n      public: bucket.public,\n      accessible: !filesError,\n      error: filesError?.message,\n    });\n  }\n\n  \u002F\u002F Test upload\u002Fdownload cycle\n  const testFile = new Blob(['health-check'], { type: 'text\u002Fplain' });\n  const testPath = `_health_check\u002F${Date.now()}.txt`;\n\n  const { error: uploadError } = await supabase.storage\n    .from('test-bucket')\n    .upload(testPath, testFile);\n\n  if (!uploadError) {\n    await supabase.storage.from('test-bucket').remove([testPath]);\n    console.log('Storage upload\u002Fdownload: OK');\n  } else {\n    console.error('Storage upload failed:', uploadError.message);\n  }\n}\n```\n\n## Output\n\nAfter running this incident runbook, you will have:\n\n- **Platform status assessment** — confirmed whether the issue is Supabase-side or application-side\n- **SDK health check** — latency measurement and connectivity verification via `createClient`\n- **Connection pool analysis** — `pg_stat_activity` showing active, idle, and leaked connections\n- **Long-running query identification** — stuck queries with PIDs ready for cancellation\n- **RLS policy diagnosis** — side-by-side comparison of anon vs. service role query results\n- **Edge Function status** — deployment status, cold start detection, and log inspection\n- **Storage health report** — bucket accessibility and upload\u002Fdownload verification\n- **Evidence bundle** — complete diagnostic data for Supabase support escalation\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `FetchError: request failed` | Supabase API unreachable | Check status.supabase.com; verify network\u002FDNS |\n| `connection refused` on port 5432 | Direct DB access blocked or wrong credentials | Use pooler URL (port 6543) or check dashboard connection strings |\n| `too many clients already` | Connection pool exhausted | Kill idle-in-transaction connections; enable Supavisor pooling |\n| `permission denied for table` | RLS blocking or wrong role | Check policies with `pg_policy`; verify JWT claims |\n| `WORKER_LIMIT` in Edge Function | Memory\u002FCPU exceeded | Reduce function payload size; optimize imports |\n| `JWT expired` | Token not refreshing | Verify `autoRefreshToken: true` in `createClient` options |\n| `storage\u002Fobject-not-found` | File deleted or wrong path | Check bucket policies; verify path with service role client |\n| `rate limit exceeded` (429) | Too many API requests | Implement exponential backoff; contact Supabase for limit increase |\n\n## Examples\n\n**Example 1 — Quick triage script:**\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nasync function triageSupabase() {\n  const supabase = createClient(\n    process.env.NEXT_PUBLIC_SUPABASE_URL!,\n    process.env.SUPABASE_SERVICE_ROLE_KEY!,\n    { auth: { autoRefreshToken: false, persistSession: false } }\n  );\n\n  \u002F\u002F 1. Database connectivity\n  const { error: dbError } = await supabase.from('_health_check').select('id').limit(1);\n  console.log('Database:', dbError ? `ERROR: ${dbError.message}` : 'OK');\n\n  \u002F\u002F 2. Auth service\n  const { data: authData, error: authError } = await supabase.auth.getSession();\n  console.log('Auth service:', authError ? `ERROR: ${authError.message}` : 'OK');\n\n  \u002F\u002F 3. Storage service\n  const { error: storageError } = await supabase.storage.listBuckets();\n  console.log('Storage:', storageError ? `ERROR: ${storageError.message}` : 'OK');\n\n  \u002F\u002F 4. Realtime service\n  const channel = supabase.channel('health');\n  channel.subscribe((status) => {\n    console.log('Realtime:', status);\n    channel.unsubscribe();\n  });\n}\n```\n\n**Example 2 — Connection leak detector:**\n\n```sql\n-- Run this during an incident to find leaked connections\nWITH connection_summary AS (\n  SELECT usename, state,\n         count(*) AS conn_count,\n         max(age(now(), state_change)) AS max_age\n  FROM pg_stat_activity\n  WHERE datname = current_database()\n  GROUP BY usename, state\n)\nSELECT usename, state, conn_count,\n       max_age::text AS max_idle_time,\n       CASE\n         WHEN state = 'idle in transaction' THEN 'LEAK - kill these'\n         WHEN state = 'idle' AND max_age > interval '10 minutes' THEN 'STALE - review'\n         ELSE 'OK'\n       END AS assessment\nFROM connection_summary\nORDER BY conn_count DESC;\n```\n\n**Example 3 — Escalation evidence bundle:**\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js';\n\nasync function buildEvidenceBundle() {\n  const supabase = createClient(url, serviceRoleKey, {\n    auth: { autoRefreshToken: false, persistSession: false },\n  });\n\n  const evidence = {\n    timestamp: new Date().toISOString(),\n    projectRef: process.env.SUPABASE_PROJECT_REF,\n    symptoms: [],\n    diagnostics: {},\n  };\n\n  \u002F\u002F Collect connection stats\n  const { data: connStats } = await supabase.rpc('get_connection_stats');\n  evidence.diagnostics['connections'] = connStats;\n\n  \u002F\u002F Collect recent errors from your error tracking\n  evidence.symptoms.push('Describe the user-facing symptoms here');\n\n  \u002F\u002F Include request IDs from failed API calls\n  \u002F\u002F The x-request-id header from Supabase responses identifies specific requests\n\n  console.log('Evidence bundle for Supabase support:');\n  console.log(JSON.stringify(evidence, null, 2));\n  \u002F\u002F Submit at: https:\u002F\u002Fsupabase.com\u002Fdashboard\u002Fsupport\n}\n```\n\n## Resources\n\n- [Supabase Status Page](https:\u002F\u002Fstatus.supabase.com)\n- [Supabase Support Portal](https:\u002F\u002Fsupabase.com\u002Fdashboard\u002Fsupport)\n- [Database Health — Supabase Docs](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Finspect)\n- [RLS Debugging — Supabase Docs](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Ftroubleshooting\u002Frls-simplified-BJTcS8)\n- [Edge Functions Logs — Supabase Docs](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Ffunctions\u002Flogging)\n- [Connection Pooling with Supavisor](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fconnecting-to-postgres#connection-pooler)\n- [pg_stat_activity — PostgreSQL Docs](https:\u002F\u002Fwww.postgresql.org\u002Fdocs\u002Fcurrent\u002Fmonitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW)\n\n## Next Steps\n\n- For GDPR compliance and data handling, see `supabase-data-handling`\n- For performance tuning and query optimization, see `supabase-performance-tuning`\n- For observability and monitoring setup, see `supabase-observability`\n- For common error patterns and fixes, see `supabase-common-errors`\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","incident-response","debugging","operations","runbook","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute Supabase incident response: dashboard health checks, connection pool status,\npg_stat_activity queries, RLS debugging, Edge Function logs, storage health, and escalation.\nUse when responding to Supabase outages, investigating production errors, debugging\nconnection issues, or preparing evidence for Supabase support escalation.\nTrigger: \"supabase incident\", \"supabase outage\", \"supabase down\", \"supabase on-call\",\n\"supabase emergency\", \"supabase broken\", \"supabase connection issues\".\n","Read, Grep, Bash(npx supabase:*), Bash(supabase:*), Bash(curl:*), Bash(psql:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--supabase-pack--supabase-incident-runbook",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-incident-runbook",{"tool":51,"command":52},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill supabase-incident-runbook",{"tool":54,"command":55},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill supabase-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--supabase-pack--supabase-incident-runbook\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",[],[]]