
runpod-comfyui-models
Repair imported ComfyUI workflows with missing or broken model metadata for ComfyUI-RunpodDirect. Accept a workflow JSON or original ComfyUI output PNG, extract and inventory it, and resolve exact model artifacts. Use when a user reports a broken workflow, missing models, or failed model discovery; use companion-clis for generic Hugging Face transfers and runpod-mcp or runpodctl for Pod lifecycle.
- Installs
- 465
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/runpod/runpod-plugins-official --skill runpod-comfyui-models- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads runpod-comfyui-models automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Repair a ComfyUI workflow for RunpodDirect
Return a new UI workflow JSON containing trustworthy properties.models records that
ComfyUI-RunpodDirect can consume — never substitute a plausible model merely to make the
graph queue. Never edit, replace, or overwrite the supplied JSON or PNG. For every
recoverable UI workflow, hand off exactly one new <workflow-stem>.repaired.json — even
when resolution is incomplete, ambiguous, gated, or interrupted.
Terms — workflow vs prompt vs metadata record
| Term | What it is | Role here |
|---|---|---|
| UI workflow JSON | The graph the ComfyUI frontend exports/imports: nodes, links, widget values, properties | the only JSON this skill annotates |
API prompt JSON | The execution format POSTed to /prompt, keyed by node id | inventory evidence only — never annotate it |
properties.models record | A loader node's model metadata entry (name, url, directory, optional hash) | what a repair adds or fixes |
Annotation targets the UI format only; the API prompt has no portable model-metadata contract.
Intake
- No artifact yet → ask exactly once: “Please attach the workflow JSON or the original ComfyUI output PNG.” (Screenshots and re-encoded images usually lose the workflow.)
- Artifact present → no further intake questions: extract when needed, inventory, resolve, write the repaired copy, return it.
- No recoverable UI workflow (API-only JSON, stripped PNG) → that is the single blocker; request the original UI workflow or PNG.
Decide the path
| Observed state | Action |
|---|---|
| Every model requirement has complete metadata with no reported issues | Preserve its content unchanged, write the one new final JSON, and report that no records were added. Verify or harden only when explicitly requested or when a live failure provides evidence of a problem. |
| Exact filename but no trustworthy URL | Inventory node context, then resolve candidates from original template sources, ComfyUI-Manager, Hugging Face, or Civitai. |
| Generic filename or several credible matches | Do not apply ambiguous metadata or download. Publish the partial workflow, report its path, then show the candidates and ask the user to choose. |
| Gated or license-restricted artifact | Publish the partial workflow first, then stop before authentication/download until access and license acceptance are confirmed. |
| RunpodDirect routes unavailable | Produce the repaired workflow; keep its working manifest temporary and recommend or diagnose RunpodDirect only when the environment warrants it. |
The references
| Reference | The one question it answers |
|---|---|
| reference/resolution.md | Which exact artifact is this model? Evidence, source order, confidence policy. |
| reference/metadata.md | How is approved metadata written into the workflow? Patch rules, unsafe-URL handling, the exact handoff lines. |
| reference/runpoddirect.md | Is the live extension there, and how is it driven safely? Feature detection, download authorization, URL/redirect/secret safety. |
Low-friction contract
- inspect / check → read-only work.
- find / repair / fix → also write the new repaired copy.
- download / make it work on this Pod → also download verified public unchanged tuples.
- run / test end to end → plus one controlled smoke test.
Never reconfirm a step the opening intent already covered. Ask once, and only for a material decision: ambiguity, gated access or a license, an install or restart, a cost/storage choice, or an action beyond the opening request. If no decision remains, finish the authorized work and report once — an optional next step is not a question.
Workflow
- Extract (PNG input only):
python3 -B extract_png_workflow.pypulls the embedded UIworkflowfrom a ComfyUI output PNG into the task's temporary directory. - Inventory:
python3 -B inventory_workflow_models.pylists every loader selection, subgraphs included — evidence, never an identity decision. - Resolve each identity per reference/resolution.md,
stopping at the first
verifiedpublisher artifact; keep the review manifest temporary. - Apply:
python3 -B apply_model_metadata.py --allow-unresolvedwrites the new workflow every time, even when nothing could be resolved; patch rules, unsafe-URL handling, and the publish contract live in reference/metadata.md. - Live checks (only within the request's scope): one batched read-only probe of the
pod's RunpodDirect routes —
curlis fine, batched rather than a visible sequence — then downloads only as authorized, per reference/runpoddirect.md.
Consult --help only after a usage error. Working state (extracted JSON, inventory,
manifest) lives in one task-specific temporary directory, deleted after the repaired
JSON validates; the repaired JSON is the only persistent artifact. Hand off in plain
language — the exact lines are in reference/metadata.md.
Routing onward
| The task is actually… | Send it to |
|---|---|
| Provision a pod for the workflow | golden path 02 (index: golden paths), then runpod-mcp or runpodctl |
| Model repo and file already known exactly | companion-clis |
| A template pod won't boot, or models are missing on a template pod | runpod-templates |
| Install or understand RunpodDirect itself | reference/runpoddirect.md |
FAQ
What does the runpod-comfyui-models skill do?
Repair imported ComfyUI workflows with missing or broken model metadata for ComfyUI-RunpodDirect. Accept a workflow JSON or original ComfyUI output PNG, extract and inventory it, and resolve exact model artifacts. Use when a user reports a broken workflow, missing models, or failed model discovery; use companion-clis for generic Hugging Face transfers and runpod-mcp or runpodctl for Pod lifecycle.
How do I install runpod-comfyui-models?
Run npx skills add https://github.com/runpod/runpod-plugins-official --skill runpod-comfyui-models in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/runpod-comfyui-models/ (personal) or .claude/skills/runpod-comfyui-models/ (project).
Which AI agents can use runpod-comfyui-models?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is runpod-comfyui-models safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains runpod-comfyui-models?
It is published by runpod in runpod/runpod-plugins-official. It has 465 recorded installs.
More from runpod/runpod-plugins-official
runpodctl
runpod/runpod-plugins-official
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). 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.
flash
runpod/runpod-plugins-official
Write and deploy code-first Runpod Serverless with runpod-flash: @Endpoint/@remote, flash dev, resource configuration, and debugging. Use runpod-build-template for explicit Dockerfile/template project authoring, and runpodctl/runpod-mcp for infrastructure management.
companion-clis
runpod/runpod-plugins-official
Companion CLIs for Runpod workflows — HuggingFace, GitHub, Docker, and AWS. Use runpod-build-template for complete template project authoring, and the ComfyUI model-repair guide in runpod-templates for imported workflows lacking model download metadata.
runpod
runpod/runpod-plugins-official
Start here for any Runpod task — running GPU/CPU 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-build-template, 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.
runpod-usage
runpod/runpod-plugins-official
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 flash.
runpod-mcp
runpod/runpod-plugins-official
Manage Runpod infrastructure through the connected Runpod MCP server's tool calls (pods, serverless endpoints and jobs, templates, network volumes, registry credentials, secrets, clusters, the GPU/CPU catalog, and billing), and connect the server when it is missing (hosted or local npx). Load it before the first Runpod MCP tool call of a request: it routes the task to the journey skill that carries the procedure, owns the answer contract and the rules on which resources you may change, and defers to runpodctl for the terminal, file transfer, and SSH setup; template project and Hub listing authoring routes to runpod-build-template.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available