Agent skill

vastai-incident-runbook

Execute Vast.ai incident response for GPU instance failures and outages. Use when responding to instance failures, investigating training crashes, or handling spot preemption emergencies. Trigger with phrases like "vastai incident", "vastai outage", "vastai down", "vastai emergency", "vastai instance failed". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-coderead-onlyMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill vastai-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: 6 KB
Bundled scripts: none
Version: 1.11.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadGrepBash(vastai:*)Bash(curl:*)Bash(ssh:*)
Requires: Designed for Claude Code, also compatible with Codex and OpenClaw
Path: skills/.curated/vastai-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

# Vast.ai Incident Runbook ## Overview Rapid incident response procedures for Vast.ai GPU instance failures. Covers triage, mitigation, recovery, and postmortem for common incident types: spot preemption, instance crashes, GPU failures, and billing issues. ## Prerequisites - Vast.ai CLI access - SSH access to instances (if still running) - Checkpoint storage accessible (S3/GCS) ## Instructions ### Triage: Assess Impact (< 2 minutes) ```bash #!/bin/bash set -euo pipefail echo "=== INCIDENT TRIAGE ===" echo "Time: $(date -u)" # 1. Check all instances echo -e "\n--- Instance Status ---" vastai show instances --raw | python3 -c " import sys, json for inst in json.load(sys.stdin): status = inst.get('actual_status', '?') flag = 'ALERT' if status in ('error', 'exited', 'offline') else 'OK' print(f' [{flag}] ID:{inst[\"id\"]} Status:{status} ' f'GPU:{inst.get(\"gpu_name\",\"?\")} \${inst.get(\"dph_total\",0):.3f}/hr') " # 2. Check if affected instance has recent logs echo -e "\n--- Recent Logs (last 20 lines) ---" vastai logs ${INSTANCE_ID:-0} --tail 20 2>/dev/null || echo "No logs available" # 3. Check account balance echo -e "\n--- Account ---" vastai show user --raw | python3 -c "import

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Instructions
  4. Triage: Assess Impact (< 2 minutes)
  5. Incident Type 1: Spot Preemption
  6. Incident Type 2: Training Job Crash
  7. Incident Type 3: GPU Hardware Failure
  8. Incident Type 4: Billing Emergency
  9. Postmortem Template
  10. Output
  11. Error Handling
  12. Resources
  13. Next Steps
  14. Examples
Commands it runs
set -euo pipefail
echo "=== INCIDENT TRIAGE ==="
echo "Time: $(date -u)"
echo -e "\n--- Instance Status ---"
vastai show instances --raw | python3 -c "
import sys, json
for inst in json.load(sys.stdin):
status = inst.get('actual_status', '?')
flag = 'ALERT' if status in ('error', 'exited', 'offline') else 'OK'
echo -e "\n--- Recent Logs (last 20 lines) ---"
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the vastai-incident-runbook skill do?

Execute Vast.ai incident response for GPU instance failures and outages. Use when responding to instance failures, investigating training crashes, or handling spot preemption emergencies. Trigger with phrases like "vastai incident", "vastai outage", "vastai down", "vastai emergency", "vastai instance failed". '

How do I install it?

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