一键导入
provider-resilience
Defensive patterns for GitHub (gh) and Azure DevOps (az) CLI interactions — error handling, idempotency, rate limits, missing resources.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Defensive patterns for GitHub (gh) and Azure DevOps (az) CLI interactions — error handling, idempotency, rate limits, missing resources.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Compressed-prose response style for the orchestrator (opt-in via behavior.caveman_mode). Drops articles, fillers, and transitional prose; preserves code, paths, JSON/TOML, and quoted text verbatim.
Maestro project patterns — Rust CLI with ratatui TUI, tokio async, Claude CLI process management, and stream-json parsing.
TEMPLATE - Backend API development patterns. Copy and customize for your backend framework (Express, Django, Spring Boot, FastAPI, etc.)
TEMPLATE - Frontend web development patterns. Copy and customize for your frontend framework (React, Vue, Angular, Svelte, etc.)
API contract validation patterns for ensuring client-side models match backend JSON responses. Prevents decoding failures from schema mismatches. Tech-stack agnostic.
TEMPLATE - Mobile development patterns. Copy and customize for your mobile framework (React Native, Flutter, Swift, Kotlin, etc.)
| name | provider-resilience |
| version | 1.0.0 |
| description | Defensive patterns for GitHub (gh) and Azure DevOps (az) CLI interactions — error handling, idempotency, rate limits, missing resources. |
| allowed-tools | Read, Grep, Glob, WebSearch |
Knowledge base for robust
ghandazCLI interactions. Consulted bysubagent-architectandsubagent-qawhen designing features that touch GitHub or Azure DevOps APIs.
gh or az| Topic | File |
|---|---|
| Error taxonomy and recovery | errors.md |
| Idempotency patterns | idempotency.md |
GitHub CLI (gh) patterns | github-cli.md |
Azure DevOps CLI (az) patterns | azure-devops-cli.md |
| Rate limiting and batching | rate-limits.md |
Never assume remote state. Always verify-then-act or act-then-recover. Maestro runs on user machines against repos we don't control — labels, milestones, permissions, and API limits vary per project.