[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AC3GV40JQJKFTWZDTQCWXM":3,"skill-same:01M7AC3GV40JQJKFTWZDTQCWXM":103},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":14,"repositoryHtmlUrl":69,"repositoryHomepageUrl":6,"ownerHtmlUrl":70,"ownerBlogUrl":6,"ownerDescription":71,"updatedAt":72,"install":73,"resources":86},"01M7AC3GV40JQJKFTWZDTQCWXM","validating-backup-integrity-for-recovery",null,"Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: validating-backup-integrity-for-recovery\ndescription: Validates backup integrity through cryptographic hash verification,\n  automated restore testing, corruption detection, and recoverability checks to\n  confirm backups are reliable for disaster recovery and ransomware response. Use\n  before relying on backups for recovery, when building post-backup validation\n  pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped\n  backups for silent corruption or tampering.\ndomain: cybersecurity\nsubdomain: incident-response\ntags:\n- incident-response\n- backup\n- integrity\n- hash-verification\n- restore-testing\n- disaster-recovery\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- RS.MA-01\n- RS.MA-02\n- RS.AN-03\n- RC.RP-01\nmitre_attack:\n- T1486\n- T1490\n- T1070\n- T1078\n- T1489\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - positioning\n  - monetization\n  techniques:\n  - id: T1531\n    name: Account Access Removal\n    tactic: positioning\n    source: attack\n  - id: F1018\n    name: Convert to Cryptocurrency\n    tactic: monetization\n    source: f3\n  - id: F1047\n    name: Transfer of funds\n    tactic: monetization\n    source: f3\n  - id: F1017.001\n    name: 'Conversion to Physical Monetary Instruments: Cash'\n    tactic: monetization\n    source: f3\n---\n# Validating Backup Integrity for Recovery\n\n## When to Use\n\nUse this skill when:\n- Verifying backup integrity before relying on backups for ransomware recovery\n- Building automated backup validation pipelines that run after each backup job\n- Auditing backup infrastructure to confirm recoverability for compliance (SOC 2, ISO 27001, NIST CSF RC.RP-03)\n- Detecting silent data corruption (bit rot) in backup storage before a disaster occurs\n- Validating that immutable or air-gapped backups have not been tampered with\n\n**Do not use** for initial backup configuration or scheduling. This skill focuses on post-backup validation.\n\n## Prerequisites\n\n- Access to backup storage (local, NAS, S3, Azure Blob, GCS)\n- Python 3.9+ with `hashlib` (standard library)\n- Backup manifests or baseline hash files for comparison\n- Isolated restore environment for restore testing\n- Backup tool CLI access (restic, borgbackup, rclone, or vendor-specific)\n\n## Workflow\n\n### Step 1: Generate Baseline Hash Manifest\n\nCreate a cryptographic fingerprint of every file at backup time:\n\n```bash\n# Generate SHA-256 manifest for a directory\nfind \u002Fdata\u002Fproduction -type f -exec sha256sum {} \\; > \u002Fmanifests\u002Fprod_baseline_$(date +%Y%m%d).sha256\n\n# Verify manifest format\nhead -5 \u002Fmanifests\u002Fprod_baseline_20260319.sha256\n# e3b0c44298fc1c149afbf4c8996fb924...  \u002Fdata\u002Fproduction\u002Fconfig.yaml\n# a7ffc6f8bf1ed76651c14756a061d662...  \u002Fdata\u002Fproduction\u002Fdatabase.sql\n```\n\n### Step 2: Verify Backup Archive Integrity\n\nCheck that the backup archive itself is not corrupted:\n\n```bash\n# Restic: verify backup repository integrity\nrestic -r s3:s3.amazonaws.com\u002Fbackup-bucket check --read-data\n\n# Borg: verify backup archive\nborg check --verify-data \u002Fbackup\u002Frepo::archive-2026-03-19\n\n# Tar with gzip: verify archive integrity\ngzip -t backup_20260319.tar.gz && echo \"Archive OK\" || echo \"Archive CORRUPTED\"\n\n# AWS S3: verify object checksums\naws s3api head-object --bucket backup-bucket --key daily\u002F2026-03-19.tar.gz \\\n  --checksum-mode ENABLED\n```\n\n### Step 3: Perform Restore Test to Isolated Environment\n\n```bash\n# Restore to isolated test directory\nrestic -r s3:s3.amazonaws.com\u002Fbackup-bucket restore latest --target \u002Frestore-test\u002F\n\n# Generate hash manifest of restored data\nfind \u002Frestore-test -type f -exec sha256sum {} \\; > \u002Fmanifests\u002Frestored_$(date +%Y%m%d).sha256\n\n# Compare baseline and restored manifests\ndiff \u003C(sort \u002Fmanifests\u002Fprod_baseline_20260319.sha256) \\\n     \u003C(sort \u002Fmanifests\u002Frestored_20260319.sha256)\n```\n\n### Step 4: Validate Data Completeness\n\n```bash\n# Count files in original vs restored\necho \"Original: $(find \u002Fdata\u002Fproduction -type f | wc -l) files\"\necho \"Restored: $(find \u002Frestore-test -type f | wc -l) files\"\n\n# Check total size\necho \"Original: $(du -sh \u002Fdata\u002Fproduction | cut -f1)\"\necho \"Restored: $(du -sh \u002Frestore-test | cut -f1)\"\n\n# Database consistency check after restore\npg_restore --list backup.dump | wc -l  # Count objects in dump\npsql -c \"SELECT schemaname, tablename FROM pg_tables WHERE schemaname='public';\" restored_db\n```\n\n### Step 5: Detect Ransomware Artifacts in Backups\n\nBefore trusting a backup for recovery, scan for ransomware indicators:\n\n```bash\n# Check for common ransomware file extensions\nfind \u002Frestore-test -type f \\( \\\n  -name \"*.encrypted\" -o -name \"*.locked\" -o -name \"*.crypt\" \\\n  -o -name \"*.ransom\" -o -name \"*.pay\" -o -name \"*.wncry\" \\\n  -o -name \"*.cerber\" -o -name \"*.locky\" -o -name \"*.zepto\" \\\n\\) -print\n\n# Check for ransom notes\nfind \u002Frestore-test -type f \\( \\\n  -name \"README_TO_DECRYPT*\" -o -name \"HOW_TO_RECOVER*\" \\\n  -o -name \"DECRYPT_INSTRUCTIONS*\" -o -name \"HELP_DECRYPT*\" \\\n\\) -print\n\n# Check file entropy (high entropy = possible encryption)\n# Files with entropy > 7.9 out of 8.0 are likely encrypted\npython agent.py --entropy-scan \u002Frestore-test\n```\n\n### Step 6: Automate and Schedule Validation\n\n```yaml\n# cron-based validation schedule\n# Run nightly after backup window\n0 4 * * * \u002Fopt\u002Fbackup-validator\u002Fagent.py --validate-latest --notify-on-failure\n# Weekly full restore test\n0 6 * * 0 \u002Fopt\u002Fbackup-validator\u002Fagent.py --full-restore-test --config \u002Fetc\u002Fbackup-validator\u002Fconfig.json\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Hash Manifest** | File containing cryptographic hashes (SHA-256) for every file in a dataset, used as integrity baseline |\n| **Bit Rot** | Gradual data corruption on storage media that silently alters file contents |\n| **Immutable Backup** | Backup that cannot be modified or deleted for a defined retention period |\n| **Restore Test** | Process of recovering data from backup to an isolated environment to verify recoverability |\n| **File Entropy** | Measure of randomness in file contents; encrypted files have entropy near 8.0 bits\u002Fbyte |\n| **3-2-1 Rule** | Keep 3 copies of data, on 2 different media types, with 1 offsite copy |\n| **Backup Chain** | Sequence of full and incremental backups that must all be intact for recovery |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Restic | Encrypted, deduplicated backup with built-in integrity verification |\n| BorgBackup | Deduplicating backup with archive verification |\n| Rclone | Cloud storage sync with checksum verification |\n| AWS S3 Object Lock | Immutable backup storage with WORM compliance |\n| Azure Immutable Blob | Tamper-proof backup storage for compliance |\n| sha256sum | Standard hash computation for file integrity |\n| pg_restore | PostgreSQL backup validation and restore testing |\n\n## Common Pitfalls\n\n- **Never testing restores**: The most common failure mode. Backups that are never restored are untested assumptions.\n- **Checking only archive integrity, not data integrity**: A valid tar.gz can contain corrupted file contents. Always hash individual files.\n- **Trusting last backup without scanning for ransomware**: Backups may contain encrypted files if the infection predates the backup.\n- **Ignoring incremental chain integrity**: A single corrupted incremental backup can break the entire restore chain.\n- **No alerting on validation failures**: Backup validation must be monitored with alerts, not just logged silently.\n- **Using MD5 for integrity**: MD5 is cryptographically broken. Use SHA-256 or SHA-3 for integrity verification.\n\n## References\n\n- NIST SP 800-184: Guide for Cybersecurity Event Recovery\n- NIST CSF 2.0 RC.RP-03: Backup Integrity Verification\n- CIS Controls v8: Control 11 - Data Recovery\n- CISA Ransomware Guide: https:\u002F\u002Fwww.cisa.gov\u002Fstopransomware\n","# Validating Backup Integrity for Recovery\n\n## When to Use\n\nUse this skill when:\n- Verifying backup integrity before relying on backups for ransomware recovery\n- Building automated backup validation pipelines that run after each backup job\n- Auditing backup infrastructure to confirm recoverability for compliance (SOC 2, ISO 27001, NIST CSF RC.RP-03)\n- Detecting silent data corruption (bit rot) in backup storage before a disaster occurs\n- Validating that immutable or air-gapped backups have not been tampered with\n\n**Do not use** for initial backup configuration or scheduling. This skill focuses on post-backup validation.\n\n## Prerequisites\n\n- Access to backup storage (local, NAS, S3, Azure Blob, GCS)\n- Python 3.9+ with `hashlib` (standard library)\n- Backup manifests or baseline hash files for comparison\n- Isolated restore environment for restore testing\n- Backup tool CLI access (restic, borgbackup, rclone, or vendor-specific)\n\n## Workflow\n\n### Step 1: Generate Baseline Hash Manifest\n\nCreate a cryptographic fingerprint of every file at backup time:\n\n```bash\n# Generate SHA-256 manifest for a directory\nfind \u002Fdata\u002Fproduction -type f -exec sha256sum {} \\; > \u002Fmanifests\u002Fprod_baseline_$(date +%Y%m%d).sha256\n\n# Verify manifest format\nhead -5 \u002Fmanifests\u002Fprod_baseline_20260319.sha256\n# e3b0c44298fc1c149afbf4c8996fb924...  \u002Fdata\u002Fproduction\u002Fconfig.yaml\n# a7ffc6f8bf1ed76651c14756a061d662...  \u002Fdata\u002Fproduction\u002Fdatabase.sql\n```\n\n### Step 2: Verify Backup Archive Integrity\n\nCheck that the backup archive itself is not corrupted:\n\n```bash\n# Restic: verify backup repository integrity\nrestic -r s3:s3.amazonaws.com\u002Fbackup-bucket check --read-data\n\n# Borg: verify backup archive\nborg check --verify-data \u002Fbackup\u002Frepo::archive-2026-03-19\n\n# Tar with gzip: verify archive integrity\ngzip -t backup_20260319.tar.gz && echo \"Archive OK\" || echo \"Archive CORRUPTED\"\n\n# AWS S3: verify object checksums\naws s3api head-object --bucket backup-bucket --key daily\u002F2026-03-19.tar.gz \\\n  --checksum-mode ENABLED\n```\n\n### Step 3: Perform Restore Test to Isolated Environment\n\n```bash\n# Restore to isolated test directory\nrestic -r s3:s3.amazonaws.com\u002Fbackup-bucket restore latest --target \u002Frestore-test\u002F\n\n# Generate hash manifest of restored data\nfind \u002Frestore-test -type f -exec sha256sum {} \\; > \u002Fmanifests\u002Frestored_$(date +%Y%m%d).sha256\n\n# Compare baseline and restored manifests\ndiff \u003C(sort \u002Fmanifests\u002Fprod_baseline_20260319.sha256) \\\n     \u003C(sort \u002Fmanifests\u002Frestored_20260319.sha256)\n```\n\n### Step 4: Validate Data Completeness\n\n```bash\n# Count files in original vs restored\necho \"Original: $(find \u002Fdata\u002Fproduction -type f | wc -l) files\"\necho \"Restored: $(find \u002Frestore-test -type f | wc -l) files\"\n\n# Check total size\necho \"Original: $(du -sh \u002Fdata\u002Fproduction | cut -f1)\"\necho \"Restored: $(du -sh \u002Frestore-test | cut -f1)\"\n\n# Database consistency check after restore\npg_restore --list backup.dump | wc -l  # Count objects in dump\npsql -c \"SELECT schemaname, tablename FROM pg_tables WHERE schemaname='public';\" restored_db\n```\n\n### Step 5: Detect Ransomware Artifacts in Backups\n\nBefore trusting a backup for recovery, scan for ransomware indicators:\n\n```bash\n# Check for common ransomware file extensions\nfind \u002Frestore-test -type f \\( \\\n  -name \"*.encrypted\" -o -name \"*.locked\" -o -name \"*.crypt\" \\\n  -o -name \"*.ransom\" -o -name \"*.pay\" -o -name \"*.wncry\" \\\n  -o -name \"*.cerber\" -o -name \"*.locky\" -o -name \"*.zepto\" \\\n\\) -print\n\n# Check for ransom notes\nfind \u002Frestore-test -type f \\( \\\n  -name \"README_TO_DECRYPT*\" -o -name \"HOW_TO_RECOVER*\" \\\n  -o -name \"DECRYPT_INSTRUCTIONS*\" -o -name \"HELP_DECRYPT*\" \\\n\\) -print\n\n# Check file entropy (high entropy = possible encryption)\n# Files with entropy > 7.9 out of 8.0 are likely encrypted\npython agent.py --entropy-scan \u002Frestore-test\n```\n\n### Step 6: Automate and Schedule Validation\n\n```yaml\n# cron-based validation schedule\n# Run nightly after backup window\n0 4 * * * \u002Fopt\u002Fbackup-validator\u002Fagent.py --validate-latest --notify-on-failure\n# Weekly full restore test\n0 6 * * 0 \u002Fopt\u002Fbackup-validator\u002Fagent.py --full-restore-test --config \u002Fetc\u002Fbackup-validator\u002Fconfig.json\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Hash Manifest** | File containing cryptographic hashes (SHA-256) for every file in a dataset, used as integrity baseline |\n| **Bit Rot** | Gradual data corruption on storage media that silently alters file contents |\n| **Immutable Backup** | Backup that cannot be modified or deleted for a defined retention period |\n| **Restore Test** | Process of recovering data from backup to an isolated environment to verify recoverability |\n| **File Entropy** | Measure of randomness in file contents; encrypted files have entropy near 8.0 bits\u002Fbyte |\n| **3-2-1 Rule** | Keep 3 copies of data, on 2 different media types, with 1 offsite copy |\n| **Backup Chain** | Sequence of full and incremental backups that must all be intact for recovery |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Restic | Encrypted, deduplicated backup with built-in integrity verification |\n| BorgBackup | Deduplicating backup with archive verification |\n| Rclone | Cloud storage sync with checksum verification |\n| AWS S3 Object Lock | Immutable backup storage with WORM compliance |\n| Azure Immutable Blob | Tamper-proof backup storage for compliance |\n| sha256sum | Standard hash computation for file integrity |\n| pg_restore | PostgreSQL backup validation and restore testing |\n\n## Common Pitfalls\n\n- **Never testing restores**: The most common failure mode. Backups that are never restored are untested assumptions.\n- **Checking only archive integrity, not data integrity**: A valid tar.gz can contain corrupted file contents. Always hash individual files.\n- **Trusting last backup without scanning for ransomware**: Backups may contain encrypted files if the infection predates the backup.\n- **Ignoring incremental chain integrity**: A single corrupted incremental backup can break the entire restore chain.\n- **No alerting on validation failures**: Backup validation must be monitored with alerts, not just logged silently.\n- **Using MD5 for integrity**: MD5 is cryptographically broken. Use SHA-256 or SHA-3 for integrity verification.\n\n## References\n\n- NIST SP 800-184: Guide for Cybersecurity Event Recovery\n- NIST CSF 2.0 RC.RP-03: Backup Integrity Verification\n- CIS Controls v8: Control 11 - Data Recovery\n- CISA Ransomware Guide: https:\u002F\u002Fwww.cisa.gov\u002Fstopransomware\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"mitre_f3":35,"nist_csf":55,"subdomain":26,"description":7,"mitre_attack":60},[26,27,28,29,30,31],"incident-response","backup","integrity","hash-verification","restore-testing","disaster-recovery","mahipal","cybersecurity","1.0",{"tactics":36,"version":39,"techniques":40},[37,38],"positioning","monetization","1.1",[41,45,49,52],{"id":42,"name":43,"source":44,"tactic":37},"T1531","Account Access Removal","attack",{"id":46,"name":47,"source":48,"tactic":38},"F1018","Convert to Cryptocurrency","f3",{"id":50,"name":51,"source":48,"tactic":38},"F1047","Transfer of funds",{"id":53,"name":54,"source":48,"tactic":38},"F1017.001","Conversion to Physical Monetary Instruments: Cash",[56,57,58,59],"RS.MA-01","RS.MA-02","RS.AN-03","RC.RP-01",[61,62,63,64,65],"T1486","T1490","T1070","T1078","T1489","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fvalidating-backup-integrity-for-recovery","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add NeelakshSaxena\u002FVayu --skill validating-backup-integrity-for-recovery",{"tool":79,"command":80},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill validating-backup-integrity-for-recovery",{"tool":82,"command":83},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill validating-backup-integrity-for-recovery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",true,[87,91,97],{"path":88,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fapi-reference.md","REFERENCE","参考文档",4005,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002Freferences\u002Fapi-reference.md",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002Fagent.py","SCRIPT","脚本",10734,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002Fscripts\u002Fagent.py",[104,111,118,125,132,139],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]