Oncall
pigweed-project/pigweed
Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).
Analyze, contain, and recover Mistral credential, outage, throttling, data, spend, and state-reconciliation incidents.
Install Mistral Incident Runbook
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill mistral-incident-runbook -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace mistral-incident-runbook --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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/mistral-incident-runbook .claude/skills/mistral-incident-runbook && rm -rf skills-srcUse ~/.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/
Install the "mistral-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/mistral-incident-runbook into .claude/skills/mistral-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mistral-incident-runbook", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/mistral-incident-runbookType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill mistral-incident-runbook -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace mistral-incident-runbook --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/mistral-incident-runbook .agents/skills/mistral-incident-runbook && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mistral-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/mistral-incident-runbook into .agents/skills/mistral-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mistral-incident-runbook", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill mistral-incident-runbook -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace mistral-incident-runbook --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/mistral-incident-runbook .cursor/skills/mistral-incident-runbook && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mistral-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/mistral-incident-runbook into .cursor/skills/mistral-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mistral-incident-runbook", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/mistral-incident-runbook--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill mistral-incident-runbook -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace mistral-incident-runbook --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/mistral-incident-runbook .gemini/skills/mistral-incident-runbook && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mistral-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/mistral-incident-runbook into .gemini/skills/mistral-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mistral-incident-runbook", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace mistral-incident-runbookInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill mistral-incident-runbook -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/mistral-incident-runbook .github/skills/mistral-incident-runbook && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mistral-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/mistral-incident-runbook into .github/skills/mistral-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mistral-incident-runbook", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill mistral-incident-runbook -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace mistral-incident-runbook --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/mistral-incident-runbook .opencode/skills/mistral-incident-runbook && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mistral-incident-runbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/mistral-incident-runbook into .opencode/skills/mistral-incident-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mistral-incident-runbook", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
mistral-incident-runbook- GitHub stars
- 2.8k
- Token cost
- ~883 tokens
- SKILL.md length
- 346 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analyze, contain, and recover Mistral credential, outage, throttling, data, spend, and state-reconciliation incidents.
- Works in 6 steps: Declare scope, severity, commander, UTC… → Stop retry storms and risky work while… → Classify credential, provider, capacity,… → …
- Responding to provider-related impact
- SKILL.md covers Overview, Prerequisites, Current Contract and Authentication, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Mistral Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analyze, contain, and recover Mistral credential, outage, throttling, data, spend, and state-reconciliation incidents. Use when responding to provider-related impact. Trigger with "Mistral incident", "Mistral outage", or "rotate a leaked Mistral key".
Its SKILL.md is about 880 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 or external Mistral actions require network access and explicit approval
It sits in DevOps & Cloud, covering Incident response, Runbooks and postmortems and Accounting and bookkeeping. It works with Mistral AI. 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 provider-related impact
- With Mistral incident
- Rotate a leaked Mistral key
Example prompts
- “Mistral incident”
- “Mistral outage”
- “rotate a leaked Mistral key”
- “/mistral-incident-runbook”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code; live or external Mistral actions require network access and explicit approval
- Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Declare scope, severity, commander, UTC timeline, environments, and impact.
- Stop retry storms and risky work while preserving queue/idempotency evidence.
- Classify credential, provider, capacity, spend, data, model, deploy, or state failure.
- Choose bounded containment: disable, shed, pause, rollback, rotate, or isolate.
- Reconcile files, jobs, runs, conversations, and app actions before replay.
- Recover through synthetic canary, monitor convergence, communicate, and assign actions.
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:
ReadGlobGrepWriteEdit
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
No URLs in SKILL.md.
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 or external Mistral actions require network access and explicit approval
From compatibility in the SKILL.md frontmatter.
Context cost
Mistral Incident Runbook loads about 883 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 69 tokens; SKILL.md has 346 words of instructions outside code blocks.
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). 346 words, ~883 tokens.
Download SKILL.mdSave it as
.claude/skills/mistral-incident-runbook/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- mistral-incident-runbook
- description
- Analyze, contain, and recover Mistral credential, outage, throttling, data, spend, and state-reconciliation incidents. Use when responding to provider-related impact. Trigger with "Mistral incident", "Mistral outage", or "rotate a leaked Mistral key".
- allowed-tools
- Read, Glob, Grep, Write, Edit
- compatibility
- Designed for Claude Code; live or external Mistral actions require network access and explicit approval
- argument-hint
- <incident-id> <severity> <environment>
- version
- 1.14.0
- license
- MIT
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- tags
- saas, mistral, incident-response
- model
- inherit
- effort
- high
Mistral Incident Response
Overview
Restore safety before throughput. Classify, stop amplification, protect evidence, reconcile ambiguous work, and use the smallest reversible containment action.
Prerequisites
- An incident commander, severity policy, inventory, and current runbooks.
- Content-free telemetry, deployment controls, rotation, and admin/status evidence.
- Communication, evidence-retention, and post-incident owners.
Current Contract
Provider, account, app, and data incidents differ. Workspace caps can suspend access; Files, Batch, Conversations, Agents, and Workflows may outlive a failed request and need reconciliation.
Authentication
Never paste keys into incident channels. On exposure, revoke through approved admin, rotate consumers, and verify old-key denial without displaying values.
Instructions
- Declare scope, severity, commander, UTC timeline, environments, and impact.
- Stop retry storms and risky work while preserving queue/idempotency evidence.
- Classify credential, provider, capacity, spend, data, model, deploy, or state failure.
- Choose bounded containment: disable, shed, pause, rollback, rotate, or isolate.
- Reconcile files, jobs, runs, conversations, and app actions before replay.
- Recover through synthetic canary, monitor convergence, communicate, and assign actions.
Tool Discipline
Use Read, Glob, and Grep to inspect code, locks, configuration, tests, and evidence. Use Write and Edit only for approved repository changes. Invocation alone does not authorize network calls, paid usage, uploads, stateful resources, admin mutations, deployments, or deletion.
Approval Boundaries
The commander must approve revocation, traffic, queue or job changes, deletion, limits or spend changes, rollback, and customer communication. Record the approver and exact containment scope.
Error Handling
- Blind replay can duplicate paid/stateful work.
- Purging queues can destroy reconciliation evidence.
- Provider recovery does not prove app backlog convergence.
Output
Return scope and timeline, classification, containment approvals, affected state, reconciliation, recovery, residual risk, communications, and follow-ups. Keep unresolved ambiguity visible with a named owner.
Examples
- Disable batch submission while reconciling accepted jobs.
- Rotate an exposed key and prove old-key denial plus new-key canary.
Validation
Tabletop key exposure, 429, outage, cap reached, content leak, stuck stream, and ambiguous state; verify rollback/comms.
Resources
- Current first-party evidence map — recheck dated sources before relying on mutable endpoints, models, limits, prices, preview status, or retention.
- Record live account observations as environment-specific evidence, not universal Mistral guarantees.
© 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/mistral-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
Mistral 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Mistral Incident Runbook this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~883 | Automated safety check: Pass | MIT | |
| Oncallpigweed-project/pigweed | 548 | — | ~963 | Automated safety check: Pass | Apache-2.0 | |
| Activation Governance Chaos RolloutAli-Marandi/DataSense | 107 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Incident Response686f6c61/alfred-dev | 117 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Superset Incident Triagesuperset-sh/superset | 15k | — | ~1k | Automated safety check: Pass | Custom licence | |
| Post-Incident DebriefVeryGoodOpenSource/vgv-wingspan | 109 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Activation Governance Chaos Rollout
Ali-Marandi/DataSense
Design, validate, and govern fail-closed customer-activation automations that use an Outbox/worker pattern.
Incident Response
686f6c61/alfred-dev
Protocolo de respuesta ante incidentes en produccion: triaje, mitigacion, causa raiz y postmortem.
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.
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.
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.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming 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.
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.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
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.
Related
Works with
Categories
Questions about Mistral Incident Runbook
What does Mistral Incident Runbook do?
Analyze, contain, and recover Mistral credential, outage, throttling, data, spend, and state-reconciliation incidents. Mistral Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analyze, contain, and recover Mistral credential, outage, throttling, data, spend, and state-reconciliation incidents.
When should I use Mistral Incident Runbook?
Mistral Incident Runbook fits situations like: responding to provider-related impact; with Mistral incident; rotate a leaked Mistral key.
How do I install Mistral Incident Runbook in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill mistral-incident-runbook -a claude-code`. Or copy the skill folder (skills/.curated/mistral-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/mistral-incident-runbook in your project. Claude Code loads it when a task matches its description.
How do I install Mistral Incident Runbook in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill mistral-incident-runbook -a codex`. Or copy the skill folder (skills/.curated/mistral-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/mistral-incident-runbook in your project. Codex loads it when a task matches its description.
Can I use Mistral 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 mistral-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/mistral-incident-runbook, .gemini/skills/mistral-incident-runbook, .github/skills/mistral-incident-runbook and .opencode/skills/mistral-incident-runbook in your project.
What does Mistral Incident Runbook need to run?
SKILL.md names no scripts, command-line tools or credentials: Mistral Incident Runbook is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; live or external Mistral actions require network access and explicit approval.
Does Mistral Incident Runbook access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Mistral 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 Mistral Incident Runbook use?
Mistral 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 Mistral Incident Runbook use?
About 883 tokens (SKILL.md is roughly 3.5k 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 236 tokens, read only when the agent opens those files.
What are the alternatives to Mistral Incident Runbook?
Skills that share tags, products or a category with Mistral 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 Mistral 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.