agentleFS
badgidsbadgids/Story-Film-Skills/skills/generation-model-setup/SKILL.md

generation-model-setup

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Compatibility redirect for pre-v0.0.31 projects. Story-Film generation is workflow-first; use generation-workflow-setup to select complete ComfyUI workflows instead of asking the user to assemble model/resource stacks.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not ask the user to choose adapters, checkpoints, diffusion models, VAEs, text encoders, LoRAs, audio models, upscalers, or …

    line 17
  2. Very specific:

    Do not use ask_user_question or another four-option TUI picker for generation configuration.

    line 18
  3. Distinctive:

    Treat the concrete resource names stored in the selected workflow as part of that workflow choice.

    line 22

≈ “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

Generation Model Setup

Direct interactive model/resource selection was retired in v0.0.31.

Current behavior

  1. Read ../../references/WORKFLOW_SELECTION.md.
  2. Read ../generation-workflow-setup/SKILL.md.
  3. Do not ask the user to choose adapters, checkpoints, diffusion models, VAEs, text encoders, LoRAs, audio models, upscalers, or frame-interpolation models one at a time.
  4. Do not use ask_user_question or another four-option TUI picker for generation configuration.
  5. Build the complete relevant workflow catalog and show it as an ordinary numbered list.
  6. Let the user select the complete workflow by number.
  7. Record the workflow in 00_project/workflow_preferences.json.
  8. Treat the concrete resource names stored in the selected workflow as part of that workflow choice.
  9. Validate the selected workflow against the active ComfyUI server before execution.

Legacy data

00_project/model_preferences.json, scripts/model_inventory.py, and scripts/model_preferences.py can still be used to inspect or migrate older projects and for low-level diagnostics.

They must not override a workflow selected through generation-workflow-setup.

Done

This compatibility skill is done when control has moved to generation-workflow-setup.

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.