Comfyui Animatool
ShiroEirin/comfyui-good-anima
Route ALL Anima image generation: validate Danbooru hard anchors, form visual brief, assemble English prompts and args, then load comfyui-manager for workflow execution.
Explain an existing VibeComfy or ComfyUI workflow, ready template, recipe, scratchpad, target graph, node chain, model path, prompt path, or runtime result.
Install Explain Comfy Workflow
$ npx skills add peteromallet/VibeComfy --skill explain-comfy-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install peteromallet/VibeComfy explain-comfy-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/peteromallet/VibeComfy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/docs/agent-skill/skills/explain-comfy-workflow .claude/skills/explain-comfy-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "explain-comfy-workflow" agent skill from https://github.com/peteromallet/VibeComfy/tree/main/docs/agent-skill/skills/explain-comfy-workflow into .claude/skills/explain-comfy-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-comfy-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/peteromallet/VibeComfy/tree/main/docs/agent-skill/skills/explain-comfy-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add peteromallet/VibeComfy --skill explain-comfy-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install peteromallet/VibeComfy explain-comfy-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peteromallet/VibeComfy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/docs/agent-skill/skills/explain-comfy-workflow .agents/skills/explain-comfy-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "explain-comfy-workflow" agent skill from https://github.com/peteromallet/VibeComfy/tree/main/docs/agent-skill/skills/explain-comfy-workflow into .agents/skills/explain-comfy-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-comfy-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add peteromallet/VibeComfy --skill explain-comfy-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install peteromallet/VibeComfy explain-comfy-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peteromallet/VibeComfy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/docs/agent-skill/skills/explain-comfy-workflow .cursor/skills/explain-comfy-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "explain-comfy-workflow" agent skill from https://github.com/peteromallet/VibeComfy/tree/main/docs/agent-skill/skills/explain-comfy-workflow into .cursor/skills/explain-comfy-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-comfy-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/peteromallet/VibeComfy.git --path docs/agent-skill/skills/explain-comfy-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add peteromallet/VibeComfy --skill explain-comfy-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install peteromallet/VibeComfy explain-comfy-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peteromallet/VibeComfy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/docs/agent-skill/skills/explain-comfy-workflow .gemini/skills/explain-comfy-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "explain-comfy-workflow" agent skill from https://github.com/peteromallet/VibeComfy/tree/main/docs/agent-skill/skills/explain-comfy-workflow into .gemini/skills/explain-comfy-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-comfy-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install peteromallet/VibeComfy explain-comfy-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add peteromallet/VibeComfy --skill explain-comfy-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/peteromallet/VibeComfy.git skills-src && mkdir -p .github/skills && cp -r skills-src/docs/agent-skill/skills/explain-comfy-workflow .github/skills/explain-comfy-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "explain-comfy-workflow" agent skill from https://github.com/peteromallet/VibeComfy/tree/main/docs/agent-skill/skills/explain-comfy-workflow into .github/skills/explain-comfy-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-comfy-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add peteromallet/VibeComfy --skill explain-comfy-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install peteromallet/VibeComfy explain-comfy-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peteromallet/VibeComfy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/docs/agent-skill/skills/explain-comfy-workflow .opencode/skills/explain-comfy-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "explain-comfy-workflow" agent skill from https://github.com/peteromallet/VibeComfy/tree/main/docs/agent-skill/skills/explain-comfy-workflow into .opencode/skills/explain-comfy-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explain-comfy-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
explain-comfy-workflow- GitHub stars
- 150
- Token cost
- ~806 tokens
- SKILL.md length
- 377 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
Explain an existing VibeComfy or ComfyUI workflow, ready template, recipe, scratchpad, target graph, node chain, model path, prompt path, or runtime result.
- The user asks what a workflow does
- SKILL.md covers Fast Path, What To Answer, Boundaries and Return Shape
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Why a graph is wired a certain way
What it does
Explain Comfy Workflow is an agent skill from peteromallet/VibeComfy. Explain an existing VibeComfy or ComfyUI workflow, ready template, recipe, scratchpad, target graph, node chain, model path, prompt path, or runtime result. Use when the user asks what a workflow does, how it works, what a node or setting means, why a graph is wired a certain way, what will happen if it runs, or wants answers about a workflow without necessarily editing or executing it.
Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in AI & LLM Engineering, covering Diffusion and image models. It works with ComfyUI. The licence is MIT.
When your agent uses it
- The user asks what a workflow does
- Why a graph is wired a certain way
- What will happen if it runs
- Wants answers about a workflow without necessarily editing
Example prompts
- “/explain-comfy-workflow”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit b1429c6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Explain Comfy Workflow loads about 806 tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 377 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from peteromallet/VibeComfy at commit b1429c6, republished under its MIT licence (© peteromallet). 377 words, ~806 tokens.
Download SKILL.mdSave it as
.claude/skills/explain-comfy-workflow/SKILL.md (or your agent's skills folder).- name
- explain-comfy-workflow
- description
- Explain an existing VibeComfy or ComfyUI workflow, ready template, recipe, scratchpad, target graph, node chain, model path, prompt path, or runtime result. Use when the user asks what a workflow does, how it works, what a node or setting means, why a graph is wired a certain way, what will happen if it runs, or wants answers about a workflow without necessarily editing or executing it.
Explain Comfy Workflow
Use this for understanding, not mutation. Push toward the same VibeComfy evidence path as edit/run/debug, but stop at a clear answer unless the user asks to change or execute the graph.
Fast Path
vibecomfy inspect <workflow>
vibecomfy analyze info <workflow>If the target is raw JSON, inspect it as import evidence and use the positional-source conversion path when a Python explanation is needed:
vibecomfy import <workflow.json>
vibecomfy validate workflows/<source-stem> --jsonIf the question depends on class behavior, sockets, or widgets:
vibecomfy nodes spec <ClassType>Use search-comfy-workflows only when local evidence is not enough to explain a custom node, model family, or community workflow pattern.
What To Answer
Shape the explanation around the user's question:
- what the workflow makes
- the main data path: loaders -> conditioning -> sampler/generator -> decode/output
- important public inputs, prompts, seeds, steps, dimensions, frame/audio controls, or model choices
- custom nodes, models, and missing dependencies
- likely runtime constraints or reasons it may not run
- where the answer came from: command output, node ids, file path, metadata, or run artifact
Keep it concrete. Name exact node classes and ids when they matter. Do not invent field meanings; inspect the graph or node spec.
Boundaries
- Do not edit the workflow; hand off to
edit-comfy-workflow. - Do not run GPU work just to explain a static graph; hand off to
run-comfy-workflowonly when the user asks for execution or output proof. - Do not diagnose a failure beyond the available evidence; hand off to
debug-comfy-workflowwhen logs, validation errors, or missing assets are central. - Do not search Hivemind for every question. Start with the local graph and escalate only when semantics or precedent are missing.
Show full SKILL.md (123 more words)Show less
Return Shape
Answer in plain language with a compact evidence trail:
- target workflow or file
- short purpose summary
- main node/data path
- relevant knobs or dependencies
- uncertainties or next proof step, if any
For a vibecomfy.exec node, identify the source mode (inline function,
snapshot capsule, or installed entrypoint), the declared semantic IO, the
physical in_N/out_N mapping, bindings, result adapter, source digest,
and declared worker dependencies. Inspecting a capsule is inert; only
queue-time execution imports it. Link users to the custom Python workflow
guide when they want to edit or
export the source.
If the answer is based on a run, cite the RunResult fields or out/runs/<run_id>/metadata.json. If it is based on an edit candidate, say it is a candidate graph, not an executed result.
© peteromallet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in docs/agent-skill/skills/explain-comfy-workflow of peteromallet/VibeComfy.
Open the folder on GitHubat commit b1429c6
Compare with similar skills
Explain Comfy Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Explain Comfy Workflow this skillpeteromallet/VibeComfy | 150 | — | ~806 | Automated safety check: Pass | MIT | |
| Comfyui AnimatoolShiroEirin/comfyui-good-anima | 476 | — | ~4.6k | Automated safety check: Pass | GPL-3.0 | |
| Comfyui Agent Skill MieMieMieeeee/comfyui-agent-skill | 116 | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| Importing SubgraphsComfy-Org/workflow_templates | 1.3k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Comfyui Node Addernixified-ai/flake | 841 | — | ~806 | Automated safety check: Pass | AGPL-3.0 | |
| Managing BundlesComfy-Org/workflow_templates | 1.3k | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Comfyui Agent Skill Mie
MieMieeeee/comfyui-agent-skill
Agent skill for running registered ComfyUI workflows through a stable CLI, and for importing a user's own ComfyUI workflow into their private registry after review.
Importing Subgraphs
Comfy-Org/workflow_templates
Imports and registers subgraph blueprints into the ComfyUI workflowtemplates repository.
Comfyui Node Adder
nixified-ai/flake
Adds new custom nodes to the ComfyUI Nix project, including npins fetching, dependency resolution in package.nix, disabling impure pip installs, and verifying the Nix build.
Managing Bundles
Comfy-Org/workflow_templates
Manages template bundles, categories, and ordering in the ComfyUI template repository.
Headroom
momori777/Artemis
SmartCrusher + CCR context compression — crunch large JSON arrays, tool outputs, and search results to save tokens.
More from peteromallet/VibeComfy
All 9 skills in this repoAdd Comfy Workflow Template
peteromallet/VibeComfy
Add a durable VibeComfy ready workflow/template from a ComfyUI source workflow.
Debug Comfy Workflow
peteromallet/VibeComfy
Diagnose a VibeComfy or ComfyUI workflow that fails validation, conversion, node/model resolution, runtime execution, or output production.
Edit Comfy Workflow
peteromallet/VibeComfy
Edit an existing VibeComfy or ComfyUI workflow, ready template, recipe, scratchpad, or target graph.
Reorganise Comfy Workflow
peteromallet/VibeComfy
Reorganise an existing ComfyUI workflow layout without changing runtime behavior.
Run Comfy Workflow
peteromallet/VibeComfy
Execute an existing VibeComfy/ComfyUI workflow, ready template, recipe, or scratchpad and collect outputs.
Search Comfy Workflows
peteromallet/VibeComfy
Search for ComfyUI workflow precedents, VibeComfy ready templates, node wiring examples, Banodoco/Hivemind community workflow knowledge, and concrete graph patterns before editing or adding a…
Related
Works with
Categories
Questions about Explain Comfy Workflow
What does Explain Comfy Workflow do?
Explain an existing VibeComfy or ComfyUI workflow, ready template, recipe, scratchpad, target graph, node chain, model path, prompt path, or runtime result. Explain Comfy Workflow is an agent skill from peteromallet/VibeComfy. Explain an existing VibeComfy or ComfyUI workflow, ready template, recipe, scratchpad, target graph, node chain, model path, prompt path, or runtime result.
When should I use Explain Comfy Workflow?
Explain Comfy Workflow fits situations like: the user asks what a workflow does; why a graph is wired a certain way; what will happen if it runs; wants answers about a workflow without necessarily editing.
How do I install Explain Comfy Workflow in Claude Code?
Run `npx skills add peteromallet/VibeComfy --skill explain-comfy-workflow -a claude-code`. Or copy the skill folder (docs/agent-skill/skills/explain-comfy-workflow in peteromallet/VibeComfy) into .claude/skills/explain-comfy-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Explain Comfy Workflow in Codex?
Run `npx skills add peteromallet/VibeComfy --skill explain-comfy-workflow -a codex`. Or copy the skill folder (docs/agent-skill/skills/explain-comfy-workflow in peteromallet/VibeComfy) into .agents/skills/explain-comfy-workflow in your project. Codex loads it when a task matches its description.
Can I use Explain Comfy Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add peteromallet/VibeComfy --skill explain-comfy-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/explain-comfy-workflow, .gemini/skills/explain-comfy-workflow, .github/skills/explain-comfy-workflow and .opencode/skills/explain-comfy-workflow in your project.
What does Explain Comfy Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Explain Comfy Workflow is instructions for the agent only. Our summary lists: Python 3.
Does Explain Comfy Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Explain Comfy Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Explain Comfy Workflow use?
Explain Comfy Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Explain Comfy Workflow use?
About 806 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Explain Comfy Workflow?
Skills that share tags, products or a category with Explain Comfy Workflow: Comfyui Animatool (ShiroEirin/comfyui-good-anima, 476 stars), Comfyui Agent Skill Mie (MieMieeeee/comfyui-agent-skill, 116 stars), Importing Subgraphs (Comfy-Org/workflow_templates, 1.3k stars) and Comfyui Node Adder (nixified-ai/flake, 841 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Explain Comfy Workflow?
peteromallet (a GitHub user) maintains it in peteromallet/VibeComfy, which has 150 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 1, 2026.
Source: peteromallet/VibeComfy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.