[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76P1PASK0KGCREWTYTS5R6J":3,"skill-same:01M76P1PASK0KGCREWTYTS5R6J":71},{"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},"01M76P1PASK0KGCREWTYTS5R6J","supabase-reliability-patterns",null,"Implement Supabase reliability patterns including circuit breakers, idempotency, and graceful degradation.\nUse when building fault-tolerant Supabase integrations, implementing retry strategies,\nor adding resilience to production Supabase services.\nTrigger with phrases like \"supabase reliability\", \"supabase circuit breaker\",\n\"supabase idempotent\", \"supabase resilience\", \"supabase fallback\", \"supabase bulkhead\".","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-reliability-patterns\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: supabase-reliability-patterns\ndescription: |\n  Implement Supabase reliability patterns including circuit breakers, idempotency, and graceful degradation.\n  Use when building fault-tolerant Supabase integrations, implementing retry strategies,\n  or adding resilience to production Supabase services.\n  Trigger with phrases like \"supabase reliability\", \"supabase circuit breaker\",\n  \"supabase idempotent\", \"supabase resilience\", \"supabase fallback\", \"supabase bulkhead\".\nallowed-tools: Read, Write, Edit\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Supabase Reliability Patterns\n\n## Prerequisites\n- Understanding of circuit breaker pattern\n- opossum or similar library installed\n- Queue infrastructure for DLQ\n- Caching layer for fallbacks\n\n## Instructions\n\nProduction Supabase integrations must be designed to handle two failure scenarios gracefully: temporary degradation (connection timeouts, brief overloads) and complete unavailability (platform outage). Circuit breakers address the first by preventing retry storms from amplifying degraded conditions. Idempotency keys address the second by making operations safe to replay after a failure, ensuring that a network timeout does not result in duplicated writes when the request is retried.\n\n### Step 1: Implement Circuit Breaker\nWrap Supabase calls with a circuit breaker using a library like opossum. Configure the failure threshold (percentage of failures that trips the breaker), the reset timeout (how long to wait before testing recovery), and a fallback function that returns a cached or default response when the circuit is open. This prevents cascading failures from propagating to your entire application during Supabase degradation events.\n\n### Step 2: Add Idempotency Keys\nGenerate deterministic keys for write operations using a hash of the input parameters or a client-provided UUID. Store the idempotency key alongside the result so that duplicate requests return the original response rather than executing the operation again. This is especially important for payment or provisioning workflows where duplicate execution has financial or resource consequences.\n\n### Step 3: Configure Bulkheads\nSeparate queues for different operation priorities so that a surge in low-priority batch processing does not starve high-priority user-facing operations of Supabase connection capacity.\n\n### Step 4: Set Up Dead Letter Queue\nHandle permanent failures gracefully by routing operations that exceed the maximum retry count to a dead letter queue. Alert on DLQ depth and provide a replay mechanism so failed operations can be reprocessed after the underlying issue is resolved.\n\n## Output\n- Circuit breaker protecting Supabase calls with configured fallback behavior\n- Idempotency preventing duplicate writes on retry scenarios\n- Bulkhead isolation separating high and low-priority operation queues\n- Dead letter queue capturing and alerting on permanent failures\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- [Circuit Breaker Pattern](https:\u002F\u002Fmartinfowler.com\u002Fbliki\u002FCircuitBreaker.html)\n- [Opossum Documentation](https:\u002F\u002Fnodeshift.dev\u002Fopossum\u002F)\n- [Supabase Reliability Guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freliability)\n\n## Overview\n\nImplement Supabase reliability patterns including circuit breakers, idempotency, and graceful degradation.","# Supabase Reliability Patterns\n\n## Prerequisites\n- Understanding of circuit breaker pattern\n- opossum or similar library installed\n- Queue infrastructure for DLQ\n- Caching layer for fallbacks\n\n## Instructions\n\nProduction Supabase integrations must be designed to handle two failure scenarios gracefully: temporary degradation (connection timeouts, brief overloads) and complete unavailability (platform outage). Circuit breakers address the first by preventing retry storms from amplifying degraded conditions. Idempotency keys address the second by making operations safe to replay after a failure, ensuring that a network timeout does not result in duplicated writes when the request is retried.\n\n### Step 1: Implement Circuit Breaker\nWrap Supabase calls with a circuit breaker using a library like opossum. Configure the failure threshold (percentage of failures that trips the breaker), the reset timeout (how long to wait before testing recovery), and a fallback function that returns a cached or default response when the circuit is open. This prevents cascading failures from propagating to your entire application during Supabase degradation events.\n\n### Step 2: Add Idempotency Keys\nGenerate deterministic keys for write operations using a hash of the input parameters or a client-provided UUID. Store the idempotency key alongside the result so that duplicate requests return the original response rather than executing the operation again. This is especially important for payment or provisioning workflows where duplicate execution has financial or resource consequences.\n\n### Step 3: Configure Bulkheads\nSeparate queues for different operation priorities so that a surge in low-priority batch processing does not starve high-priority user-facing operations of Supabase connection capacity.\n\n### Step 4: Set Up Dead Letter Queue\nHandle permanent failures gracefully by routing operations that exceed the maximum retry count to a dead letter queue. Alert on DLQ depth and provide a replay mechanism so failed operations can be reprocessed after the underlying issue is resolved.\n\n## Output\n- Circuit breaker protecting Supabase calls with configured fallback behavior\n- Idempotency preventing duplicate writes on retry scenarios\n- Bulkhead isolation separating high and low-priority operation queues\n- Dead letter queue capturing and alerting on permanent failures\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- [Circuit Breaker Pattern](https:\u002F\u002Fmartinfowler.com\u002Fbliki\u002FCircuitBreaker.html)\n- [Opossum Documentation](https:\u002F\u002Fnodeshift.dev\u002Fopossum\u002F)\n- [Supabase Reliability Guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freliability)\n\n## Overview\n\nImplement Supabase reliability patterns including circuit breakers, idempotency, and graceful degradation.",{"name":5,"author":24,"license":15,"version":25,"description":26,"allowed-tools":27,"compatible-with":28},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Implement Supabase reliability patterns including circuit breakers, idempotency, and graceful degradation.\nUse when building fault-tolerant Supabase integrations, implementing retry strategies,\nor adding resilience to production Supabase services.\nTrigger with phrases like \"supabase reliability\", \"supabase circuit breaker\",\n\"supabase idempotent\", \"supabase resilience\", \"supabase fallback\", \"supabase bulkhead\".\n","Read, Write, Edit","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-reliability-patterns",{"tool":41,"command":42},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill supabase-reliability-patterns",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill supabase-reliability-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fsupabase-reliability-patterns\u002FSKILL.md",true,[49,55,59,63,67],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fcircuit-breaker.md","REFERENCE","参考文档",802,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fsupabase-reliability-patterns\u002Freferences\u002Fcircuit-breaker.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fdead-letter-queue.md",1028,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fsupabase-reliability-patterns\u002Freferences\u002Fdead-letter-queue.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Ferrors.md",340,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fsupabase-reliability-patterns\u002Freferences\u002Ferrors.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fexamples.md",139,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fsupabase-reliability-patterns\u002Freferences\u002Fexamples.md",{"path":68,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fidempotency-keys.md",880,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fsupabase-reliability-patterns\u002Freferences\u002Fidempotency-keys.md",[72,79,86,93,100,108],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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",[],[]]