[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CFT09Z585CEZW18ACSDGXT":3,"skill-same:01M6CFT09Z585CEZW18ACSDGXT":74},{"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":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":6,"updatedAt":60,"install":61,"resources":73},"01M6CFT09Z585CEZW18ACSDGXT","write-guide",null,"Write or change a skill, reference doc or golden path in this repo so it agrees with the concept graph and is linked to it. Use when adding or editing any SKILL.md, reference\u002F*.md or golden path, and after adding or changing a concept so the docs that cover it are updated too. Pairs with the add-concept skill, which covers the concept files themselves.","runpod\u002Frunpod-plugins-official","runpod","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F95939477?v=4","01M6CFSV7PCCKKMKEV6AM8XC7H","Runpod","01M6CFSVC1QMHFR2P1HF14EZ08",49,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Frunpod\u002Frunpod-plugins-official\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwrite-guide\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"write","guide","write guide","files","when","concept","cover","which","true","with","it","add","golden","docs","reference","use","repo","editing","doc","graph","change","2026-11-10 10:12:30",false,"---\nname: write-guide\ndescription: Write or change a skill, reference doc or golden path in this repo so it agrees with the concept graph and is linked to it. Use when adding or editing any SKILL.md, reference\u002F*.md or golden path, and after adding or changing a concept so the docs that cover it are updated too. Pairs with the add-concept skill, which covers the concept files themselves.\nmetadata:\n  internal: true\n---\n\n# Write a guide against the concept graph\n\nThis repo has two kinds of content that must agree:\n\n- **Concepts** (`plugins\u002Frunpod\u002Fskills\u002Frunpod-usage\u002Fconcepts\u002F*.yaml`) hold exact facts as\n  rules, each citing a public source. They are the source of truth for *what is true*.\n- **Guides** (every `SKILL.md`, `reference\u002F*.md` and golden path) explain, teach and\n  demonstrate. They are the source of truth for *how to do it*.\n\nA guide states facts that the concept rules support, and links to the concepts it covers.\nA concept is covered by at least one guide. `pnpm check:guides` enforces both links.\n\n## Writing or changing a guide\n\n1. **Find the concepts it touches** before writing (run these in `ontology\u002Ftools\u002F`):\n\n   ```bash\n   pnpm build:sqlite\n   pnpm query tree \"\u003Cconcept>\"      # the concept, its children and the guides that cover them\n   pnpm query search \"\u003Cquestion>\"   # the rules that answer a question\n   pnpm query concept \"\u003Cname>\"      # every rule on one concept, with evidence\n   ```\n\n2. **Write from the rules.** Every factual claim (a limit, a default, a state, what an action\n   does, what exists) must match a rule. Explain it in your own words and add the *how*: the\n   commands, order, pitfalls and verification.\n   - If the guide needs a fact that no rule has, **add the rule first** with the\n     `add-concept` skill, citing the spec, the public docs or a live probe. Then write the\n     guide.\n   - If a rule is wrong or out of date, fix the rule (and its evidence) in the same change.\n   - Never let a guide and a rule say different things. If you find a disagreement, the\n     public source decides which one changes.\n\n3. **Declare the links.**\n\n   | Guide | Where | Example |\n   |---|---|---|\n   | `SKILL.md` | `metadata.concepts` in the frontmatter | `concepts: [pod, network-volume]` |\n   | Reference doc | a `concepts:` line in frontmatter at the top | `---`\u003Cbr>`concepts: [runpod-secret]`\u003Cbr>`---` |\n   | Golden path | `lanes`, `mcp`, `concepts`, `status`, `verified` and `evals` in frontmatter, plus the matching `> **Status:**` line under the title | see `plugins\u002Frunpod\u002Fskills\u002Frunpod\u002Fgolden-paths\u002FREADME.md` |\n\n   List the concepts the guide actually explains or uses, not every word it mentions.\n   `pnpm build:bundle --suggest` lists the concepts each golden path names, as candidates.\n   A reference doc that a rule already cites as evidence is linked automatically, but list\n   its concepts anyway when it covers more than the citing rules.\n\n4. **Point to the rules** when a doc is the main explanation of a concept. End it with a short\n   \"Exact rules\" section with a Markdown link to each concept file (from a reference doc the\n   target is `..\u002Fconcepts\u002F\u003Cid>.yaml`).\n\n5. **Route it.** A new reference doc gets a row in its skill's `SKILL.md` table. A new golden\n   path gets rows in the router's table and `golden-paths\u002FREADME.md`.\n\n## After adding or changing a concept\n\n1. `pnpm check:guides` fails if the new concept has no guide. Extend an existing doc or write\n   a new one, following the steps above.\n2. Find the guides that already cover it and check they still agree with the rules:\n\n   ```bash\n   pnpm query tree \"\u003Cconcept>\"                    # guides linked to it\n   grep -rln \"\u003Cname or alias>\" ..\u002F..\u002Fplugins\u002F     # guides that mention it without a link\n   ```\n\n3. When a rule cites a skill file as evidence and you change that file, re-read the rule:\n   `grep -rn \"\u003Cpath>\" ..\u002F..\u002Fplugins\u002Frunpod\u002Fskills\u002Frunpod-usage\u002Fconcepts\u002F`.\n\n## Style\n\nFollow `plugins\u002Frunpod\u002Fskills\u002Frunpod-usage\u002Fconcepts\u002FREADME.md` → \"Writing style\" and the\nrepo conventions in `AGENTS.md`: plain present tense, \"Runpod\", code identifiers in\nbackticks, no \"currently\" or \"not yet\", and positive claims over claims that something is\nmissing (a missing capability needs the spec or docs as evidence, and CLI absence claims are\nchecked by `hooks\u002Fcheck_cli_absence_claims.py`).\n\n## Check\n\n```bash\ncd ontology\u002Ftools\npnpm format && pnpm validate --strict && pnpm check:guides && pnpm scan && pnpm test\ncd ..\u002F.. && python3 hooks\u002Fcheck_links.py && python3 hooks\u002Fcheck_runpod_branding.py\n```\n\n`check:guides` must report no errors, and the build line \"concepts with a guide\" must stay at\nevery concept.\n","# Write a guide against the concept graph\n\nThis repo has two kinds of content that must agree:\n\n- **Concepts** (`plugins\u002Frunpod\u002Fskills\u002Frunpod-usage\u002Fconcepts\u002F*.yaml`) hold exact facts as\n  rules, each citing a public source. They are the source of truth for *what is true*.\n- **Guides** (every `SKILL.md`, `reference\u002F*.md` and golden path) explain, teach and\n  demonstrate. They are the source of truth for *how to do it*.\n\nA guide states facts that the concept rules support, and links to the concepts it covers.\nA concept is covered by at least one guide. `pnpm check:guides` enforces both links.\n\n## Writing or changing a guide\n\n1. **Find the concepts it touches** before writing (run these in `ontology\u002Ftools\u002F`):\n\n   ```bash\n   pnpm build:sqlite\n   pnpm query tree \"\u003Cconcept>\"      # the concept, its children and the guides that cover them\n   pnpm query search \"\u003Cquestion>\"   # the rules that answer a question\n   pnpm query concept \"\u003Cname>\"      # every rule on one concept, with evidence\n   ```\n\n2. **Write from the rules.** Every factual claim (a limit, a default, a state, what an action\n   does, what exists) must match a rule. Explain it in your own words and add the *how*: the\n   commands, order, pitfalls and verification.\n   - If the guide needs a fact that no rule has, **add the rule first** with the\n     `add-concept` skill, citing the spec, the public docs or a live probe. Then write the\n     guide.\n   - If a rule is wrong or out of date, fix the rule (and its evidence) in the same change.\n   - Never let a guide and a rule say different things. If you find a disagreement, the\n     public source decides which one changes.\n\n3. **Declare the links.**\n\n   | Guide | Where | Example |\n   |---|---|---|\n   | `SKILL.md` | `metadata.concepts` in the frontmatter | `concepts: [pod, network-volume]` |\n   | Reference doc | a `concepts:` line in frontmatter at the top | `---`\u003Cbr>`concepts: [runpod-secret]`\u003Cbr>`---` |\n   | Golden path | `lanes`, `mcp`, `concepts`, `status`, `verified` and `evals` in frontmatter, plus the matching `> **Status:**` line under the title | see `plugins\u002Frunpod\u002Fskills\u002Frunpod\u002Fgolden-paths\u002FREADME.md` |\n\n   List the concepts the guide actually explains or uses, not every word it mentions.\n   `pnpm build:bundle --suggest` lists the concepts each golden path names, as candidates.\n   A reference doc that a rule already cites as evidence is linked automatically, but list\n   its concepts anyway when it covers more than the citing rules.\n\n4. **Point to the rules** when a doc is the main explanation of a concept. End it with a short\n   \"Exact rules\" section with a Markdown link to each concept file (from a reference doc the\n   target is `..\u002Fconcepts\u002F\u003Cid>.yaml`).\n\n5. **Route it.** A new reference doc gets a row in its skill's `SKILL.md` table. A new golden\n   path gets rows in the router's table and `golden-paths\u002FREADME.md`.\n\n## After adding or changing a concept\n\n1. `pnpm check:guides` fails if the new concept has no guide. Extend an existing doc or write\n   a new one, following the steps above.\n2. Find the guides that already cover it and check they still agree with the rules:\n\n   ```bash\n   pnpm query tree \"\u003Cconcept>\"                    # guides linked to it\n   grep -rln \"\u003Cname or alias>\" ..\u002F..\u002Fplugins\u002F     # guides that mention it without a link\n   ```\n\n3. When a rule cites a skill file as evidence and you change that file, re-read the rule:\n   `grep -rn \"\u003Cpath>\" ..\u002F..\u002Fplugins\u002Frunpod\u002Fskills\u002Frunpod-usage\u002Fconcepts\u002F`.\n\n## Style\n\nFollow `plugins\u002Frunpod\u002Fskills\u002Frunpod-usage\u002Fconcepts\u002FREADME.md` → \"Writing style\" and the\nrepo conventions in `AGENTS.md`: plain present tense, \"Runpod\", code identifiers in\nbackticks, no \"currently\" or \"not yet\", and positive claims over claims that something is\nmissing (a missing capability needs the spec or docs as evidence, and CLI absence claims are\nchecked by `hooks\u002Fcheck_cli_absence_claims.py`).\n\n## Check\n\n```bash\ncd ontology\u002Ftools\npnpm format && pnpm validate --strict && pnpm check:guides && pnpm scan && pnpm test\ncd ..\u002F.. && python3 hooks\u002Fcheck_links.py && python3 hooks\u002Fcheck_runpod_branding.py\n```\n\n`check:guides` must report no errors, and the build line \"concepts with a guide\" must stay at\nevery concept.\n",{"name":5,"metadata":50,"description":7},{"internal":51},true,"main","dbb1981a84523cc36673d1badf335a1f8f6bd496",".claude\u002Fskills\u002Fwrite-guide",10,"https:\u002F\u002Fgithub.com\u002Frunpod\u002Frunpod-plugins-official","https:\u002F\u002Fdocs.runpod.io\u002Fagent-setup.md","https:\u002F\u002Fgithub.com\u002Frunpod","https:\u002F\u002Fwww.runpod.io","2026-11-12 09:58:55",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":51},[63,66,69],{"tool":64,"command":65},"npx","npx skills add runpod\u002Frunpod-plugins-official --skill write-guide",{"tool":67,"command":68},"bunx","bunx skills add runpod\u002Frunpod-plugins-official --skill write-guide",{"tool":70,"command":71},"pnpm","pnpm dlx skills add runpod\u002Frunpod-plugins-official --skill write-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frunpod\u002Frunpod-plugins-official\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwrite-guide\u002FSKILL.md",[],[75,107,128,144,164,183],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":87,"publishedAt":45},"01M717A4HFW93XQC7PTXV1QFFH","runpod-vllm","Serve a Hugging Face model with vLLM on Runpod (Hub worker-vllm queue endpoint, load-balancing endpoint on a vllm\u002Fvllm-openai image, or a Pod), sized, CUDA-pinned and verified with a real OpenAI client. Use for any \"deploy\u002Fserve\u002Ftest 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.","https:\u002F\u002Fgithub.com\u002Frunpod\u002Frunpod-plugins-official\u002Fblob\u002Fmain\u002Fplugins\u002Frunpod\u002Fskills\u002Frunpod-vllm\u002FSKILL.md",[81,84],{"categoryNo":82,"categoryName":83,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[88,9,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106],"runpod vllm","vLLM","volume","model","worker","image","log","port","request","release","network","verified","hugging face","openai","face","endpoint","availability","load-balancing","for",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":114,"publishedAt":45},"01M6CFW2PPRQZ006AVQXGMWPH1","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, network-volume upload\u002Fdownload). Use for terminal\u002FCI\u002Fscripting, SSH setup, `doctor`, or when the Runpod MCP tools are not connected; prefer runpod-mcp for structured tool calls in an MCP-enabled session.","https:\u002F\u002Fgithub.com\u002Frunpod\u002Frunpod-plugins-official\u002Fblob\u002Fmain\u002Fplugins\u002Frunpod\u002Fskills\u002Frunpodctl\u002FSKILL.md",[113],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[109,115,91,116,117,118,119,120,90,121,122,98,9,123,124,125,103,126,127,28],"doctor","ci","MCP","Bash","cli","template","CPU","terminal","ssh setup","Tools","macos","send","windows",{"skillNo":129,"name":9,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":45},"01M6CFVTW32TE82Y5NA85H83CK","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.","https:\u002F\u002Fgithub.com\u002Frunpod\u002Frunpod-plugins-official\u002Fblob\u002Fmain\u002Fplugins\u002Frunpod\u002Fskills\u002Frunpod\u002FSKILL.md",[133],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[9,117,135,120,98,136,90,137,138,139,140,36,103,141,142,124,143,109,115,28],"migrate","start","end","companion","paths","flash","journey","audit","path",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":45},"01M6CFVK41CSZ4HM1N7TKM3WWY","runpod-usage","Explain Runpod architecture and design choices: Pods versus Serverless, GPU\u002FVRAM, image construction, storage, networking, and workload development. For creating or improving a complete template project use runpod-build-template; execute infrastructure with runpodctl\u002Frunpod-mcp and code-first work with runpod-flash.","https:\u002F\u002Fgithub.com\u002Frunpod\u002Frunpod-plugins-official\u002Fblob\u002Fmain\u002Fplugins\u002Frunpod\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[150],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[152,9,153,109,154,155,156,117,39,93,157,158,159,160,90,106,161,162,92,163],"runpod usage","usage","development","container","design","code","explain","architecture","disk","project","complete","vram",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":171,"publishedAt":45},"01M6CFVEPPADDF61NC3MC4KCE5","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.","https:\u002F\u002Fgithub.com\u002Frunpod\u002Frunpod-plugins-official\u002Fblob\u002Fmain\u002Fplugins\u002Frunpod\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[170],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[172,173,9,109,174,175,176,91,177,117,178,93,118,120,95,179,180,181,182,106],"runpod templates","templates","projects","python3","official","inventory","workflow","scripts","troubleshoot","png","repair",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":192,"publishedAt":45},"01M6PP9W1XMN6PT4J4H0XEMTKW","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\u002Fvllm-openai image, or a vLLM Pod), defer to runpod-vllm.","https:\u002F\u002Fgithub.com\u002Frunpod\u002Frunpod-plugins-official\u002Fblob\u002Fmain\u002Fplugins\u002Frunpod\u002Fskills\u002Frunpod-serverless-deploy\u002FSKILL.md",[189,190,191],{"categoryNo":82,"categoryName":83,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[193,9,194,195,196,197,198,199,90,200,201,91,202,92,117,203,204,178,93,28],"runpod serverless deploy","serverless deploy","deploy","serverless","back","Video","community","processing","scope","pick","loop","URL"]