miro-incident-runbook
Execute Miro REST API v2 incident response with triage, mitigation, and postmortem. Use when responding to Miro-related outages, investigating API errors, or running post-incident reviews for Miro integration failures. Trigger with phrases like "miro incident", "miro outage", "miro down", "miro on-call", "miro emergency", "miro broken". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill miro-incident-runbook --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.
# Miro Incident Runbook ## Overview Rapid incident response for Miro REST API v2 integration failures: triage, mitigation, recovery, and postmortem. ## Severity Levels | Level | Definition | Response | Example | |-------|------------|----------|---------| | P1 | Complete integration outage | < 15 min | Miro API returns 5xx on all calls | | P2 | Degraded service | < 1 hour | High latency, partial 4
What does the miro-incident-runbook skill do?
Execute Miro REST API v2 incident response with triage, mitigation, and postmortem. Use when responding to Miro-related outages, investigating API errors, or running post-incident reviews for Miro integration failures. Trigger with phrases like "miro incident", "miro outage", "miro down", "miro on-call", "miro emergency", "miro broken". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill miro-incident-runbook --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.