exa-incident-runbook
Execute Exa incident response with triage, mitigation, and postmortem procedures. Use when responding to Exa-related outages, investigating errors, or running post-incident reviews for Exa integration failures. Trigger with phrases like "exa incident", "exa outage", "exa down", "exa on-call", "exa emergency", "exa broken". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill exa-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.
# Exa Incident Runbook ## Overview Rapid incident response procedures for Exa search API issues. Exa errors include a `requestId` field for support escalation. Default rate limit is 10 QPS. Contact hello@exa.ai for urgent production issues. ## Severity Levels | Level | Definition | Response Time | Example | |-------|------------|---------------|---------| | P1 | All Exa calls failing | < 15 min | 401/500 on every request | | P2 | Degraded performance | < 1 hour | High latency, partial failures | | P3 | Minor impact | < 4 hours | Empty results, content fetch failures | | P4 | No user impact | Next business day | Monitoring gaps | ## Quick Triage (Run First) ```bash set -euo pipefail echo "=== Exa Triage ===" # 1. Test API connectivity echo -n "API Status: " HTTP_CODE=$(curl -s -o /tmp/exa-triage.json -w "%{http_code}" \ -X POST https://api.exa.ai/search \ -H "x-api-key: $EXA_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query":"triage test","numResults":1}') echo "$HTTP_CODE" # 2. Show error details if not 200 if [ "$HTTP_CODE" != "200" ]; then echo "Error response:" cat /tmp/exa-triage.json | python3 -m json.tool 2>/dev/null || cat /tmp/exa-triage.json fi # 3. Check if it'
- Overview
- Severity Levels
- Quick Triage (Run First)
- Decision Tree
- Immediate Actions by Error Code
- 401/403 — Authentication
- 429 — Rate Limited
- 5xx — Exa Server Errors
- Communication Templates
- Internal (Slack)
- Support Escalation
- Post-Incident
- Evidence Collection
- Postmortem Template
set -euo pipefail
echo "=== Exa Triage ==="
echo -n "API Status: "
echo "$HTTP_CODE"
if [ "$HTTP_CODE" != "200" ]; then
echo "Error response:"
cat /tmp/exa-triage.json | python3 -m json.tool 2>/dev/null || cat /tmp/exa-triage.json
fi
echo ""
echo "API Key: ${EXA_API_KEY:+SET (${#EXA_API_KEY} chars)}"What does the exa-incident-runbook skill do?
Execute Exa incident response with triage, mitigation, and postmortem procedures. Use when responding to Exa-related outages, investigating errors, or running post-incident reviews for Exa integration failures. Trigger with phrases like "exa incident", "exa outage", "exa down", "exa on-call", "exa emergency", "exa broken". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill exa-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.