Przejdź do treści
Biblioteka skilli
AI i agenci · Automatyzacja

comfyui

/comfyui

Pracuje z workflow ComfyUI w automatyzacji generowania wideo: obrazy, wideo, modele, LoRA i importy workflow.

Licencja
AGPL-3.0
Ostatnia zmiana repozytorium
01.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

Brak sygnałów. Repozytorium zmienione 01.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

Co robi i kiedy

Pracuje z workflow ComfyUI w automatyzacji generowania wideo: obrazy, wideo, modele, LoRA i importy workflow.

Oryginalny opis (EN)

Use when working with ComfyUI workflows in Video Generation Automation, including comfyui_image/comfyui_video, custom workflow_json/workflow_path inputs, output_node selection, missing model setup, LoRAs, low-VRAM workflow choices, and community workflow imports.

Jak działa

  1. Server Contract
  2. Choosing a Workflow
  3. Output Node Contract
  4. Templated vs Fixed Nodes
  5. Model and LoRA Setup
  6. Provenance
  7. Failure Handling
Sekcje z nagłówków SKILL.md, w oryginale · 52 linii, 628 słów
Podgląd SKILL.md
---
name: comfyui
description: Use when working with ComfyUI workflows in Video Generation Automation, including comfyui_image/comfyui_video, custom workflow_json/workflow_path inputs, output_node selection, missing model setup, LoRAs, low-VRAM workflow choices, and community workflow imports.
---

# ComfyUI Workflows in Video Generation Automation

Use this skill before calling `comfyui_image` or `comfyui_video`, and when converting a community ComfyUI workflow into a Video Generation Automation tool call.

## Server Contract

- ComfyUI must be running before the tool can generate. The default server is `http://localhost:8188`; override it with `COMFYUI_SERVER_URL`.
- Health and hardware status come from `GET /system_stats`.
- Jobs are submitted to `POST /prompt`, completed outputs are read from `GET /history/{prompt_id}`, and artifact bytes are downloaded with `GET /view`.
- Export workflows with ComfyUI's API-format JSON, not the UI layout format. If a downloaded workflow will not submit, re-export it from ComfyUI with API format enabled.

## Choosing a Workflow

- Use bundled workflows when the requested operation matches and the local machine has the required models and VRAM.
- Use a custom `workflow_json` or `workflow_path` when the user needs a community recipe, a lower-VRAM model, a different style family, or custom nodes.
- For 8GB-12GB GPUs, prefer lower-footprint workflows such as Wan 2.1 1.3B, LTXV FP8 or quantized workflows, or Wan 2.2 GGUF/quantized community workflows. The bundled Wan 2.2 14B FP8 video workflows are a 16GB-class path, not a provider-wide floor.
- Do not promise that arbitrary custom workflows will fit a machine. The workflow, quantization, resolution, frame count, and offload settings determine the real resource envelope.

## Output Node Contract

- Custom workflows must pass `output_node`.
- Pick the node that writes the artifact, usually `SaveImage`, `SaveVideo`, `VHS_VideoCombine`, or another terminal saver node.
- Pass the node ID as a string, for example `"108"`. Do not pass the class name.
- If a workflow has multiple savers, choose the final deliverable node, not previews or intermediates.

## Templated vs Fixed Nodes

- Identify templated nodes before execution: prompt text, seed, dimensions, frame count, source image, sampler settings, and output filename prefix.
- Fixed nodes are model loaders, VAEs, text encoders, LoRA loaders, schedulers, and graph wiring. Do not mutate those unless the workflow author intended that customization.
- For community workflows, inspect each loader node and note every required model or custom node before running. Missing models should be handled through the tool's structured `missing_models` payload when available.

## Model and LoRA Setup

- Use ComfyUI Manager or the workflow author's model links when available, and respect model licenses.
- Place models in the folders expected by the loader nodes: diffusion models under `ComfyUI/models/diffusion_models/`, text encoders under `ComfyUI/models/text_encoders/`, VAEs under `ComfyUI/models/vae/`, and LoRAs under `ComfyUI/models/loras/`.
- For LoRA stacks, use `LoraLoader` or `LoraLoaderModelOnly` chains in the workflow. Record each LoRA name plus `strength_model` and `strength_clip` when applicable.
- The current ComfyUI tools do not inject LoRAs into arbitrary graphs. To use LoRAs, provide a workflow that already contains the LoRA loader chain and pass model-stack provenance.

## Provenance

- For custom workflows, provide `workflow_name` and `workflow_model` when known.
- Provide `workflow_model_stack` for reproducibility when the workflow is not bundled. Include base checkpoint or diffusion model, quantization, text encoder, VAE, LoRAs and strengths, sampler or scheduler, steps, and guidance if the workflow exposes them.
- The tools record the final workflow hash. Treat that hash plus the model stack, seed, dimensions, and prompt as the reproducibility contract.

## Failure Handling

- If the server is unavailable, surface the structured setup offer. Starting ComfyUI or setting `COMFYUI_SERVER_URL` is the first fix.
- If models are missing, read `data.missing_models[]`; each item should include the file name, role, destination hint, and download URL when Video Generation Automation knows it.
- If custom nodes are missing, ask the user to install them through ComfyUI Manager or the workflow author's documented install path, then restart ComfyUI.
- If a long render times out locally, check ComfyUI history before retrying from scratch; the server may still have completed the prompt.

Wersje

RepozytoriumWynikLicencja
Ta strona · Zulgo/video-generation-automation100AGPL-3.0
mrsandipmandal/CineForge100Apache-2.0
TerminalSkills/skills100Apache-2.0
dreamlab-ai/agentbox100AGPL-3.0
calesthio/OpenMontage100AGPL-3.0
G1Joshi/Agent-Skills100MIT
SlavaSexton/ComfyUI-Agent-Kit95Apache-2.0

Migawka bazy z 13.11.2026 · wersja paczki 733fcafe5398 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 1 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100comfyui-workflow-helper
    Buduje i dostraja przepływy ComfyUI: grafy węzłów, ładowarki modeli, sampler i scheduler, warunkowanie i ControlNet, instalacja checkpointów i LoRA oraz optymalizacja VRAM i szybkości.
  • 98ai-toolkit-trainer
    Trenuje własne LoRA za pomocą ostris AI-Toolkit dla WAN 2.2 i 2.1 oraz Z-Image: konfiguracja lokalna i RunPod, przygotowanie zbioru, kluczowe parametry i użycie w ComfyUI.
  • 100comfyui-connect
    Wysyła workflow w formacie API do serwera ComfyUI, odpytuje o wynik, pobiera pliki wyjściowe i anuluje zadania.
  • 100genai-comfyui-local
    Wysyła sprawdzony workflow API do lokalnego serwera ComfyUI i kontroluje jego wykonanie.
  • 95comfyui-media-workflows
    Składa, audytuje i uruchamia przepływy ComfyUI do obrazów, wideo i upscalingu, z kontrolą powtarzalności, pochodzenia i praw.
  • 100comfyui-graph-engineering
    Projektuje i naprawia pipeline'y ComfyUI dla obrazu, wideo, dźwięku i 3D, z jasnymi kontraktami wejść i wyjść.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.