[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AB6ZDEMC3YV43HW2DXZQJ5":3,"skill-same:01M7AB6ZDEMC3YV43HW2DXZQJ5":101},{"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":46,"commitSha":47,"skillDirectory":48,"forksCount":14,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M7AB6ZDEMC3YV43HW2DXZQJ5","scanning-docker-images-with-trivy",null,"Scans a Docker image with Trivy for vulnerabilities in OS packages and language dependencies, misconfiguration, exposed secrets, and licence violations, emitting SARIF, CycloneDX, or SPDX output. Use when scanning or gating a specific image, wiring an image scan into CI\u002FCD, or checking an image during an incident investigation. Keywords: Trivy, image scan, --severity, --exit-code, SARIF, ignore file, .trivyignore. Do not use for cluster-wide scanning or non-image targets - use performing-container-security-scanning-with-trivy; when the toolchain is Grype use scanning-container-images-with-grype.","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\u002Fscanning-docker-images-with-trivy\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-docker-images-with-trivy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: scanning-docker-images-with-trivy\ndescription: >-\n  Scans a Docker image with Trivy for vulnerabilities in OS packages and language\n  dependencies, misconfiguration, exposed secrets, and licence violations, emitting SARIF,\n  CycloneDX, or SPDX output. Use when scanning or gating a specific image, wiring an image\n  scan into CI\u002FCD, or checking an image during an incident investigation. Keywords: Trivy,\n  image scan, --severity, --exit-code, SARIF, ignore file, .trivyignore. Do not use for\n  cluster-wide scanning or non-image targets - use\n  performing-container-security-scanning-with-trivy; when the toolchain is Grype use\n  scanning-container-images-with-grype.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- containers\n- docker\n- security\n- trivy\n- vulnerability-scanning\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- PR.IR-01\n- ID.AM-08\n- DE.CM-01\nmitre_attack:\n- T1610\n- T1611\n- T1609\n- T1525\n- T1190\n---\n# Scanning Docker Images with Trivy\n\n## Overview\n\nTrivy is a comprehensive open-source vulnerability scanner by Aqua Security that detects vulnerabilities in OS packages, language-specific dependencies, misconfigurations, secrets, and license violations within container images. It integrates into CI\u002FCD pipelines and supports multiple output formats including SARIF, CycloneDX, and SPDX.\n\n\n## When to Use\n\n- When conducting security assessments that involve scanning docker images with trivy\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Docker Engine 20.10+\n- Trivy v0.50+ installed\n- Internet access for vulnerability database updates\n- Container registry credentials (for private registries)\n\n## Core Concepts\n\n### Scanner Types\n\n| Scanner | Flag | Detects |\n|---------|------|---------|\n| Vulnerability | `--scanners vuln` | CVEs in OS packages and libraries |\n| Misconfiguration | `--scanners misconfig` | Dockerfile\u002FK8s manifest misconfigs |\n| Secret | `--scanners secret` | Hardcoded passwords, API keys, tokens |\n| License | `--scanners license` | Software license compliance issues |\n\n### Severity Levels\n\n- **CRITICAL**: CVSS 9.0-10.0 - Immediate action required\n- **HIGH**: CVSS 7.0-8.9 - Fix before production deployment\n- **MEDIUM**: CVSS 4.0-6.9 - Plan remediation\n- **LOW**: CVSS 0.1-3.9 - Accept or fix opportunistically\n- **UNKNOWN**: Unscored - Evaluate manually\n\n### Vulnerability Database\n\nTrivy uses multiple vulnerability databases:\n- NVD (National Vulnerability Database)\n- Red Hat Security Data\n- Alpine SecDB\n- Debian Security Tracker\n- Ubuntu CVE Tracker\n- Amazon Linux Security Center\n- GitHub Advisory Database\n\n## Workflow\n\n### Step 1: Install Trivy\n\n```bash\n# Linux (apt)\nsudo apt-get install wget apt-transport-https gnupg lsb-release\nwget -qO - https:\u002F\u002Faquasecurity.github.io\u002Ftrivy-repo\u002Fdeb\u002Fpublic.key | gpg --dearmor | sudo tee \u002Fusr\u002Fshare\u002Fkeyrings\u002Ftrivy.gpg > \u002Fdev\u002Fnull\necho \"deb [signed-by=\u002Fusr\u002Fshare\u002Fkeyrings\u002Ftrivy.gpg] https:\u002F\u002Faquasecurity.github.io\u002Ftrivy-repo\u002Fdeb $(lsb_release -sc) main\" | sudo tee -a \u002Fetc\u002Fapt\u002Fsources.list.d\u002Ftrivy.list\nsudo apt-get update && sudo apt-get install trivy\n\n# macOS\nbrew install trivy\n\n# Docker\ndocker pull aquasecurity\u002Ftrivy:latest\n```\n\n### Step 2: Basic Image Scanning\n\n```bash\n# Scan a public image\ntrivy image python:3.12-slim\n\n# Scan with severity filter\ntrivy image --severity CRITICAL,HIGH nginx:latest\n\n# Ignore unfixed vulnerabilities\ntrivy image --ignore-unfixed alpine:3.19\n\n# Scan local image\ndocker build -t myapp:latest .\ntrivy image myapp:latest\n\n# Scan from tar archive\ndocker save myapp:latest -o myapp.tar\ntrivy image --input myapp.tar\n```\n\n### Step 3: Advanced Scanning Options\n\n```bash\n# All scanners (vuln + misconfig + secret + license)\ntrivy image --scanners vuln,misconfig,secret,license myapp:latest\n\n# Generate SBOM in CycloneDX format\ntrivy image --format cyclonedx --output sbom.cdx.json myapp:latest\n\n# Generate SBOM in SPDX format\ntrivy image --format spdx-json --output sbom.spdx.json myapp:latest\n\n# JSON output for programmatic processing\ntrivy image --format json --output results.json myapp:latest\n\n# SARIF output for GitHub Security tab\ntrivy image --format sarif --output results.sarif myapp:latest\n\n# Template-based output\ntrivy image --format template --template \"@contrib\u002Fhtml.tpl\" --output report.html myapp:latest\n\n# Scan specific layers only\ntrivy image --list-all-pkgs myapp:latest\n```\n\n### Step 4: Scanning Kubernetes Manifests\n\n```bash\n# Scan Dockerfile for misconfigurations\ntrivy config Dockerfile\n\n# Scan Kubernetes manifests\ntrivy config k8s-deployment.yaml\n\n# Scan Helm charts\ntrivy config .\u002Fhelm-chart\u002F\n\n# Scan Terraform files\ntrivy config .\u002Fterraform\u002F\n```\n\n### Step 5: CI\u002FCD Integration\n\n```yaml\n# GitHub Actions\nname: Trivy Container Scan\non: push\n\njobs:\n  scan:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Build image\n        run: docker build -t myapp:${{ github.sha }} .\n\n      - name: Run Trivy vulnerability scanner\n        uses: aquasecurity\u002Ftrivy-action@master\n        with:\n          image-ref: myapp:${{ github.sha }}\n          format: sarif\n          output: trivy-results.sarif\n          severity: CRITICAL,HIGH\n          exit-code: 1\n\n      - name: Upload Trivy scan results\n        uses: github\u002Fcodeql-action\u002Fupload-sarif@v3\n        if: always()\n        with:\n          sarif_file: trivy-results.sarif\n\n      - name: Generate SBOM\n        uses: aquasecurity\u002Ftrivy-action@master\n        with:\n          image-ref: myapp:${{ github.sha }}\n          format: cyclonedx\n          output: sbom.cdx.json\n```\n\n```yaml\n# GitLab CI\ntrivy-scan:\n  stage: security\n  image:\n    name: aquasecurity\u002Ftrivy:latest\n    entrypoint: [\"\"]\n  script:\n    - trivy image --exit-code 1 --severity CRITICAL,HIGH\n        --format json --output gl-container-scanning-report.json\n        $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA\n  artifacts:\n    reports:\n      container_scanning: gl-container-scanning-report.json\n```\n\n### Step 6: Policy Enforcement with .trivyignore\n\n```bash\n# .trivyignore - Ignore specific CVEs with expiry\n# Accepted risk: low-impact vulnerability in dev dependency\nCVE-2023-12345 exp:2025-06-01\n\n# False positive: not exploitable in our configuration\nCVE-2024-67890\n\n# Vendor will not fix\nCVE-2023-11111\n```\n\n### Step 7: Scan Private Registry Images\n\n```bash\n# Docker Hub (uses ~\u002F.docker\u002Fconfig.json)\ntrivy image myregistry.azurecr.io\u002Fmyapp:latest\n\n# ECR\naws ecr get-login-password --region us-east-1 | docker login --username AWS --password-stdin \u003Caccount>.dkr.ecr.us-east-1.amazonaws.com\ntrivy image \u003Caccount>.dkr.ecr.us-east-1.amazonaws.com\u002Fmyapp:latest\n\n# GCR\ntrivy image gcr.io\u002Fmy-project\u002Fmyapp:latest\n\n# With explicit credentials\nTRIVY_USERNAME=user TRIVY_PASSWORD=pass trivy image registry.example.com\u002Fmyapp:latest\n```\n\n## Validation Commands\n\n```bash\n# Verify Trivy installation\ntrivy version\n\n# Update vulnerability database\ntrivy image --download-db-only\n\n# Quick scan with table output\ntrivy image --severity CRITICAL python:3.12\n\n# Verify no CRITICAL vulnerabilities\ntrivy image --exit-code 1 --severity CRITICAL myapp:latest\necho \"Exit code: $?\"  # 0 = no vulns, 1 = vulns found\n```\n\n## References\n\n- [Trivy Documentation](https:\u002F\u002Ftrivy.dev\u002Fdocs\u002F)\n- [Trivy GitHub Repository](https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Ftrivy)\n- [Trivy GitHub Action](https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Ftrivy-action)\n- [Aqua Security - Trivy Scanner Guide](https:\u002F\u002Fwww.aquasec.com\u002Fproducts\u002Ftrivy\u002F)\n","# Scanning Docker Images with Trivy\n\n## Overview\n\nTrivy is a comprehensive open-source vulnerability scanner by Aqua Security that detects vulnerabilities in OS packages, language-specific dependencies, misconfigurations, secrets, and license violations within container images. It integrates into CI\u002FCD pipelines and supports multiple output formats including SARIF, CycloneDX, and SPDX.\n\n\n## When to Use\n\n- When conducting security assessments that involve scanning docker images with trivy\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Docker Engine 20.10+\n- Trivy v0.50+ installed\n- Internet access for vulnerability database updates\n- Container registry credentials (for private registries)\n\n## Core Concepts\n\n### Scanner Types\n\n| Scanner | Flag | Detects |\n|---------|------|---------|\n| Vulnerability | `--scanners vuln` | CVEs in OS packages and libraries |\n| Misconfiguration | `--scanners misconfig` | Dockerfile\u002FK8s manifest misconfigs |\n| Secret | `--scanners secret` | Hardcoded passwords, API keys, tokens |\n| License | `--scanners license` | Software license compliance issues |\n\n### Severity Levels\n\n- **CRITICAL**: CVSS 9.0-10.0 - Immediate action required\n- **HIGH**: CVSS 7.0-8.9 - Fix before production deployment\n- **MEDIUM**: CVSS 4.0-6.9 - Plan remediation\n- **LOW**: CVSS 0.1-3.9 - Accept or fix opportunistically\n- **UNKNOWN**: Unscored - Evaluate manually\n\n### Vulnerability Database\n\nTrivy uses multiple vulnerability databases:\n- NVD (National Vulnerability Database)\n- Red Hat Security Data\n- Alpine SecDB\n- Debian Security Tracker\n- Ubuntu CVE Tracker\n- Amazon Linux Security Center\n- GitHub Advisory Database\n\n## Workflow\n\n### Step 1: Install Trivy\n\n```bash\n# Linux (apt)\nsudo apt-get install wget apt-transport-https gnupg lsb-release\nwget -qO - https:\u002F\u002Faquasecurity.github.io\u002Ftrivy-repo\u002Fdeb\u002Fpublic.key | gpg --dearmor | sudo tee \u002Fusr\u002Fshare\u002Fkeyrings\u002Ftrivy.gpg > \u002Fdev\u002Fnull\necho \"deb [signed-by=\u002Fusr\u002Fshare\u002Fkeyrings\u002Ftrivy.gpg] https:\u002F\u002Faquasecurity.github.io\u002Ftrivy-repo\u002Fdeb $(lsb_release -sc) main\" | sudo tee -a \u002Fetc\u002Fapt\u002Fsources.list.d\u002Ftrivy.list\nsudo apt-get update && sudo apt-get install trivy\n\n# macOS\nbrew install trivy\n\n# Docker\ndocker pull aquasecurity\u002Ftrivy:latest\n```\n\n### Step 2: Basic Image Scanning\n\n```bash\n# Scan a public image\ntrivy image python:3.12-slim\n\n# Scan with severity filter\ntrivy image --severity CRITICAL,HIGH nginx:latest\n\n# Ignore unfixed vulnerabilities\ntrivy image --ignore-unfixed alpine:3.19\n\n# Scan local image\ndocker build -t myapp:latest .\ntrivy image myapp:latest\n\n# Scan from tar archive\ndocker save myapp:latest -o myapp.tar\ntrivy image --input myapp.tar\n```\n\n### Step 3: Advanced Scanning Options\n\n```bash\n# All scanners (vuln + misconfig + secret + license)\ntrivy image --scanners vuln,misconfig,secret,license myapp:latest\n\n# Generate SBOM in CycloneDX format\ntrivy image --format cyclonedx --output sbom.cdx.json myapp:latest\n\n# Generate SBOM in SPDX format\ntrivy image --format spdx-json --output sbom.spdx.json myapp:latest\n\n# JSON output for programmatic processing\ntrivy image --format json --output results.json myapp:latest\n\n# SARIF output for GitHub Security tab\ntrivy image --format sarif --output results.sarif myapp:latest\n\n# Template-based output\ntrivy image --format template --template \"@contrib\u002Fhtml.tpl\" --output report.html myapp:latest\n\n# Scan specific layers only\ntrivy image --list-all-pkgs myapp:latest\n```\n\n### Step 4: Scanning Kubernetes Manifests\n\n```bash\n# Scan Dockerfile for misconfigurations\ntrivy config Dockerfile\n\n# Scan Kubernetes manifests\ntrivy config k8s-deployment.yaml\n\n# Scan Helm charts\ntrivy config .\u002Fhelm-chart\u002F\n\n# Scan Terraform files\ntrivy config .\u002Fterraform\u002F\n```\n\n### Step 5: CI\u002FCD Integration\n\n```yaml\n# GitHub Actions\nname: Trivy Container Scan\non: push\n\njobs:\n  scan:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Build image\n        run: docker build -t myapp:${{ github.sha }} .\n\n      - name: Run Trivy vulnerability scanner\n        uses: aquasecurity\u002Ftrivy-action@master\n        with:\n          image-ref: myapp:${{ github.sha }}\n          format: sarif\n          output: trivy-results.sarif\n          severity: CRITICAL,HIGH\n          exit-code: 1\n\n      - name: Upload Trivy scan results\n        uses: github\u002Fcodeql-action\u002Fupload-sarif@v3\n        if: always()\n        with:\n          sarif_file: trivy-results.sarif\n\n      - name: Generate SBOM\n        uses: aquasecurity\u002Ftrivy-action@master\n        with:\n          image-ref: myapp:${{ github.sha }}\n          format: cyclonedx\n          output: sbom.cdx.json\n```\n\n```yaml\n# GitLab CI\ntrivy-scan:\n  stage: security\n  image:\n    name: aquasecurity\u002Ftrivy:latest\n    entrypoint: [\"\"]\n  script:\n    - trivy image --exit-code 1 --severity CRITICAL,HIGH\n        --format json --output gl-container-scanning-report.json\n        $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA\n  artifacts:\n    reports:\n      container_scanning: gl-container-scanning-report.json\n```\n\n### Step 6: Policy Enforcement with .trivyignore\n\n```bash\n# .trivyignore - Ignore specific CVEs with expiry\n# Accepted risk: low-impact vulnerability in dev dependency\nCVE-2023-12345 exp:2025-06-01\n\n# False positive: not exploitable in our configuration\nCVE-2024-67890\n\n# Vendor will not fix\nCVE-2023-11111\n```\n\n### Step 7: Scan Private Registry Images\n\n```bash\n# Docker Hub (uses ~\u002F.docker\u002Fconfig.json)\ntrivy image myregistry.azurecr.io\u002Fmyapp:latest\n\n# ECR\naws ecr get-login-password --region us-east-1 | docker login --username AWS --password-stdin \u003Caccount>.dkr.ecr.us-east-1.amazonaws.com\ntrivy image \u003Caccount>.dkr.ecr.us-east-1.amazonaws.com\u002Fmyapp:latest\n\n# GCR\ntrivy image gcr.io\u002Fmy-project\u002Fmyapp:latest\n\n# With explicit credentials\nTRIVY_USERNAME=user TRIVY_PASSWORD=pass trivy image registry.example.com\u002Fmyapp:latest\n```\n\n## Validation Commands\n\n```bash\n# Verify Trivy installation\ntrivy version\n\n# Update vulnerability database\ntrivy image --download-db-only\n\n# Quick scan with table output\ntrivy image --severity CRITICAL python:3.12\n\n# Verify no CRITICAL vulnerabilities\ntrivy image --exit-code 1 --severity CRITICAL myapp:latest\necho \"Exit code: $?\"  # 0 = no vulns, 1 = vulns found\n```\n\n## References\n\n- [Trivy Documentation](https:\u002F\u002Ftrivy.dev\u002Fdocs\u002F)\n- [Trivy GitHub Repository](https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Ftrivy)\n- [Trivy GitHub Action](https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Ftrivy-action)\n- [Aqua Security - Trivy Scanner Guide](https:\u002F\u002Fwww.aquasec.com\u002Fproducts\u002Ftrivy\u002F)\n",{"name":5,"tags":25,"author":31,"domain":32,"license":15,"version":33,"nist_csf":34,"subdomain":39,"description":7,"mitre_attack":40},[26,27,28,29,30],"containers","docker","security","trivy","vulnerability-scanning","mahipal","cybersecurity","1.0",[35,36,37,38],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01","container-security",[41,42,43,44,45],"T1610","T1611","T1609","T1525","T1190","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fscanning-docker-images-with-trivy","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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add NeelakshSaxena\u002FVayu --skill scanning-docker-images-with-trivy",{"tool":59,"command":60},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill scanning-docker-images-with-trivy",{"tool":62,"command":63},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill scanning-docker-images-with-trivy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-docker-images-with-trivy\u002FSKILL.md",true,[67,73,77,83,87,91,97],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"assets\u002Ftemplate.md","ASSET","资产文件",1698,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-docker-images-with-trivy\u002Fassets\u002Ftemplate.md",{"path":74,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fapi-reference.md","REFERENCE","参考文档",1633,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-docker-images-with-trivy\u002Freferences\u002Fapi-reference.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fstandards.md",2517,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-docker-images-with-trivy\u002Freferences\u002Fstandards.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fworkflows.md",3689,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-docker-images-with-trivy\u002Freferences\u002Fworkflows.md",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fagent.py","SCRIPT","脚本",5696,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-docker-images-with-trivy\u002Fscripts\u002Fagent.py",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fprocess.py",10957,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscanning-docker-images-with-trivy\u002Fscripts\u002Fprocess.py",[102,109,116,123,130,137],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"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":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"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":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"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",[],[]]