agentleFS
badgidsbadgids/Story-Film-Skills/skills/comfyui-discover/SKILL.md

comfyui-discover

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Inspect a live ComfyUI server for version, hardware, feature flags, queue depth, installed node schemas, model categories, and model filenames before selecting or validating a workflow.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 4 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the Story-Film project is a child of Pi's current working directory, pass project=<project-root> to project-scoped story_comfy actions.

    line 19
  2. Distinctive:

    Use the user-supplied server URL when present.

    line 20
  3. Distinctive:

    Read system stats and features.

    line 22
  4. Very specific:

    Before building a workflow, run the bundled workflow catalog.

    line 24
  5. Very specific:

    Use /object_info through Story-Film's managed/native control layer for node schemas.

    line 26
  6. Very specific:

    use Bash, find, ls, which, locate, directory globbing, home-directory scans, or guessed personal paths to locate ComfyUI or model files.

    line 41
  7. Very specific:

    write one-off model inventory scripts or raw /models curl loops when model_inventory.py is available.

    line 45
  8. Very specific:

    search /workflow_templates, /userdata, ComfyUI saved workflows, project workflow folders, or arbitrary external paths for selectable …

    line 46
  9. Very specific:

    write one-off /object_info or /prompt parsers/loops when the bundled controller already owns live validation and execution

    line 47
  10. Distinctive:

    create mock media or download substitute models when discovery is incomplete

    line 49
  11. Distinctive:

    treat a stale saved snapshot as current capability data

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ComfyUI Discover

Read

  • ../../references/COMFYUI_OPERATIONS.md
  • ../../references/COMFYUI_NATIVE_API.md

Procedure

  1. In Pi, begin with story_comfy action=server-info. Do this before any shell, filesystem, or guessed-path attempt to locate ComfyUI.
  2. If the Story-Film project is a child of Pi's current working directory, pass project=<project-root> to project-scoped story_comfy actions. Project creation does not change Pi's working directory.
  3. Use the user-supplied server URL when present. Otherwise use the configured environment URL or loopback default.
  4. Probe the server before doing generation work.
  5. Read system stats and features.
  6. Query exact node classes or filtered node catalog only when the task needs them. In Pi use story_comfy action=node-search or action=node-info.
  7. Before building a workflow, run the bundled workflow catalog. In Pi use story_comfy action=workflow-catalog. It reads only Story-Film's comfyui_workflows/ directory: built-ins plus custom/<task>/<model>/.
  8. Query model categories and filenames only when model availability matters. In Pi use story_comfy action=model-inventory and action=model-search. The server registries include model roots registered through extra_model_paths.yaml.
  9. Use /object_info through Story-Film's managed/native control layer for node schemas. Its node input schema is under input.required and input.optional. Do not treat an empty result from an incorrectly parsed inputs field as evidence that models are missing.
  10. Save a project snapshot to 04_generation/comfyui/server_snapshot.json when reproducibility or later diagnosis benefits.

Bundled commands:

python scripts/comfyui_control.py probe
python scripts/comfyui_control.py nodes --query <term>
python scripts/comfyui_control.py models
python scripts/workflow_catalog.py catalog PROJECT --query <term>
python scripts/comfyui_control.py models --folder <category>

Do not

  • use Bash, find, ls, which, locate, directory globbing, home-directory scans, or guessed personal paths to locate ComfyUI or model files; use story_comfy and the live server registry instead
  • infer that ComfyUI is absent from a failed cd, a missing guessed directory, or a failed filesystem search
  • infer that models are absent from an empty guessed checkpoints, vae, loras, unet, or diffusion_models directory
  • invoke managed comfy-cli discovery commands directly through Bash when story_comfy can perform the operation
  • write one-off model inventory scripts or raw /models curl loops when model_inventory.py is available; use the bundled inventory tool for Story-Film model selection
  • search /workflow_templates, /userdata, ComfyUI saved workflows, project workflow folders, or arbitrary external paths for selectable workflows; custom workflow JSON must be copied into comfyui_workflows/custom/<task>/<model>/
  • write one-off /object_info or /prompt parsers/loops when the bundled controller already owns live validation and execution
  • infer that models are absent because they are outside the ComfyUI application directory
  • create mock media or download substitute models when discovery is incomplete
  • assume a custom node exists from an online workflow
  • treat a stale saved snapshot as current capability data
  • guess model filenames from model family names

Done

The next step has live evidence for the server, required node classes, and relevant models instead of assumptions.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.