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

comfyui-api-v2

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Operate a user-selected Comfy API v2 endpoint such as comfy-api-proxy using durable jobs, poll-first state, UUID assets, API-format workflow submission, targeted cancellation, safe asset retrieval, optional bearer auth, and idempotent submission practices.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep the returned job ID.

    line 21
  2. Distinctive:

    Use the job's returned output and asset links rather than inventing URL shapes where links are provided.

    line 23
  3. Distinctive:

    Keep bearer tokens and partner API keys out of project files and logs.

    line 25
  4. Distinctive:

    Use v2 multipart asset upload when v2 asset identity or proxy placement is required.

    line 38

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

Comfy API v2

Read

  • ../../references/COMFY_API_V2.md
  • ../../references/COMFYUI_SECURITY.md

Procedure

  1. Confirm the user selected a v2 endpoint or proxy surface.
  2. Probe /api/v2/health when supported.
  3. Submit API-format workflow JSON to /api/v2/jobs.
  4. Keep the returned job ID.
  5. Poll /api/v2/jobs/{id} as the source of truth.
  6. Use the job's returned output and asset links rather than inventing URL shapes where links are provided.
  7. Cancel only the selected job.
  8. Keep bearer tokens and partner API keys out of project files and logs.

Bundled command:

python scripts/comfy_api_v2.py health
python scripts/comfy_api_v2.py submit --workflow WORKFLOW.json
python scripts/comfy_api_v2.py wait JOB_ID
python scripts/comfy_api_v2.py cancel JOB_ID

Assets

Use v2 multipart asset upload when v2 asset identity or proxy placement is required. Do not use model upload to place executable content or arbitrary configuration files.

Done

The job is represented by its durable v2 ID and outputs are followed through server-provided asset records or links.

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.