[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A77SHQAX5PF481FXCDK6PJ":3,"skill-same:01M7A77SHQAX5PF481FXCDK6PJ":82},{"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":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M7A77SHQAX5PF481FXCDK6PJ","generating-and-analyzing-sboms",null,"Generate CycloneDX and SPDX SBOMs from container images and filesystems with Syft, correlate them to CVEs with Grype, and sign\u002Fattest them with Cosign. Use when you need a machine-readable dependency inventory for supply-chain risk, want to scan images or SBOMs for known vulnerabilities, or are embedding SBOM generation and vulnerability gating into CI\u002FCD.","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\u002Fgenerating-and-analyzing-sboms\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgenerating-and-analyzing-sboms\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: generating-and-analyzing-sboms\ndescription: Generate CycloneDX and SPDX SBOMs from container images and filesystems with Syft, correlate them to CVEs with Grype, and sign\u002Fattest them with Cosign. Use when you need a machine-readable dependency inventory for supply-chain risk, want to scan images or SBOMs for known vulnerabilities, or are embedding SBOM generation and vulnerability gating into CI\u002FCD.\ndomain: cybersecurity\nsubdomain: supply-chain-security\ntags:\n- supply-chain-security\n- sbom\n- cyclonedx\n- spdx\n- syft\n- grype\n- vulnerability-management\n- devsecops\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- ID.AM-08\nmitre_attack:\n- T1195.001\n---\n# Generating and Analyzing SBOMs\n\n> **Authorized Use Only:** Generate and scan SBOMs only for software and images you own or are authorized to assess. Treat SBOMs as sensitive inventory data — they reveal your dependency attack surface.\n\n## Overview\n\nA Software Bill of Materials (SBOM) is a formal, machine-readable inventory of every component, library, and dependency in a piece of software — the supply-chain equivalent of an ingredients label. SBOMs are central to defending against supply-chain compromise (CISA's SBOM initiative, US Executive Order 14028) because you cannot patch what you cannot see. The two dominant SBOM standards are:\n\n- **CycloneDX** — an OWASP standard optimized for security use cases (vulnerabilities, VEX, dependency relationships).\n- **SPDX** — a Linux Foundation \u002F ISO standard (ISO\u002FIEC 5962) strong on licensing and provenance.\n\nThe reference open-source toolchain is from Anchore:\n\n- **Syft** generates SBOMs (CycloneDX, SPDX, or its native format) from container images and filesystems.\n- **Grype** matches an SBOM (or image) against vulnerability databases to find CVEs.\n- **Cosign** (Sigstore) signs SBOMs and attaches them to images as signed attestations for tamper-evident provenance.\n\nThis skill covers producing standards-compliant SBOMs, correlating them with vulnerability intelligence, and embedding the workflow into CI\u002FCD.\n\n## When to Use\n\n- Establishing and maintaining a component inventory for applications and container images.\n- Continuously detecting known vulnerabilities (including newly disclosed CVEs against existing artifacts).\n- Satisfying procurement\u002Fregulatory SBOM requirements (CISA, EO 14028).\n- Producing signed SBOM attestations for downstream supply-chain trust.\n\n## Prerequisites\n\n- Install Syft and Grype (official install scripts):\n  ```bash\n  curl -sSfL https:\u002F\u002Fraw.githubusercontent.com\u002Fanchore\u002Fsyft\u002Fmain\u002Finstall.sh | sh -s -- -b \u002Fusr\u002Flocal\u002Fbin\n  curl -sSfL https:\u002F\u002Fraw.githubusercontent.com\u002Fanchore\u002Fgrype\u002Fmain\u002Finstall.sh | sh -s -- -b \u002Fusr\u002Flocal\u002Fbin\n  ```\n- Install Cosign for signing\u002Fattestation:\n  ```bash\n  # via Go, or download a release from https:\u002F\u002Fgithub.com\u002Fsigstore\u002Fcosign\u002Freleases\n  go install github.com\u002Fsigstore\u002Fcosign\u002Fv2\u002Fcmd\u002Fcosign@latest\n  ```\n- Access to the target images\u002Fsource and (for signing) a registry plus keys or keyless OIDC.\n\n## Objectives\n\n- Generate CycloneDX and SPDX SBOMs from images and directories.\n- Scan SBOMs and images for vulnerabilities with Grype.\n- Gate CI\u002FCD builds on severity thresholds.\n- Sign and attach SBOM attestations with Cosign and verify them.\n\n## MITRE ATT&CK Mapping\n\n| ID | Official Technique Name | Relevance to this skill |\n|----|------------------------|--------------------------|\n| T1195.001 | Supply Chain Compromise: Compromise Software Dependencies and Development Tools | SBOM generation and vulnerability correlation expose compromised or vulnerable dependencies — the attack surface adversaries abuse under this technique. |\n\nThis is a defensive supply-chain skill; the mapping reflects the adversary technique it is designed to detect and mitigate.\n\n## Workflow\n\n### 1. Generate a CycloneDX SBOM from a container image\n`-o \u003Cformat>` selects output; `cyclonedx-json` is security-oriented.\n```bash\nsyft alpine:latest -o cyclonedx-json=alpine.cdx.json\n```\n\n### 2. Generate an SPDX SBOM from a source directory\nUse the `dir:` source to inventory a checked-out repository; `spdx-json` for the SPDX standard.\n```bash\nsyft dir:. -o spdx-json=app.spdx.json\n```\n\n### 3. Emit multiple formats at once\nProduce both standards in a single pass for different consumers.\n```bash\nsyft myorg\u002Fapp:1.4.2 \\\n  -o cyclonedx-json=app.cdx.json \\\n  -o spdx-json=app.spdx.json \\\n  -o table\n```\n\n### 4. Scan the SBOM for vulnerabilities with Grype\nDecoupling generation from scanning lets you re-scan stored SBOMs as new CVEs land — without rebuilding.\n```bash\n# Scan an existing SBOM\ngrype sbom:app.cdx.json -o table\n\n# JSON report for automation\ngrype sbom:app.cdx.json -o json > app.vulns.json\n```\nYou can also scan an image directly (Grype generates the SBOM internally):\n```bash\ngrype myorg\u002Fapp:1.4.2 -o table\n```\n\n### 5. Gate CI\u002FCD on severity\n`--fail-on` exits non-zero at or above a severity, failing the pipeline.\n```bash\ngrype sbom:app.cdx.json --fail-on high\n```\nFilter out unfixable noise with a `.grype.yaml` policy (`only-fixed: true`) or `--only-fixed`:\n```bash\ngrype sbom:app.cdx.json --only-fixed --fail-on critical\n```\n\n### 6. Sign and attach the SBOM as an attestation\nCosign records the SBOM as a signed, in-toto attestation alongside the image in the registry.\n```bash\n# Key-based signing\ncosign attest --key cosign.key \\\n  --predicate app.spdx.json \\\n  --type spdxjson \\\n  myorg\u002Fapp:1.4.2\n\n# Keyless (Sigstore OIDC \u002F Fulcio + Rekor)\nCOSIGN_EXPERIMENTAL=1 cosign attest \\\n  --predicate app.cdx.json \\\n  --type cyclonedx \\\n  myorg\u002Fapp:1.4.2\n```\n\n### 7. Verify the attestation downstream\nConsumers verify provenance before trusting an image.\n```bash\ncosign verify-attestation --key cosign.pub --type spdxjson myorg\u002Fapp:1.4.2\n```\n\n### 8. Retrieve and re-scan attached SBOMs\nPull the attested SBOM from the registry and re-run Grype as part of continuous monitoring.\n```bash\ncosign download attestation myorg\u002Fapp:1.4.2 \\\n  | jq -r '.payload' | base64 -d | jq '.predicate' > pulled.spdx.json\ngrype sbom:pulled.spdx.json -o table\n```\n\n### 9. Correlate to vulnerability intelligence\nFeed Grype JSON into your vulnerability management workflow: deduplicate by CVE, enrich with EPSS\u002FKEV for prioritization, and track remediation SLAs. Re-scan stored SBOMs on each Grype DB update to catch newly disclosed CVEs in unchanged artifacts.\n\n## Tools and Resources\n\n| Tool | Purpose | Link |\n|------|---------|------|\n| Syft | SBOM generation | https:\u002F\u002Fgithub.com\u002Fanchore\u002Fsyft |\n| Grype | Vulnerability scanning of SBOMs\u002Fimages | https:\u002F\u002Fgithub.com\u002Fanchore\u002Fgrype |\n| Cosign | SBOM signing\u002Fattestation | https:\u002F\u002Fgithub.com\u002Fsigstore\u002Fcosign |\n| CycloneDX | Security-focused SBOM standard | https:\u002F\u002Fcyclonedx.org\u002F |\n| SPDX | ISO SBOM standard | https:\u002F\u002Fspdx.dev\u002F |\n| CISA SBOM | Guidance and minimum elements | https:\u002F\u002Fwww.cisa.gov\u002Fsbom |\n\n## Format Comparison\n\n| Aspect | CycloneDX | SPDX |\n|--------|-----------|------|\n| Steward | OWASP | Linux Foundation \u002F ISO 5962 |\n| Strength | Security, VEX, vulnerabilities | Licensing, provenance |\n| Common syft `-o` values | `cyclonedx-json`, `cyclonedx-xml` | `spdx-json`, `spdx` (tag-value) |\n\n## Validation Criteria\n\n- [ ] CycloneDX SBOM generated from the target image\n- [ ] SPDX SBOM generated from source where required\n- [ ] SBOM scanned with Grype producing a CVE report\n- [ ] CI\u002FCD gated with `--fail-on` at an agreed severity\n- [ ] SBOM signed and attached as an attestation with Cosign\n- [ ] Attestation verified downstream\n- [ ] Stored SBOMs re-scanned on Grype DB updates\n- [ ] Findings correlated\u002Fprioritized (EPSS\u002FKEV) and tracked to remediation\n","# Generating and Analyzing SBOMs\n\n> **Authorized Use Only:** Generate and scan SBOMs only for software and images you own or are authorized to assess. Treat SBOMs as sensitive inventory data — they reveal your dependency attack surface.\n\n## Overview\n\nA Software Bill of Materials (SBOM) is a formal, machine-readable inventory of every component, library, and dependency in a piece of software — the supply-chain equivalent of an ingredients label. SBOMs are central to defending against supply-chain compromise (CISA's SBOM initiative, US Executive Order 14028) because you cannot patch what you cannot see. The two dominant SBOM standards are:\n\n- **CycloneDX** — an OWASP standard optimized for security use cases (vulnerabilities, VEX, dependency relationships).\n- **SPDX** — a Linux Foundation \u002F ISO standard (ISO\u002FIEC 5962) strong on licensing and provenance.\n\nThe reference open-source toolchain is from Anchore:\n\n- **Syft** generates SBOMs (CycloneDX, SPDX, or its native format) from container images and filesystems.\n- **Grype** matches an SBOM (or image) against vulnerability databases to find CVEs.\n- **Cosign** (Sigstore) signs SBOMs and attaches them to images as signed attestations for tamper-evident provenance.\n\nThis skill covers producing standards-compliant SBOMs, correlating them with vulnerability intelligence, and embedding the workflow into CI\u002FCD.\n\n## When to Use\n\n- Establishing and maintaining a component inventory for applications and container images.\n- Continuously detecting known vulnerabilities (including newly disclosed CVEs against existing artifacts).\n- Satisfying procurement\u002Fregulatory SBOM requirements (CISA, EO 14028).\n- Producing signed SBOM attestations for downstream supply-chain trust.\n\n## Prerequisites\n\n- Install Syft and Grype (official install scripts):\n  ```bash\n  curl -sSfL https:\u002F\u002Fraw.githubusercontent.com\u002Fanchore\u002Fsyft\u002Fmain\u002Finstall.sh | sh -s -- -b \u002Fusr\u002Flocal\u002Fbin\n  curl -sSfL https:\u002F\u002Fraw.githubusercontent.com\u002Fanchore\u002Fgrype\u002Fmain\u002Finstall.sh | sh -s -- -b \u002Fusr\u002Flocal\u002Fbin\n  ```\n- Install Cosign for signing\u002Fattestation:\n  ```bash\n  # via Go, or download a release from https:\u002F\u002Fgithub.com\u002Fsigstore\u002Fcosign\u002Freleases\n  go install github.com\u002Fsigstore\u002Fcosign\u002Fv2\u002Fcmd\u002Fcosign@latest\n  ```\n- Access to the target images\u002Fsource and (for signing) a registry plus keys or keyless OIDC.\n\n## Objectives\n\n- Generate CycloneDX and SPDX SBOMs from images and directories.\n- Scan SBOMs and images for vulnerabilities with Grype.\n- Gate CI\u002FCD builds on severity thresholds.\n- Sign and attach SBOM attestations with Cosign and verify them.\n\n## MITRE ATT&CK Mapping\n\n| ID | Official Technique Name | Relevance to this skill |\n|----|------------------------|--------------------------|\n| T1195.001 | Supply Chain Compromise: Compromise Software Dependencies and Development Tools | SBOM generation and vulnerability correlation expose compromised or vulnerable dependencies — the attack surface adversaries abuse under this technique. |\n\nThis is a defensive supply-chain skill; the mapping reflects the adversary technique it is designed to detect and mitigate.\n\n## Workflow\n\n### 1. Generate a CycloneDX SBOM from a container image\n`-o \u003Cformat>` selects output; `cyclonedx-json` is security-oriented.\n```bash\nsyft alpine:latest -o cyclonedx-json=alpine.cdx.json\n```\n\n### 2. Generate an SPDX SBOM from a source directory\nUse the `dir:` source to inventory a checked-out repository; `spdx-json` for the SPDX standard.\n```bash\nsyft dir:. -o spdx-json=app.spdx.json\n```\n\n### 3. Emit multiple formats at once\nProduce both standards in a single pass for different consumers.\n```bash\nsyft myorg\u002Fapp:1.4.2 \\\n  -o cyclonedx-json=app.cdx.json \\\n  -o spdx-json=app.spdx.json \\\n  -o table\n```\n\n### 4. Scan the SBOM for vulnerabilities with Grype\nDecoupling generation from scanning lets you re-scan stored SBOMs as new CVEs land — without rebuilding.\n```bash\n# Scan an existing SBOM\ngrype sbom:app.cdx.json -o table\n\n# JSON report for automation\ngrype sbom:app.cdx.json -o json > app.vulns.json\n```\nYou can also scan an image directly (Grype generates the SBOM internally):\n```bash\ngrype myorg\u002Fapp:1.4.2 -o table\n```\n\n### 5. Gate CI\u002FCD on severity\n`--fail-on` exits non-zero at or above a severity, failing the pipeline.\n```bash\ngrype sbom:app.cdx.json --fail-on high\n```\nFilter out unfixable noise with a `.grype.yaml` policy (`only-fixed: true`) or `--only-fixed`:\n```bash\ngrype sbom:app.cdx.json --only-fixed --fail-on critical\n```\n\n### 6. Sign and attach the SBOM as an attestation\nCosign records the SBOM as a signed, in-toto attestation alongside the image in the registry.\n```bash\n# Key-based signing\ncosign attest --key cosign.key \\\n  --predicate app.spdx.json \\\n  --type spdxjson \\\n  myorg\u002Fapp:1.4.2\n\n# Keyless (Sigstore OIDC \u002F Fulcio + Rekor)\nCOSIGN_EXPERIMENTAL=1 cosign attest \\\n  --predicate app.cdx.json \\\n  --type cyclonedx \\\n  myorg\u002Fapp:1.4.2\n```\n\n### 7. Verify the attestation downstream\nConsumers verify provenance before trusting an image.\n```bash\ncosign verify-attestation --key cosign.pub --type spdxjson myorg\u002Fapp:1.4.2\n```\n\n### 8. Retrieve and re-scan attached SBOMs\nPull the attested SBOM from the registry and re-run Grype as part of continuous monitoring.\n```bash\ncosign download attestation myorg\u002Fapp:1.4.2 \\\n  | jq -r '.payload' | base64 -d | jq '.predicate' > pulled.spdx.json\ngrype sbom:pulled.spdx.json -o table\n```\n\n### 9. Correlate to vulnerability intelligence\nFeed Grype JSON into your vulnerability management workflow: deduplicate by CVE, enrich with EPSS\u002FKEV for prioritization, and track remediation SLAs. Re-scan stored SBOMs on each Grype DB update to catch newly disclosed CVEs in unchanged artifacts.\n\n## Tools and Resources\n\n| Tool | Purpose | Link |\n|------|---------|------|\n| Syft | SBOM generation | https:\u002F\u002Fgithub.com\u002Fanchore\u002Fsyft |\n| Grype | Vulnerability scanning of SBOMs\u002Fimages | https:\u002F\u002Fgithub.com\u002Fanchore\u002Fgrype |\n| Cosign | SBOM signing\u002Fattestation | https:\u002F\u002Fgithub.com\u002Fsigstore\u002Fcosign |\n| CycloneDX | Security-focused SBOM standard | https:\u002F\u002Fcyclonedx.org\u002F |\n| SPDX | ISO SBOM standard | https:\u002F\u002Fspdx.dev\u002F |\n| CISA SBOM | Guidance and minimum elements | https:\u002F\u002Fwww.cisa.gov\u002Fsbom |\n\n## Format Comparison\n\n| Aspect | CycloneDX | SPDX |\n|--------|-----------|------|\n| Steward | OWASP | Linux Foundation \u002F ISO 5962 |\n| Strength | Security, VEX, vulnerabilities | Licensing, provenance |\n| Common syft `-o` values | `cyclonedx-json`, `cyclonedx-xml` | `spdx-json`, `spdx` (tag-value) |\n\n## Validation Criteria\n\n- [ ] CycloneDX SBOM generated from the target image\n- [ ] SPDX SBOM generated from source where required\n- [ ] SBOM scanned with Grype producing a CVE report\n- [ ] CI\u002FCD gated with `--fail-on` at an agreed severity\n- [ ] SBOM signed and attached as an attestation with Cosign\n- [ ] Attestation verified downstream\n- [ ] Stored SBOMs re-scanned on Grype DB updates\n- [ ] Findings correlated\u002Fprioritized (EPSS\u002FKEV) and tracked to remediation\n",{"name":5,"tags":25,"author":34,"domain":35,"license":15,"version":36,"nist_csf":37,"subdomain":26,"description":7,"mitre_attack":39},[26,27,28,29,30,31,32,33],"supply-chain-security","sbom","cyclonedx","spdx","syft","grype","vulnerability-management","devsecops","mahipal","cybersecurity","1.0",[38],"ID.AM-08",[40],"T1195.001","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fgenerating-and-analyzing-sboms","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":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add NeelakshSaxena\u002FVayu --skill generating-and-analyzing-sboms",{"tool":54,"command":55},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill generating-and-analyzing-sboms",{"tool":57,"command":58},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill generating-and-analyzing-sboms","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgenerating-and-analyzing-sboms\u002FSKILL.md",true,[62,66,72,76],{"path":63,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fapi-reference.md","REFERENCE","参考文档",2393,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgenerating-and-analyzing-sboms\u002Freferences\u002Fapi-reference.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fstandards.md",1430,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgenerating-and-analyzing-sboms\u002Freferences\u002Fstandards.md",{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"scripts\u002Fagent.py","SCRIPT","脚本",5466,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgenerating-and-analyzing-sboms\u002Fscripts\u002Fagent.py",[83,90,97,104,111,118],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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":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},"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":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},"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":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},"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",[],[]]