Agent skill

mistral-incident-runbook

Execute Mistral AI incident response procedures with triage, mitigation, and postmortem. Use when responding to Mistral AI-related outages, investigating errors, or running post-incident reviews. Trigger with phrases like "mistral incident", "mistral outage", "mistral down", "mistral on-call", "mistral emergency". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-coderead-onlyMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill mistral-incident-runbook --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.12.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadGrepBash(kubectl:*)Bash(curl:*)
Requires: Designed for Claude Code, also compatible with Codex and OpenClaw
Path: plugins/saas-packs/mistral-pack/skills/mistral-incident-runbook/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Mistral AI Incident Runbook ## Overview Rapid incident response procedures for Mistral AI integration failures. Covers severity classification, quick triage script, decision tree, per-error mitigations, communication templates, and postmortem process. ## Severity Levels | Level | Definition | Response Time | Example | |-------|------------|---------------|---------| | P1 | Complete outage | < 15 min | All Mistral requests failing | | P2 | Degraded service | < 1 hour | High latency, partial 429s | | P3 | Minor impact | < 4 hours | Occasional errors, non-critical feature | | P4 | No user impact | Next business day | Monitoring gaps, docs | ## Quick Triage Script ```bash #!/bin/bash set -euo pipefail echo "=== Mistral AI Quick Triage ===" echo "Timestamp: $(date -u +%Y-%m-%dT%H:%M:%SZ)" # 1. API health echo -e "\n1. Mistral API status:" HTTP=$(curl -s -o /dev/null -w "%{http_code}" \ -H "Authorization: Bearer ${MISTRAL_API_KEY}" \ https://api.mistral.ai/v1/models 2>/dev/null) echo " HTTP: $HTTP" case $HTTP in 200) echo " OK — API is reachable" ;; 401) echo " AUTH FAILURE — API key invalid or revoked" ;; 429) echo " RATE LIMITED — check workspace limits" ;; 5*) echo " SERVER ERROR —

What's inside
Steps it walks through
  1. Overview
  2. Severity Levels
  3. Quick Triage Script
  4. Decision Tree
  5. Immediate Actions
  6. Step 1: 401 — Authentication Failure (P1)
  7. Step 2: 429 — Rate Limited (P2)
  8. Step 3: 5xx — Mistral Service Error (P1/P2)
  9. Step 4: Network/Timeout Error (P2)
  10. Communication Templates
  11. Internal (Slack)
  12. External (Status Page)
  13. Post-Incident
  14. Evidence Collection
Commands it runs
set -euo pipefail
echo "=== Mistral AI Quick Triage ==="
echo "Timestamp: $(date -u +%Y-%m-%dT%H:%M:%SZ)"
echo -e "\n1. Mistral API status:"
echo "   HTTP: $HTTP"
case $HTTP in
esac
echo -e "\n2. App health endpoint:"
curl -sf https://yourapp.com/health 2>/dev/null | jq '.services.mistral' || echo "   UNREACHABLE"
echo -e "\n3. Error rate (last 5m):"
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the mistral-incident-runbook skill do?

Execute Mistral AI incident response procedures with triage, mitigation, and postmortem. Use when responding to Mistral AI-related outages, investigating errors, or running post-incident reviews. Trigger with phrases like "mistral incident", "mistral outage", "mistral down", "mistral on-call", "mistral emergency". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill mistral-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,630 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.

Keep going