ComfyUI TTS

PassAudited by ClawScan on May 1, 2026.

Overview

This skill appears to be a straightforward ComfyUI text-to-speech wrapper, with expected network use and optional local audio file saving that users should configure carefully.

Before installing, confirm you trust the ComfyUI host you configure, avoid sending sensitive text to unknown servers, choose output paths carefully, and keep advanced option values within the documented ranges.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If COMFYUI_HOST points to a remote or untrusted server, the text being converted to speech is shared with that server.

Why it was flagged

The script sends the TTS workflow, including the requested text, to the configured ComfyUI server over HTTP.

Skill content
COMFYUI_URL="http://${COMFYUI_HOST}:${COMFYUI_PORT}" ... -d "$PAYLOAD" "${COMFYUI_URL}/prompt"
Recommendation

Use a trusted ComfyUI instance, preferably local for sensitive text, and avoid sending private content to unknown hosts.

What this means

The skill can create or overwrite the file path chosen for audio output.

Why it was flagged

When an output path is provided, the script creates the destination directory if needed and writes the downloaded audio file there.

Skill content
if [ -n "$OUTPUT_FILE" ]; then ... mkdir -p "$OUTPUT_DIR" ... curl -s -o "$OUTPUT_FILE" "$VIEW_URL"
Recommendation

Choose a safe output location and avoid pointing the output option at important existing files.

What this means

Unusual option values could produce malformed or unintended ComfyUI workflow requests.

Why it was flagged

Several command-line option values are interpolated directly into the ComfyUI workflow JSON rather than being JSON-escaped or validated like the main text field.

Skill content
--character) CHARACTER="$2" ... "character": "${CHARACTER}" ... "model_size": "${MODEL_SIZE}" ... "top_p": ${TOP_P}
Recommendation

Use the documented option values; maintainers should validate numeric options and JSON-escape string options before building the workflow.