[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AB4VFZ42GTDFQ41SYSRDT3":3,"skill-same:01M7AB4VFZ42GTDFQ41SYSRDT3":60},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7AB4VFZ42GTDFQ41SYSRDT3","runpod-mcp",null,"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.","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\u002Frunpod-mcp\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: runpod-mcp\ndescription: >-\n  Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates,\n  network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via\n  the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools\n  (create-pod, list-endpoints, …) are connected in this session, or to connect\n  them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra\n  CRUD when MCP is available; use runpodctl for the terminal, file transfer, or\n  SSH setup.\nallowed-tools: Bash(npx:*), Bash(claude:*)\ncompatibility: Linux, macOS, Windows\nmetadata:\n  author: runpod\n  version: \"1.2.0\" # x-release-please-version\nlicense: Apache-2.0\n---\n\n# Runpod MCP\n\nThe Runpod MCP server exposes Runpod's control plane as structured tool calls,\nso an MCP-capable agent can manage infrastructure without shelling out. It is the\nsame Runpod REST API that `runpodctl` uses — pick MCP when its tools are\nconnected (typed params, structured errors, no shell quoting).\n\n**For a multi-step job, read the worked example before calling tools.** Tool calls are easy\nto issue and easy to issue in the wrong order — the verified end-to-end sequences live in\n[runpod\u002Fgolden-paths\u002FREADME.md](..\u002Frunpod\u002Fgolden-paths\u002FREADME.md) (image → template →\nendpoint, pod → volume → serverless, multi-region, autoscaling, monitoring). This skill\ncovers what each tool does; the paths cover what order to do them in and what it costs.\n\n## Connect\n\nConnect the hosted server with **your API key as a Bearer header** if you also use runpodctl\u002Fflash — that one key auths the MCP *and* the CLIs (the 80% path):\n\n```bash\nclaude mcp add --transport http runpod -s user https:\u002F\u002Fmcp.getrunpod.io\u002F \\\n  --header \"Authorization: Bearer $RUNPOD_API_KEY\"\n```\n\nPlain **OAuth** (\"Sign in with Runpod\", via `npx @runpod\u002Fmcp-server@latest add`) is MCP-only — the CLIs stay unauthed, so use it only for MCP-only work. Local **stdio** runs the server as a subprocess with your key. Those variants + the key-vs-OAuth tradeoff: **[reference\u002Fconnect.md](reference\u002Fconnect.md)**. After connecting, reconnect the client (in Claude Code, `\u002Fmcp`) so the tools load.\n\n**Verify it's live (do this before relying on MCP):** in Claude Code run `\u002Fmcp` —\n`runpod` should show **Connected**, not *Needs authentication* (if it's the latter,\nsign in there first; the bundled plugin server registers the URL but stays inert\nuntil you authenticate). Confirm a real call works by asking for `list-endpoints`.\nIf the `runpod` tools aren't present at all, the server isn't connected — (re)run the\ninstall above, or fall back to **runpodctl** for this task.\n\n**Check the server version (which REST API it drives):** the MCP `initialize` handshake\nreturns it in `serverInfo.version`. `\u002Fmcp` in Claude Code shows it, or probe the hosted\nserver directly:\n\n```bash\nprintf '%s\\n' '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2024-11-05\",\"capabilities\":{},\"clientInfo\":{\"name\":\"probe\",\"version\":\"0\"}}}' \\\n| curl -s -X POST https:\u002F\u002Fmcp.getrunpod.io\u002F -H \"Content-Type: application\u002Fjson\" \\\n    -H \"Accept: application\u002Fjson, text\u002Fevent-stream\" -H \"Authorization: Bearer $RUNPOD_API_KEY\" -d @-\n# → serverInfo.version e.g. \"3.0.0 [RUNPOD_REST_VERSION=v2]\"  (verified 2026-07-29)\n```\n\nThe MCP server drives Runpod's **REST v2** internally (`RUNPOD_REST_VERSION=v2`), so most\ntools avoid the buggy **public `rest.runpod.io\u002Fv1`** control API. Two exceptions worth\nknowing: the Hub, public-endpoint and `set-endpoint-gpus` tools go through GraphQL (so they\nwork under either REST version), and **CPU serverless endpoints are not creatable through\nMCP** — v2 has no CPU-endpoint concept at all (`create-endpoint` requires `gpuPoolIds`), so\nuse `runpodctl serverless create --compute-type CPU` for those.\n\n**Prefer MCP or `runpodctl` over hand-rolled `rest.runpod.io\u002Fv1` calls for creating endpoints.**\n\n## Tool surface\n\nStructured tools, grouped by resource:\n\n- **Pods** — list, get, create, update, start, stop, restart, delete, stream logs.\n- **Serverless endpoints** — list, get, create, update, delete; list workers; list releases; stream worker logs.\n  - **Logs are no longer an MCP-only capability** — runpodctl grew `pod logs` and `serverless logs` in v2.10.0. MCP still returns already-parsed, bounded frames, which is the easier shape inside an agent; reach for the CLI when you are shell-only or want `--follow`. Job *output* streaming (`stream-job`) remains MCP-only.\n  - `create-endpoint` takes `endpointType: QUEUE` (default) or `LOAD_BALANCER` — see golden path 14. The routing type is fixed at creation; `update-endpoint` cannot change it.\n  - Read an endpoint's invoke URLs from `requestUrls` on the get\u002Flist reply instead of assembling them.\n  - To pin a specific GPU **SKU** on an existing endpoint use `set-endpoint-gpus`; `create-endpoint`\u002F`update-endpoint` expose only `gpuPoolIds` and can't express a SKU (`deploy-hub-repo` can pin one at deploy time via `gpuIds` exclusions).\n- **Jobs (serverless runtime)** — run, runsync, status, stream, cancel, retry, health, purge queue.\n- **Hub** — `list-hub-repos` (public catalog of prebuilt Serverless workers and Pod templates: vLLM, ComfyUI, …) and `deploy-hub-repo`, which deploys a repo's listed release as an endpoint — the same as clicking Deploy on the Hub.\n- **Public endpoints** — `list-public-endpoints`: managed pay-per-use model APIs (text\u002Fimage\u002Fvideo\u002Faudio) that need no deployment. Call the returned endpointId with `run-endpoint`\u002F`runsync-endpoint`.\n- **Templates** — list, get, create, update, delete.\n- **Network volumes** — list, get, create, update, delete. `create-network-volume` takes `volumeType` (`STANDARD` | `HIGH_PERFORMANCE`) and a size of 10–4096 GB; omit `volumeType` to get the data center's default tier. The tier is **immutable after creation** — `update-network-volume` can't change it.\n- **Container registry auth** — list, get, create, delete. A username + password for **any** registry; pass the resulting id as `containerRegistryAuthId` on create-pod\u002Fcreate-endpoint.\n- **ECR delegations** (`list-`\u002F`create-`\u002F`delete-registry-delegation`) — **AWS ECR only**, v2 only, and stores no credentials: you register a repository ARN and Runpod gets scoped pull access instead. Prefer it over a stored username\u002Fpassword for ECR. The reply carries a `dockerRegistryUri` — that's the image URI to deploy with.\n- **Catalog** — list\u002Fget GPU types, list\u002Fget CPU types, list\u002Fget data centers.\n- **Billing** — scoped usage\u002Fcost breakdowns (`get-billing`).\n\n> The tool list above is a map, not a contract. The server is the source of truth —\n> `\u002Fmcp` (or your client's tool list) shows exactly what the connected version exposes,\n> and each tool carries its own parameter descriptions. Check there before assuming a\n> capability exists or doesn't.\n\n> Delete tools (`delete-template`, `delete-pod`, …) can return `isError: true` with\n> \"Unexpected end of JSON input\" **even on success** — the Runpod REST API returns\n> 204 No Content. Don't treat it as failure; confirm with a follow-up `get-`\u002F`list-`\n> (a deleted resource then 404s).\n\n## Use MCP vs runpodctl\n\n- **Use runpod-mcp** when the tools are connected AND the task is infra CRUD or a\n  serverless job call the server exposes. Cap large job\u002Flog output to a file.\n- **Use runpodctl instead** for: **`send`\u002F`receive`** file transfer, **SSH** key\n  management, **`doctor`** setup, **model cache** — or any shell-only agent, or\n  when the user wants a reproducible command.\n- **Hand pod creation to runpodctl** for a **multi-GPU priority list** (MCP's v2\n  create-pod takes one GPU type; extra `gpuTypeIds` are dropped with a `_warning`\n  on success), or for a **template + CPU** pod together — `create-pod` rejects that\n  combination, since a template deploy is GPU-and-v2-only. Each alone is fine in\n  MCP: `templateId` (v2-only, `imageName` then optional, and each field you pass\n  replaces the template's whole value rather than merging) or `computeType: \"CPU\"`.\n- **Not this lane:** writing\u002Fdeploying your own Python (→ flash); downloading\n  models or building\u002Fpushing images (→ companion-clis).\n\nFor concepts (pods vs serverless, GPU selection, storage), read\n`..\u002Frunpod-usage\u002F`.\n\n## Source & docs\n\n- Server source: https:\u002F\u002Fgithub.com\u002Frunpod\u002Frunpod-mcp\n- Package (npm): https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@runpod\u002Fmcp-server\n- Hosted endpoint: https:\u002F\u002Fmcp.getrunpod.io\u002F\n- Docs: https:\u002F\u002Fdocs.runpod.io\n","# Runpod MCP\n\nThe Runpod MCP server exposes Runpod's control plane as structured tool calls,\nso an MCP-capable agent can manage infrastructure without shelling out. It is the\nsame Runpod REST API that `runpodctl` uses — pick MCP when its tools are\nconnected (typed params, structured errors, no shell quoting).\n\n**For a multi-step job, read the worked example before calling tools.** Tool calls are easy\nto issue and easy to issue in the wrong order — the verified end-to-end sequences live in\n[runpod\u002Fgolden-paths\u002FREADME.md](..\u002Frunpod\u002Fgolden-paths\u002FREADME.md) (image → template →\nendpoint, pod → volume → serverless, multi-region, autoscaling, monitoring). This skill\ncovers what each tool does; the paths cover what order to do them in and what it costs.\n\n## Connect\n\nConnect the hosted server with **your API key as a Bearer header** if you also use runpodctl\u002Fflash — that one key auths the MCP *and* the CLIs (the 80% path):\n\n```bash\nclaude mcp add --transport http runpod -s user https:\u002F\u002Fmcp.getrunpod.io\u002F \\\n  --header \"Authorization: Bearer $RUNPOD_API_KEY\"\n```\n\nPlain **OAuth** (\"Sign in with Runpod\", via `npx @runpod\u002Fmcp-server@latest add`) is MCP-only — the CLIs stay unauthed, so use it only for MCP-only work. Local **stdio** runs the server as a subprocess with your key. Those variants + the key-vs-OAuth tradeoff: **[reference\u002Fconnect.md](reference\u002Fconnect.md)**. After connecting, reconnect the client (in Claude Code, `\u002Fmcp`) so the tools load.\n\n**Verify it's live (do this before relying on MCP):** in Claude Code run `\u002Fmcp` —\n`runpod` should show **Connected**, not *Needs authentication* (if it's the latter,\nsign in there first; the bundled plugin server registers the URL but stays inert\nuntil you authenticate). Confirm a real call works by asking for `list-endpoints`.\nIf the `runpod` tools aren't present at all, the server isn't connected — (re)run the\ninstall above, or fall back to **runpodctl** for this task.\n\n**Check the server version (which REST API it drives):** the MCP `initialize` handshake\nreturns it in `serverInfo.version`. `\u002Fmcp` in Claude Code shows it, or probe the hosted\nserver directly:\n\n```bash\nprintf '%s\\n' '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2024-11-05\",\"capabilities\":{},\"clientInfo\":{\"name\":\"probe\",\"version\":\"0\"}}}' \\\n| curl -s -X POST https:\u002F\u002Fmcp.getrunpod.io\u002F -H \"Content-Type: application\u002Fjson\" \\\n    -H \"Accept: application\u002Fjson, text\u002Fevent-stream\" -H \"Authorization: Bearer $RUNPOD_API_KEY\" -d @-\n# → serverInfo.version e.g. \"3.0.0 [RUNPOD_REST_VERSION=v2]\"  (verified 2026-07-29)\n```\n\nThe MCP server drives Runpod's **REST v2** internally (`RUNPOD_REST_VERSION=v2`), so most\ntools avoid the buggy **public `rest.runpod.io\u002Fv1`** control API. Two exceptions worth\nknowing: the Hub, public-endpoint and `set-endpoint-gpus` tools go through GraphQL (so they\nwork under either REST version), and **CPU serverless endpoints are not creatable through\nMCP** — v2 has no CPU-endpoint concept at all (`create-endpoint` requires `gpuPoolIds`), so\nuse `runpodctl serverless create --compute-type CPU` for those.\n\n**Prefer MCP or `runpodctl` over hand-rolled `rest.runpod.io\u002Fv1` calls for creating endpoints.**\n\n## Tool surface\n\nStructured tools, grouped by resource:\n\n- **Pods** — list, get, create, update, start, stop, restart, delete, stream logs.\n- **Serverless endpoints** — list, get, create, update, delete; list workers; list releases; stream worker logs.\n  - **Logs are no longer an MCP-only capability** — runpodctl grew `pod logs` and `serverless logs` in v2.10.0. MCP still returns already-parsed, bounded frames, which is the easier shape inside an agent; reach for the CLI when you are shell-only or want `--follow`. Job *output* streaming (`stream-job`) remains MCP-only.\n  - `create-endpoint` takes `endpointType: QUEUE` (default) or `LOAD_BALANCER` — see golden path 14. The routing type is fixed at creation; `update-endpoint` cannot change it.\n  - Read an endpoint's invoke URLs from `requestUrls` on the get\u002Flist reply instead of assembling them.\n  - To pin a specific GPU **SKU** on an existing endpoint use `set-endpoint-gpus`; `create-endpoint`\u002F`update-endpoint` expose only `gpuPoolIds` and can't express a SKU (`deploy-hub-repo` can pin one at deploy time via `gpuIds` exclusions).\n- **Jobs (serverless runtime)** — run, runsync, status, stream, cancel, retry, health, purge queue.\n- **Hub** — `list-hub-repos` (public catalog of prebuilt Serverless workers and Pod templates: vLLM, ComfyUI, …) and `deploy-hub-repo`, which deploys a repo's listed release as an endpoint — the same as clicking Deploy on the Hub.\n- **Public endpoints** — `list-public-endpoints`: managed pay-per-use model APIs (text\u002Fimage\u002Fvideo\u002Faudio) that need no deployment. Call the returned endpointId with `run-endpoint`\u002F`runsync-endpoint`.\n- **Templates** — list, get, create, update, delete.\n- **Network volumes** — list, get, create, update, delete. `create-network-volume` takes `volumeType` (`STANDARD` | `HIGH_PERFORMANCE`) and a size of 10–4096 GB; omit `volumeType` to get the data center's default tier. The tier is **immutable after creation** — `update-network-volume` can't change it.\n- **Container registry auth** — list, get, create, delete. A username + password for **any** registry; pass the resulting id as `containerRegistryAuthId` on create-pod\u002Fcreate-endpoint.\n- **ECR delegations** (`list-`\u002F`create-`\u002F`delete-registry-delegation`) — **AWS ECR only**, v2 only, and stores no credentials: you register a repository ARN and Runpod gets scoped pull access instead. Prefer it over a stored username\u002Fpassword for ECR. The reply carries a `dockerRegistryUri` — that's the image URI to deploy with.\n- **Catalog** — list\u002Fget GPU types, list\u002Fget CPU types, list\u002Fget data centers.\n- **Billing** — scoped usage\u002Fcost breakdowns (`get-billing`).\n\n> The tool list above is a map, not a contract. The server is the source of truth —\n> `\u002Fmcp` (or your client's tool list) shows exactly what the connected version exposes,\n> and each tool carries its own parameter descriptions. Check there before assuming a\n> capability exists or doesn't.\n\n> Delete tools (`delete-template`, `delete-pod`, …) can return `isError: true` with\n> \"Unexpected end of JSON input\" **even on success** — the Runpod REST API returns\n> 204 No Content. Don't treat it as failure; confirm with a follow-up `get-`\u002F`list-`\n> (a deleted resource then 404s).\n\n## Use MCP vs runpodctl\n\n- **Use runpod-mcp** when the tools are connected AND the task is infra CRUD or a\n  serverless job call the server exposes. Cap large job\u002Flog output to a file.\n- **Use runpodctl instead** for: **`send`\u002F`receive`** file transfer, **SSH** key\n  management, **`doctor`** setup, **model cache** — or any shell-only agent, or\n  when the user wants a reproducible command.\n- **Hand pod creation to runpodctl** for a **multi-GPU priority list** (MCP's v2\n  create-pod takes one GPU type; extra `gpuTypeIds` are dropped with a `_warning`\n  on success), or for a **template + CPU** pod together — `create-pod` rejects that\n  combination, since a template deploy is GPU-and-v2-only. Each alone is fine in\n  MCP: `templateId` (v2-only, `imageName` then optional, and each field you pass\n  replaces the template's whole value rather than merging) or `computeType: \"CPU\"`.\n- **Not this lane:** writing\u002Fdeploying your own Python (→ flash); downloading\n  models or building\u002Fpushing images (→ companion-clis).\n\nFor concepts (pods vs serverless, GPU selection, storage), read\n`..\u002Frunpod-usage\u002F`.\n\n## Source & docs\n\n- Server source: https:\u002F\u002Fgithub.com\u002Frunpod\u002Frunpod-mcp\n- Package (npm): https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@runpod\u002Fmcp-server\n- Hosted endpoint: https:\u002F\u002Fmcp.getrunpod.io\u002F\n- Docs: https:\u002F\u002Fdocs.runpod.io\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":27,"compatibility":28},{"author":25,"version":26},"runpod","1.2.0","Bash(npx:*), Bash(claude:*)","Linux, macOS, Windows","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Frunpod-mcp","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":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add NeelakshSaxena\u002FVayu --skill runpod-mcp",{"tool":42,"command":43},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill runpod-mcp",{"tool":45,"command":46},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill runpod-mcp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"evals\u002Fwhen-to-use-mcp.eval.md","REFERENCE","参考文档",1045,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frunpod-mcp\u002Fevals\u002Fwhen-to-use-mcp.eval.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"reference\u002Fconnect.md",1250,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frunpod-mcp\u002Freference\u002Fconnect.md",[61,68,74,81,88,95],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"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":69,"name":25,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7ACC63SRHEA5KMCHSMZK2TC","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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"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":96,"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":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7ACBC7GHVH6T9YEAPCG2AP8","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]