Agent skill

Miro Incident Runbook

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Plan and implement repository-side containment and recovery controls for Miro authorization, capacity, outage, and data-correctness incidents, with approval-gated live actions.

MITAuto-check passedDevOps & Cloud

Install Miro Incident Runbook

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill miro-incident-runbook -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace miro-incident-runbook --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/miro-incident-runbook .claude/skills/miro-incident-runbook && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
miro-incident-runbook
GitHub stars
2.8k
Token cost
~1.1k tokens
SKILL.md length
427 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Plan and implement repository-side containment and recovery controls for Miro authorization, capacity, outage, and data-correctness incidents, with approval-gated live actions.

  • Works in 6 steps: Declare incident scope, commander,… → Contain with write disablement, queue… → Correlate deployment changes, token… → …
  • Responding to a Miro service incident
  • SKILL.md covers Overview, Prerequisites, Tool Discipline and Current Contract, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Miro Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Plan and implement repository-side containment and recovery controls for Miro authorization, capacity, outage, and data-correctness incidents, with approval-gated live actions. Use when responding to a Miro service incident. Trigger with "Miro incident".

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; live work requires an authorized Miro app and redacted evidence

It sits in DevOps & Cloud, covering Incident response, Runbooks and postmortems and Authorization and RBAC. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Responding to a Miro service incident
  • With Miro incident

Example prompts

  • “Miro incident”
  • “/miro-incident-runbook”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code; live work requires an authorized Miro app and redacted evidence
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, Write, Edit

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Declare incident scope, commander, severity, start time, affected tenants/operations, and change freeze.
  2. Contain with write disablement, queue pause, concurrency reduction, or circuit opening appropriate to evidence.
  3. Correlate deployment changes, token events, rate headers, semantic drift, and official Miro status.
  4. Run the smallest read-only probe to classify auth, tenant, capacity, vendor, network, or local failure.
  5. Recover in a canary cohort; reconcile ambiguous operations before draining queues.
  6. Verify SLOs and data correctness, document timeline/root cause/follow-ups, and obtain closure approval.

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • WebFetch
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • status.miro.com
    • developers.miro.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code; live work requires an authorized Miro app and redacted evidence

    From compatibility in the SKILL.md frontmatter.

Context cost

Miro Incident Runbook loads about 1.1k tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 69 tokens; SKILL.md has 427 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~69
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 427 words, ~1,062 tokens.

Download SKILL.mdSave it as .claude/skills/miro-incident-runbook/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
miro-incident-runbook
description
Plan and implement repository-side containment and recovery controls for Miro authorization, capacity, outage, and data-correctness incidents, with approval-gated live actions. Use when responding to a Miro service incident. Trigger with "Miro incident".
allowed-tools
Read, Glob, Grep, WebFetch, Write, Edit
compatibility
Designed for Claude Code; live work requires an authorized Miro app and redacted evidence
argument-hint
[incident-id] [symptom]
version
1.9.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
saas, miro, incident-response, operations
model
inherit
effort
high

Miro Integration Incident Response

Overview

Stabilize user impact before changing authorization or replaying writes. Keep an UTC action log and make ambiguity explicit; use the evidence produced here to make the next decision explicit and reviewable.

Prerequisites

  • Incident commander, owners, severity, and affected window
  • Current deployment, app/team context, dashboards, and safe logs
  • Write-disable, circuit-breaker, reconciliation, and rollback controls

Tool Discipline

Use Read, Glob, and Grep to inspect the repository, configuration names, adapters, tests, and evidence. Use WebFetch only for current official Miro documentation. Use Write or Edit after confirming the requested mode, target environment, tenant, board, and approval boundary. These declared tools do not call authenticated Miro APIs or deployment CLIs; implement client, configuration, and test changes, then return exact operator commands or an approval-gated handoff for live execution.

Current Contract

  • 401, 403/404, 409, 429, network, and 5xx failures require different containment.
  • One refresh attempt is safe only when serialized against rotating token storage.
  • 429 recovery follows observed reset headers and shared credit demand.
  • Timeout/5xx on a mutation is ambiguous until target state is reconciled.

Authentication

For REST work, use OAuth 2.0 Authorization Code with the narrowest Miro scopes. Bind each encrypted token record to its user, application, authorized team, and granted scopes. Never print access tokens, refresh tokens, client secrets, authorization codes, or board content.

Show full SKILL.md (211 more words)Show less

Instructions

  1. Declare incident scope, commander, severity, start time, affected tenants/operations, and change freeze.
  2. Contain with write disablement, queue pause, concurrency reduction, or circuit opening appropriate to evidence.
  3. Correlate deployment changes, token events, rate headers, semantic drift, and official Miro status.
  4. Run the smallest read-only probe to classify auth, tenant, capacity, vendor, network, or local failure.
  5. Recover in a canary cohort; reconcile ambiguous operations before draining queues.
  6. Verify SLOs and data correctness, document timeline/root cause/follow-ups, and obtain closure approval.

