home / skills / jeremylongshore / claude-code-plugins-plus-skills / vastai-debug-bundle

This skill helps you assemble comprehensive Vast.ai debug bundles and diagnostics for support tickets and troubleshooting.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill vastai-debug-bundle

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.2 KB
---
name: vastai-debug-bundle
description: |
  Collect Vast.ai debug evidence for support tickets and troubleshooting.
  Use when encountering persistent issues, preparing support tickets,
  or collecting diagnostic information for Vast.ai problems.
  Trigger with phrases like "vastai debug", "vastai support bundle",
  "collect vastai logs", "vastai diagnostic".
allowed-tools: Read, Bash(grep:*), Bash(curl:*), Bash(tar:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---

# Vast.ai Debug Bundle

## Overview
Collect all necessary diagnostic information for Vast.ai support tickets.

## Prerequisites
- Vast.ai SDK installed
- Access to application logs
- Permission to collect environment info

## Instructions

### Step 1: Create Debug Bundle Script
```bash
#!/bin/bash
# vastai-debug-bundle.sh

BUNDLE_DIR="vastai-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE_DIR"

echo "=== Vast.ai Debug Bundle ===" > "$BUNDLE_DIR/summary.txt"
echo "Generated: $(date)" >> "$BUNDLE_DIR/summary.txt"
```

### Step 2: Collect Environment Info
```bash
# Environment info
echo "--- Environment ---" >> "$BUNDLE_DIR/summary.txt"
node --version >> "$BUNDLE_DIR/summary.txt" 2>&1
npm --version >> "$BUNDLE_DIR/summary.txt" 2>&1
echo "VASTAI_API_KEY: ${VASTAI_API_KEY:+[SET]}" >> "$BUNDLE_DIR/summary.txt"
```

### Step 3: Gather SDK and Logs
```bash
# SDK version
npm list @vastai/sdk 2>/dev/null >> "$BUNDLE_DIR/summary.txt"

# Recent logs (redacted)
grep -i "vastai" ~/.npm/_logs/*.log 2>/dev/null | tail -50 >> "$BUNDLE_DIR/logs.txt"

# Configuration (redacted - secrets masked)
echo "--- Config (redacted) ---" >> "$BUNDLE_DIR/summary.txt"
cat .env 2>/dev/null | sed 's/=.*/=***REDACTED***/' >> "$BUNDLE_DIR/config-redacted.txt"

# Network connectivity test
echo "--- Network Test ---" >> "$BUNDLE_DIR/summary.txt"
echo -n "API Health: " >> "$BUNDLE_DIR/summary.txt"
curl -s -o /dev/null -w "%{http_code}" https://api.vastai.com/health >> "$BUNDLE_DIR/summary.txt"
echo "" >> "$BUNDLE_DIR/summary.txt"
```

### Step 4: Package Bundle
```bash
tar -czf "$BUNDLE_DIR.tar.gz" "$BUNDLE_DIR"
echo "Bundle created: $BUNDLE_DIR.tar.gz"
```

## Output
- `vastai-debug-YYYYMMDD-HHMMSS.tar.gz` archive containing:
  - `summary.txt` - Environment and SDK info
  - `logs.txt` - Recent redacted logs
  - `config-redacted.txt` - Configuration (secrets removed)

## Error Handling
| Item | Purpose | Included |
|------|---------|----------|
| Environment versions | Compatibility check | ✓ |
| SDK version | Version-specific bugs | ✓ |
| Error logs (redacted) | Root cause analysis | ✓ |
| Config (redacted) | Configuration issues | ✓ |
| Network test | Connectivity issues | ✓ |

## Examples

### Sensitive Data Handling
**ALWAYS REDACT:**
- API keys and tokens
- Passwords and secrets
- PII (emails, names, IDs)

**Safe to Include:**
- Error messages
- Stack traces (redacted)
- SDK/runtime versions

### Submit to Support
1. Create bundle: `bash vastai-debug-bundle.sh`
2. Review for sensitive data
3. Upload to Vast.ai support portal

## Resources
- [Vast.ai Support](https://docs.vastai.com/support)
- [Vast.ai Status](https://status.vastai.com)

## Next Steps
For rate limit issues, see `vastai-rate-limits`.

Overview

This skill collects a complete, redacted diagnostic bundle for Vast.ai support and troubleshooting. It automates environment checks, SDK and log collection, configuration redaction, and a basic network health test, then packages everything into a timestamped archive for upload to support.

How this skill works

The skill runs a small script that creates a timestamped bundle directory, captures environment and SDK versions, extracts recent logs while redacting secrets, reads and masks configuration files, performs an API health check, and compresses the results into a .tar.gz archive. The output archive contains summary, logs, and redacted config files suitable for sharing with Vast.ai support.

When to use it

  • When encountering persistent or reproducible errors with Vast.ai that require support assistance
  • Before opening a support ticket to provide complete diagnostic context
  • When you need to collect environment, SDK, and recent logs for debugging
  • After noticing connectivity or API health issues with Vast.ai services

Best practices

  • Always verify the redacted files to ensure API keys, tokens, passwords, and PII are removed
  • Run the bundle script from the project root so logs and .env files are captured
  • Limit log tails to recent entries to avoid oversharing unrelated data
  • Include the generated archive and a concise reproduction steps in the support ticket
  • Store the bundle locally or in a secure location and upload only to official support channels

Example use cases

  • Collect diagnostics after repeated job submission failures to show SDK and environment versions
  • Gather logs and network test results when API calls intermittently return errors or timeouts
  • Prepare a sanitized debug bundle to attach to a support ticket for faster triage
  • Capture redacted configuration and recent logs after an unexpected runtime crash
  • Validate environment compatibility before escalating a suspected version-specific bug

FAQ

What does the archive include?

The archive contains a summary with environment and SDK info, a recent redacted logs file, and a redacted configuration file.

How are secrets handled?

Secrets are masked by replacing values in .env and other configs with placeholders; you should review output before sharing.