canva-reliability-patterns
Implement reliability patterns for Canva Connect API \u2014 circuit\ \ breakers, idempotency, graceful degradation.\nUse when building fault-tolerant\ \ Canva integrations, implementing retry strategies,\nor adding resilience to production\ \ Canva services.\nTrigger with phrases like \"canva reliability\", \"canva circuit\ \ breaker\",\n\"canva resilience\", \"canva fallback\", \"canva fault tolerance\"\ .\n"
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill canva-reliability-patterns --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Canva Reliability Patterns ## Overview Production-grade reliability patterns for the Canva Connect API. The API has async operations (exports, uploads, autofills) that can fail or timeout, OAuth tokens that expire every 4 hours, and rate limits that require backoff. ## Circuit Breaker ```typescript import CircuitBreaker from 'opossum'; const canvaBreaker = new CircuitBreaker( async (fn: () => Pr
What does the canva-reliability-patterns skill do?
Implement reliability patterns for Canva Connect API \u2014 circuit\ \ breakers, idempotency, graceful degradation.\nUse when building fault-tolerant\ \ Canva integrations, implementing retry strategies,\nor adding resilience to production\ \ Canva services.\nTrigger with phrases like \"canva reliability\", \"canva circuit\ \ breaker\",\n\"canva resilience\", \"canva fallback\", \"canva fault tolerance\"\ .\n"
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill canva-reliability-patterns --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
