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".
Scanned 9/10/2026
Install to Claude Code
npx -y skills add micsapp/micstec-skills --skill vastai-debug-bundle --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Vastai Debug Bundle?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/micsapp-vastai-debug-bundle)More formats (shields.io, HTML) on the badges page.
---
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 <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
---
# 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
set -euo pipefail
# 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
set -euo pipefail
# 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`.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!