Agent skill

Cohere Incident Runbook

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

Analyze and mitigate Cohere integration incidents with provider, model, capacity, data, and application evidence plus reversible actions.

MITAuto-check passedDevOps & Cloud

Install Cohere Incident Runbook

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

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace cohere-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/cohere-incident-runbook .claude/skills/cohere-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
cohere-incident-runbook
GitHub stars
2.8k
Token cost
~1.1k tokens
SKILL.md length
441 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Analyze and mitigate Cohere integration incidents with provider, model, capacity, data, and application evidence plus reversible actions.

  • Works in 6 steps: Open the incident record and capture… → Check provider status and compare… → Classify the failure and apply the… → …
  • Responding to an outage
  • SKILL.md covers Overview, Prerequisites, Tool Discipline and Current Contract, plus 7 more sections
  • Needs CO_API_KEY

What it does

Cohere Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analyze and mitigate Cohere integration incidents with provider, model, capacity, data, and application evidence plus reversible actions. Use when responding to an outage or serious degradation. Trigger with "Cohere incident", "Cohere outage", or "Cohere on-call".

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 verification requires network access and an approved Cohere API key

It sits in DevOps & Cloud, covering Incident response and Runbooks and postmortems. 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 an outage
  • Serious degradation
  • With Cohere incident

Example prompts

  • “Cohere incident”
  • “Cohere outage”
  • “Cohere on-call”
  • “/cohere-incident-runbook”

Requirements

  • A credential in CO_API_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code; live verification requires network access and an approved Cohere API key
  • 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. Open the incident record and capture start time, impact, environment, endpoint, model, release, and correlation IDs.
  2. Check provider status and compare control traffic, regions, models, and recent local changes.
  3. Classify the failure and apply the smallest reversible mitigation within the incident authority matrix.
  4. Protect data and side effects while monitoring recovery against explicit thresholds.
  5. Escalate to Cohere with the redacted debug bundle when provider assistance is required.
  6. After recovery, verify normal quality and capacity, document timeline and cause, and assign preventive work.

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.cohere.com
    • docs.cohere.com

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

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • CO_API_KEY

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

  • Compatibility

    Designed for Claude Code; live verification requires network access and an approved Cohere API key

    From compatibility in the SKILL.md frontmatter.

Context cost

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

Always · name and description, kept in context so the agent knows when to use it
~72
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.9k

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). 441 words, ~1,104 tokens.

Download SKILL.mdSave it as .claude/skills/cohere-incident-runbook/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
cohere-incident-runbook
description
Analyze and mitigate Cohere integration incidents with provider, model, capacity, data, and application evidence plus reversible actions. Use when responding to an outage or serious degradation. Trigger with "Cohere incident", "Cohere outage", or "Cohere on-call".
allowed-tools
Read, Glob, Grep, WebFetch, Write, Edit
compatibility
Designed for Claude Code; live verification requires network access and an approved Cohere API key
argument-hint
[incident-id] [severity]
version
1.6.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
saas, cohere, incident-response
model
inherit
effort
high

Cohere Incident Runbook

Overview

Restore a safe user experience first, preserve evidence, and distinguish provider incidents from local regressions before making changes.

Prerequisites

  • The target repository, runtime, environment, and accountable owner
  • An approved Cohere team and key for any live verification
  • Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

  • Check Cohere's status page, but treat service-specific evidence as authoritative for your workload.
  • Separate authentication, billing, throttling, model retirement, provider 5xx, retrieval, and application failures.
  • Use only pre-approved degradation paths such as queueing, cached answers, read-only mode, or an evaluated model route.
  • Never debug by dumping keys, prompts, documents, or unrestricted environment variables.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

  1. Open the incident record and capture start time, impact, environment, endpoint, model, release, and correlation IDs.
  2. Check provider status and compare control traffic, regions, models, and recent local changes.
  3. Classify the failure and apply the smallest reversible mitigation within the incident authority matrix.
  4. Protect data and side effects while monitoring recovery against explicit thresholds.
  5. Escalate to Cohere with the redacted debug bundle when provider assistance is required.
  6. After recovery, verify normal quality and capacity, document timeline and cause, and assign preventive work.
Show full SKILL.md (157 more words)Show less

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embeddings, customer identifiers, and unrestricted environment output.

Error Handling

ConditionResponse
Unknown causePrefer traffic reduction or safe degradation over speculative code changes.
Credential suspectedRotate through the security incident process.
Model retiredUse only a pre-evaluated replacement or hold affected traffic.
Recovery unstableKeep the incident open and extend observation.

Examples

Use this compact handoff shape to keep the selected scope, validation evidence, and operational result reviewable.

Input:

text
incident=INC-77; symptom=429-spike; release=unchanged; status=investigating

Expected handoff:

text
class=capacity; mitigation=queue-cap; impact=stable; evidence=preserved

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/cohere-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

Cohere 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.

Cohere Incident Runbook compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cohere 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 8 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 Cohere Incident Runbook

What does Cohere Incident Runbook do?

Analyze and mitigate Cohere integration incidents with provider, model, capacity, data, and application evidence plus reversible actions. Cohere Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analyze and mitigate Cohere integration incidents with provider, model, capacity, data, and application evidence plus reversible actions.

When should I use Cohere Incident Runbook?

Cohere Incident Runbook fits situations like: responding to an outage; serious degradation; with Cohere incident.

How do I install Cohere Incident Runbook in Claude Code?

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

How do I install Cohere Incident Runbook in Codex?

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

Can I use Cohere 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 cohere-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/cohere-incident-runbook, .gemini/skills/cohere-incident-runbook, .github/skills/cohere-incident-runbook and .opencode/skills/cohere-incident-runbook in your project.

What does Cohere Incident Runbook need to run?

Going by SKILL.md and its folder, Cohere Incident Runbook needs credentials named CO_API_KEY. Our summary lists: A credential in CO_API_KEY. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; live verification requires network access and an approved Cohere API key.

Does Cohere Incident Runbook access the network?

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

Is Cohere 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 Cohere Incident Runbook use?

Cohere 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 Cohere Incident Runbook use?

About 1.1k tokens (SKILL.md is roughly 4.4k 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 820 tokens, read only when the agent opens those files.

What are the alternatives to Cohere Incident Runbook?

Skills that share tags, products or a category with Cohere 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 Cohere 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.