error-recovery
Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure.
- License 许可
- MIT
- 最近更新
- 2026-06-24
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- error-recovery
- tags
- [ "domain/orchestration", "artifact/workflow", "source/core-squad" ]
- domain
- reliability, agent-coordination
- license
- MIT
- confidence
- high
- description
- Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure.
03 SKILL.md 正文
Error Recovery Patterns
Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure.
1. Retry with Backoff
When: Transient failures — API timeouts, rate limits, network errors, temporary service unavailability.
Pattern:
- Wait briefly, then retry (start at 2s, double each attempt)
- Maximum 3 retries before escalating
- Log each attempt with the error received
Example: API call returns 429 Too Many Requests → wait 2s → retry → wait 4s → retry → wait 8s → retry → escalate if still failing.
2. Fallback Alternatives
When: Primary tool or approach fails and an alternative exists.
Pattern:
- Attempt primary approach
- On failure, identify alternative tool/method
- Try the alternative with the same intent
- Document which alternative was used and why
Example: Primary CLI tool fails → fall back to direct API call for the same operation.
3. Diagnose-and-Fix
When: Build failures, test failures, linting errors — structured errors with actionable output.
Pattern:
- Read the full error output carefully
- Identify the root cause from error messages
- Attempt a targeted fix
- Re-run to verify the fix
- Maximum 3 fix-retry cycles before escalating
Example: Build fails with a type error → check for missing import → add it → rebuild.
4. Escalate with Context
When: Recovery attempts have been exhausted, or the failure requires human judgment.
Pattern:
- Summarize what was attempted and what failed
- Include the exact error messages
- State what you believe the root cause is
- Suggest next steps or who might be able to help
- Hand off to the coordinator or the appropriate specialist
Example: After 3 failed build attempts → "Build fails on line 42 with null reference. Tried X, Y, Z. Likely a design issue in the Foo module. Recommend the code owner review."
5. Graceful Degradation
When: A non-critical step fails but the overall task can still deliver value.
Pattern:
- Determine if the failed step is critical to the task outcome
- If non-critical, log the failure and continue
- Deliver partial results with a clear note of what was skipped
- Offer to retry the skipped step separately
Example: Generating a report with 5 sections — section 3 data source is unavailable → produce the report with 4 sections, note that section 3 was skipped and why.
Applying These Patterns
Each agent should reference these patterns in their charter's ## Error Recovery section, tailored to their domain. The charter should list the agent's most common failure modes and map each to the appropriate pattern above.
Selection guide:
| Failure Type | Primary Pattern | Fallback Pattern |
|---|---|---|
| Network/API transient | Retry with Backoff | Escalate with Context |
| Tool/dependency missing | Fallback Alternatives | Escalate with Context |
| Build/test error | Diagnose-and-Fix | Escalate with Context |
| Auth/permissions | Retry with Backoff | Escalate with Context |
| Non-critical data missing | Graceful Degradation | — |
| Unknown/novel error | Escalate with Context | — |
? Связи
- [[MOC - Orchestration]] — Orchestration hub
- [[orchestration/squad]] — Squad
- [[000 - Map of Maps]] — Map of Maps
04 同仓库更多 Skills
ckm:ui-styling
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.
ckm:design
Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.
ckm:design-system
Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.
ckm:banner-design
Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.
seo
Comprehensive SEO analysis for any website or business type. Performs full site audits, single-page deep analysis, technical SEO checks (crawlability, indexability, Core Web Vitals with INP), schema markup detection/validation/generation, content quality assessment (E-E-A-T framework per Dec 2025 update extending to all competitive queries), image optimization, sitemap analysis, and Generative Engine Optimization (GEO) for AI Overviews, ChatGPT, and Perplexity citations. Analyzes AI crawler accessibility (GPTBot, ClaudeBot, PerplexityBot), llms.txt compliance, brand mention signals, and passage-level citability. Industry detection for SaaS, e-commerce, local business, publishers, agencies. Triggers on: "SEO", "audit", "schema", "Core Web Vitals", "sitemap", "E-E-A-T", "AI Overviews", "GEO", "technical SEO", "content quality", "page speed", "structured data".
seo-technical
Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", or "security headers".