Approval Boundaries

Credential rotation/revocation, scope or redirect changes, destructive repair, queue replay, and broad re-enable require the incident commander's explicit approval. Pause when the responsible owner or exact target is uncertain.

Output

Return severity, impact, timeline, evidence, containment, root cause/confidence, recovery metrics, reconciliation, approvals, and follow-ups. State what was not inspected or changed so the receipt cannot overclaim coverage.

Error Handling

ConditionResponse
Incident scope expandsReassess severity and containment before further recovery.
Mutation result is unknownReconcile; never blind-retry.
Shared refresh racesPause callers and serialize one rotation path.
Recovery canary regressesRecontain and restore the last verified state.

Examples

The example is a redacted operator receipt; identifiers are hashes or bounded labels, not board content or credentials.

text
incident=INC-311; class=rate-exhaustion; writes=paused; headroom=35%; ambiguous=4; reconciled=4/4; recovery=stable

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/miro-incident-runbook of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Miro Incident Runbook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Miro Incident Runbook compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Miro Incident Runbook this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.1kAutomated safety check: PassMIT
Oncallpigweed-project/pigweed548—~963Automated safety check: PassApache-2.0
Activation Governance Chaos RolloutAli-Marandi/DataSense107—~1.9kAutomated safety check: PassMIT
Incident Response686f6c61/alfred-dev117—~1.1kAutomated safety check: PassMIT
Superset Incident Triagesuperset-sh/superset15k—~1kAutomated safety check: PassCustom licence
Post-Incident DebriefVeryGoodOpenSource/vgv-wingspan109—~1.9kAutomated safety check: PassMIT

Similar skills

  • Oncall

    pigweed-project/pigweed

    Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).

    548 GitHub stars~963 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Design, validate, and govern fail-closed customer-activation automations that use an Outbox/worker pattern.

    107 GitHub stars~1.9k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Incident Response

    686f6c61/alfred-dev

    Protocolo de respuesta ante incidentes en produccion: triaje, mitigacion, causa raiz y postmortem.

    117 GitHub stars~1.1k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Superset Incident Triage

    superset-sh/superset

    Does a read-only first pass on a possible production incident: gathers deploy, Sentry and health-check signals, proposes a severity and status message, then stops for human approval.

    15k GitHub stars~1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Post-Incident Debrief

    VeryGoodOpenSource/vgv-wingspan

    Produces a blameless post-incident debrief with timeline, root cause and follow-up actions after an outage, failed release or significant bug, while details are fresh.

    109 GitHub stars~1.9k tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed
  • SRE Engineer

    Jeffallan/claude-skills

    Defines SLIs, SLOs and error budgets, and sets up golden-signal monitoring, blameless postmortems, toil automation and chaos experiments for production systems.

    12k GitHub stars~1.7k tokensUpdated 7 days ago
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Miro Incident Runbook

What does Miro Incident Runbook do?

Plan and implement repository-side containment and recovery controls for Miro authorization, capacity, outage, and data-correctness incidents, with approval-gated live actions. Miro Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Plan and implement repository-side containment and recovery controls for Miro authorization, capacity, outage, and data-correctness incidents, with approval-gated live actions.

When should I use Miro Incident Runbook?

Miro Incident Runbook fits situations like: responding to a Miro service incident; with Miro incident.

How do I install Miro Incident Runbook in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill miro-incident-runbook -a claude-code`. Or copy the skill folder (skills/.curated/miro-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/miro-incident-runbook in your project. Claude Code loads it when a task matches its description.

How do I install Miro Incident Runbook in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill miro-incident-runbook -a codex`. Or copy the skill folder (skills/.curated/miro-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/miro-incident-runbook in your project. Codex loads it when a task matches its description.

Can I use Miro Incident Runbook in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill miro-incident-runbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/miro-incident-runbook, .gemini/skills/miro-incident-runbook, .github/skills/miro-incident-runbook and .opencode/skills/miro-incident-runbook in your project.

What does Miro Incident Runbook need to run?

SKILL.md names no scripts, command-line tools or credentials: Miro Incident Runbook is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; live work requires an authorized Miro app and redacted evidence.

Does Miro Incident Runbook access the network?

SKILL.md names 2 domains. As links in the text: status.miro.com and developers.miro.com. This is read from the text; nothing was executed.

Is Miro Incident Runbook safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Miro Incident Runbook use?

Miro Incident Runbook is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Miro Incident Runbook use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 234 tokens, read only when the agent opens those files.

What are the alternatives to Miro Incident Runbook?

Skills that share tags, products or a category with Miro Incident Runbook: Oncall (pigweed-project/pigweed, 548 stars), Activation Governance Chaos Rollout (Ali-Marandi/DataSense, 107 stars), Incident Response (686f6c61/alfred-dev, 117 stars) and Superset Incident Triage (superset-sh/superset, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Miro Incident Runbook?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.