Nodes/Chye ComfyUI Toolset/πŸ”€ CYH Prompt Tools | Setup
ComfyUI Node

πŸ”€ CYH Prompt Tools | Setup

The one-click scaffold for the pack's LLM prompt enhancers

By chyerΒ·Created about a year agoΒ·Updated 6 months agoΒ· 1
πŸ”€ CYH Prompt Tools | Setup
    • status
    β—„force_recreatefalseβ–Ί

    The Chye ComfyUI Toolset's prompt enhancers don't work until a folder structure exists inside the pack - templates in one directory, API keys in another. This node is the install step that creates all of it for you, writes example templates and key files, and tells you whether it worked. You run it once, and suddenly the Enhancer nodes have something to read.

    It's the setup node for the pack's prompt_tools family, and the README is explicit: run this before anything else in that family.

    What it creates

    On execution it creates, inside the pack's own directory:

    • Presets/Preprompts/ - where template .txt files live, each containing a prompt-engineering instruction block with a {prompt} placeholder.
    • Presets/api_keys/ - where your API keys go, one file per provider.
    • Three example templates - professional_photo.txt, cinematic.txt, high_detail.txt - each with a real, usable prompt-engineering prompt baked in (camera settings, lighting, composition for photo; Nolan/Villeneuve/Deakins and color palettes for cinematic; hyper-detail for high detail).
    • Three API key placeholder files (deepseek_api_key.txt, openai_api_key.txt, anthropic_api_key.txt) with instructions instead of real keys - you edit in your actual key.
    • A .gitignore that excludes the keys directory, so you don't accidentally commit secrets if the pack lives in a repo.

    It also auto-migrates any legacy preprompts/ structure from older versions of the pack, which is a thoughtful touch for upgraders.

    The one input

    force_recreate (boolean, default off). Off, it only writes files that don't already exist - your edited templates and keys are safe. On, it overwrites the example templates and key files, clobbering anything you've customized in those specific files. Leave it off unless you want a clean reset. Output is a single status string: βœ… Setup completed successfully! or ❌ Setup failed: ....

    How you actually use it

    Drop it in any workflow, run it once (or just run the pack's nodes and read the status), then:

    # find the pack folder
    cd ComfyUI/custom_nodes/Chye-ComfyUI-Toolset/Presets/api_keys
    # put your real key on its own line, comments allowed
    echo "sk-your-real-deepseek-key" > deepseek_api_key.txt
    

    Then the Enhancer nodes pick up the key from that file. It's pure file-writing - no API calls, no model downloads, nothing to configure beyond the boolean. It's the rare ComfyUI node whose whole job is setting up files.

    Install

    ComfyUI Manager (search "Chye ComfyUI Toolset"), or:

    cd ComfyUI/custom_nodes
    git clone https://github.com/chyer/Chye-ComfyUI-Toolset
    cd Chye-ComfyUI-Toolset
    pip install -r requirements.txt
    

    Restart after. Dependencies: requests (used by the enhancers), coloredlogs, plus the pack's scipy/opencv-python installs. Zip installs need .git/.cnr-id (Chye-ComfyUI-Toolset) per the README.

    Verdict

    It's an installer masquerading as a node, and that's fine - it removes the "which folders does this pack expect?" question entirely. One run, read the status string, done. Just remember force_recreate is a reset button, not a refresh button.

    Categoryprompt_tools

    Inputs (1)

    NameTypeDefaultDescription
    force_recreateBOOLEANfalseβ€”

    Outputs (1)

    NameTypeDescription
    statusSTRINGβ€”