runpod
The router.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-10
- Stars
- ★ 49
- Forks
- 10
01 前言 Front Matter
- name
- runpod
- metadata
- { "concepts": [ "site" ] }
- description
- The router.
02 资源文件 12
- 参考文档golden-paths/01-good.md144 B
- 参考文档golden-paths/02-bad.md94 B
- 参考文档golden-paths/03-untagged.md63 B
- 许可证LICENSE1.0 KB
- 参考文档references/analysis-framework.md4.3 KB
- 脚本scripts/mcp_client.py6.1 KB
- 脚本scripts/smartmoney.py33.5 KB
- 参考文档SOURCE.md340 B
- 参考文档tests/fixtures/smartmoney_fixture.json3.5 KB
- 脚本tests/test_smartmoney_saved_wallets.py3.2 KB
- 脚本tests/test_smartmoney.py15.1 KB
- 参考文档TRUST.auto.yaml2.0 KB
03 SKILL.md 正文
Router
04 同仓库更多 Skills
runpod-vllm
Serve a Hugging Face model with vLLM on Runpod (Hub worker-vllm queue endpoint, load-balancing endpoint on a vllm/vllm-openai image, or a Pod), sized, CUDA-pinned and verified with a real OpenAI client. Use for any "deploy/serve/test this LLM with vLLM" request or a vLLM deployment that will not boot; defer to runpod-serverless-deploy for non-vLLM engines and runpod-endpoint-ops for an endpoint that already works.
runpodctl
Runpod CLI for managing GPU/CPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send/receive, network-volume upload/download). Use for terminal/CI/scripting, SSH setup, `doctor`, or when the Runpod MCP tools are not connected; prefer runpod-mcp for structured tool calls in an MCP-enabled session.
runpod
Start here when the Runpod lane is unclear: picks the skill for a task (runpod-mcp and the journey playbooks it routes to, such as runpod-serverless-deploy, runpod-pod-deploy, runpod-pod-doctor and runpod-cost-audit; runpodctl, runpod-flash, runpod-companion-clis, runpod-usage, runpod-templates, runpod-build-template, runpod-migrate) and indexes two dozen end-to-end worked examples (golden paths). Use it before any multi-step or provisioning task, even when the lane is clear, to check for a matching golden path; for the Runpod MCP tools, runpod-mcp owns the answer contract, connection and tool rules.
runpod-usage
Explain Runpod architecture and design choices: Pods versus Serverless, GPU/VRAM, image construction, storage, networking, and workload development. For creating or improving a complete template project use runpod-build-template; execute infrastructure with runpodctl/runpod-mcp and code-first work with runpod-flash.
runpod-templates
Find, use, and troubleshoot official Runpod Pod templates, including ComfyUI workflow model metadata repair. For creating or optimizing Dockerfiles and application template projects use runpod-build-template; deploy through runpod-mcp or runpodctl.
runpod-serverless-deploy
Bring any source (a HuggingFace repo, a ComfyUI workflow, a Hub release, a custom container image, a GGUF repo, a Civitai asset, or a community template) to a proven Runpod Serverless endpoint: pick the engine for the modality and model format, size the GPU from the model's real metadata, provision, warm, prove it with one real job, and hand back the URL with what it bills. Deploys an existing source through the Runpod MCP tools; code-first Python deploys (the Flash dev loop) are out of scope. Use when the user wants a model or worker served on Runpod Serverless, whatever the modality: text generation, speech-to-text or text-to-speech, image or video generation, embeddings, document processing, or their own handler image. For an LLM served with vLLM (Hub worker-vllm, a vllm/vllm-openai image, or a vLLM Pod), defer to runpod-vllm.