comfyui-runner

**Quick judgment**: A focused, lightweight skill that wraps basic lifecycle control for a local ComfyUI instance (`run`, `stop`, `status`). It is well-suited when you already have ComfyUI installed and just need a simple way to ensure it is running (or to shut it down) as part of a larger workflow. **Recommended scenarios** - Local or self-hosted setups where ComfyUI is already installed and on the system `PATH` (or co-located with the skill). - Automation/agent workflows that need to bring ComfyUI up just-in-time, verify health via `/health`, and optionally stop it afterward. - Simple monitoring or guardrail steps that check whether ComfyUI is reachable on a given host/port before attempting image generation. **Key risks & limitations** - **Environment coupling**: Assumes ComfyUI binary is installed and discoverable via `PATH` or directory; failure modes and error reporting are likely minimal. - **Platform assumptions**: Uses `curl` and likely shell-like behavior, which may not be portable across all OS environments without extra setup. - **Security considerations**: Basic auth via `COMFYUI_USER` and `COMFYUI_PASS` relies on environment variables or `.env` files; these must be handled carefully to avoid leaking credentials. - **Scope**: Only controls start/stop/status; no advanced management (logs, configuration changes, multiple instances, or graceful restart semantics).