Skip to content
TrustedSkillsbeta
Back to all skills

Viewcomfy Api Rules

Checked
mindrally·vlatest·backend·Apache-2.0

Provides API guidance and assistance for agent workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add mindrally/skills --skill viewcomfy-api-rules -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

mindrally

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned mindrally/skills at 7682ca7771.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
7682ca7771
Manifest
viewcomfy-api-rules/SKILL.md
Scanned
1 file, 50 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides expert guidance and assistance for integrating the ViewComfy API into web applications using Python. The ViewComfy API is a serverless FastAPI service that executes custom ComfyUI workflows, and this skill helps developers understand its technical details, operational considerations (like cold starts), and best practices for implementation. It focuses on enabling integration via Python and utilizes the httpx library for making requests.

When to use it

  • When building a web application that needs to execute ComfyUI workflows programmatically.
  • If you are encountering performance issues, such as cold starts or long generation times, when using the ViewComfy API.
  • To understand and correctly handle the API's response format, including prompt IDs, status updates, and file outputs.
  • When needing to implement streaming (SSE) functionality for real-time workflow tracking.

Key capabilities

  • Expertise in Python, FastAPI integrations, and web app development related to ViewComfy API integration.
  • Guidance on handling cold start delays and variable generation times.
  • Explanation of parameter requirements, specifically that the params object cannot be empty.
  • Detailed description of the API response format (prompt_id, status, completed, execution_time_seconds, prompt, outputs).
  • Best practices for secure credential storage and error handling.

Example prompts

  • "Explain how to handle cold start delays when using the ViewComfy API."
  • "What is the structure of a typical ViewComfy API response?"
  • "How do I use the infer_with_logs endpoint for streaming workflow updates?"

Tips & gotchas

  • Be prepared for potential cold starts, especially on initial API calls.
  • Always validate parameters before sending requests to avoid unnecessary API usage and errors.
  • The params object in your request must not be empty; if it is, consider modifying the seed value instead.