[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76P02S402CP99F6CT2B84QN":3,"skill-same:01M76P02S402CP99F6CT2B84QN":63},{"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":29,"commitSha":30,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M76P02S402CP99F6CT2B84QN","supabase-incident-runbook",null,"Execute Supabase incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Supabase-related outages, investigating errors,\nor running post-incident reviews for Supabase integration failures.\nTrigger with phrases like \"supabase incident\", \"supabase outage\",\n\"supabase down\", \"supabase on-call\", \"supabase emergency\", \"supabase broken\".","SamuelChien\u002Fmega-skills-collection","SamuelChien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4652114?v=4","01M74KK34WVHA0P5ZYSJRDDFMG","Samuel Chien","01M74KK35FQN1N9VZ9EPTH3P2S",0,"MIT","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fsupabase-incident-runbook\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: supabase-incident-runbook\ndescription: |\n  Execute Supabase incident response procedures with triage, mitigation, and postmortem.\n  Use when responding to Supabase-related outages, investigating errors,\n  or running post-incident reviews for Supabase integration failures.\n  Trigger with phrases like \"supabase incident\", \"supabase outage\",\n  \"supabase down\", \"supabase on-call\", \"supabase emergency\", \"supabase broken\".\nallowed-tools: Read, Grep, Bash(kubectl:*), Bash(curl:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Supabase Incident Runbook\n\n## Prerequisites\n- Access to Supabase dashboard and status page\n- kubectl access to production cluster\n- Prometheus\u002FGrafana access\n- Communication channels (Slack, PagerDuty)\n\n## Instructions\n\nIncident response for Supabase integrations requires distinguishing quickly between platform-side outages (check status.supabase.com) and issues in your own integration code or infrastructure. Misattributing a platform outage as an internal bug wastes critical time during an incident. Always verify the Supabase status page before investing engineering effort in local remediation.\n\n### Step 1: Quick Triage\nRun the triage commands to identify the issue source. Check Supabase status page, verify your API credentials have not expired, and run a minimal health check query against your Supabase instance. Compare error rates against your baseline metrics to understand the scope and onset time.\n\n### Step 2: Follow Decision Tree\nDetermine if the issue is Supabase-side or internal. Platform outages require monitoring the status page and communicating degraded service to users. Internal issues require examining your application logs, recent deployments, and configuration changes for the root cause.\n\n### Step 3: Execute Immediate Actions\nApply the appropriate remediation for the error type. For connection failures, enable circuit breakers and fallback responses. For data inconsistencies, pause write operations to prevent further corruption while you investigate.\n\n### Step 4: Communicate Status\nUpdate internal and external stakeholders. Provide clear, jargon-free status updates at regular intervals. Avoid speculation about root cause until confirmed by investigation.\n\n## Output\n- Issue identified and categorized as platform-side or internal\n- Remediation applied with evidence of restored service\n- Stakeholders notified with timeline and impact summary\n- Evidence collected for postmortem including timeline and root cause\n\n## Error Handling\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Ferrors.md` for comprehensive error handling.\n\n## Examples\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fexamples.md` for detailed examples.\n\n## Resources\n- [Supabase Status Page](https:\u002F\u002Fstatus.supabase.com)\n- [Supabase Support](https:\u002F\u002Fsupport.supabase.com)\n\n## Overview\n\nExecute Supabase incident response procedures with triage, mitigation, and postmortem.","# Supabase Incident Runbook\n\n## Prerequisites\n- Access to Supabase dashboard and status page\n- kubectl access to production cluster\n- Prometheus\u002FGrafana access\n- Communication channels (Slack, PagerDuty)\n\n## Instructions\n\nIncident response for Supabase integrations requires distinguishing quickly between platform-side outages (check status.supabase.com) and issues in your own integration code or infrastructure. Misattributing a platform outage as an internal bug wastes critical time during an incident. Always verify the Supabase status page before investing engineering effort in local remediation.\n\n### Step 1: Quick Triage\nRun the triage commands to identify the issue source. Check Supabase status page, verify your API credentials have not expired, and run a minimal health check query against your Supabase instance. Compare error rates against your baseline metrics to understand the scope and onset time.\n\n### Step 2: Follow Decision Tree\nDetermine if the issue is Supabase-side or internal. Platform outages require monitoring the status page and communicating degraded service to users. Internal issues require examining your application logs, recent deployments, and configuration changes for the root cause.\n\n### Step 3: Execute Immediate Actions\nApply the appropriate remediation for the error type. For connection failures, enable circuit breakers and fallback responses. For data inconsistencies, pause write operations to prevent further corruption while you investigate.\n\n### Step 4: Communicate Status\nUpdate internal and external stakeholders. Provide clear, jargon-free status updates at regular intervals. Avoid speculation about root cause until confirmed by investigation.\n\n## Output\n- Issue identified and categorized as platform-side or internal\n- Remediation applied with evidence of restored service\n- Stakeholders notified with timeline and impact summary\n- Evidence collected for postmortem including timeline and root cause\n\n## Error Handling\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Ferrors.md` for comprehensive error handling.\n\n## Examples\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fexamples.md` for detailed examples.\n\n## Resources\n- [Supabase Status Page](https:\u002F\u002Fstatus.supabase.com)\n- [Supabase Support](https:\u002F\u002Fsupport.supabase.com)\n\n## Overview\n\nExecute Supabase incident response procedures with triage, mitigation, and postmortem.",{"name":5,"author":24,"license":15,"version":25,"description":26,"allowed-tools":27,"compatible-with":28},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute Supabase incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Supabase-related outages, investigating errors,\nor running post-incident reviews for Supabase integration failures.\nTrigger with phrases like \"supabase incident\", \"supabase outage\",\n\"supabase down\", \"supabase on-call\", \"supabase emergency\", \"supabase broken\".\n","Read, Grep, Bash(kubectl:*), Bash(curl:*)","claude-code, codex, openclaw","main","c2b1fdccc779e99ac814e55fb69ca8d71215dd0f","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection","https:\u002F\u002Fgithub.com\u002FSamuelChien","http:\u002F\u002Fsamuelchien.com\u002F","2026-05-26 08:27:14",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SamuelChien\u002Fmega-skills-collection --skill supabase-incident-runbook",{"tool":41,"command":42},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill supabase-incident-runbook",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill supabase-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fsupabase-incident-runbook\u002FSKILL.md",true,[49,55,59],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Ferrors.md","REFERENCE","参考文档",331,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fsupabase-incident-runbook\u002Freferences\u002Ferrors.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fexamples.md",142,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fsupabase-incident-runbook\u002Freferences\u002Fexamples.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fimmediate-actions-by-error-type.md",1008,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fsupabase-incident-runbook\u002Freferences\u002Fimmediate-actions-by-error-type.md",[64,71,78,85,92,100],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M76R4WZQZAXGGXMQCA0FZ716","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M76R4T9KENDH7FENGZQHBW4G","zustand-store-creator","Zustand Store Creator - Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M76R3YWN84B7SANJ52X799ZE","zero-trust-config-helper","Zero Trust Config Helper - Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M76R3HNSV2AEYSKHM915GJ58","zapier-integration-helper","Zapier Integration Helper - Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M76R3DJSKAT4FA7DV4BF3GCE","zai-cli","Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP.\nUse when user needs image\u002Fvideo analysis, OCR, UI-to-code conversion, error diagnosis,\nreal-time web search, web page to markdown extraction, or GitHub code exploration.\nTrigger with phrases like \"analyze this image\", \"search the web for\", \"read this page\",\n\"explore this repo\", or \"use zai\". Requires Z_AI_API_KEY.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzai-cli\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M76R2KAM699XE9AJVAWE4H2E","yt-research","Research competitor YouTube channels, niches, and trending topics for your content strategy.\nUse this skill whenever the user says \"research channels\", \"analyze competitors\", \"find trending topics\",\n\"niche analysis\", \"competitive research\", \"what are other creators doing\", \"scrape YouTube channels\",\nor wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fyt-research\u002FSKILL.md",[],[]]