comfyui-node-inputs

Configure ComfyUI node input schemas with YAML frontmatter metadata.

Updated May 29, 2026
One-click install
npx skills add https://github.com/TurkeyC/Dotfiles --skill comfyui-node-inputs-turkeyc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comfyui-node-inputs
Source: https://github.com/TurkeyC/Dotfiles/tree/main/private_dot_copilot/skills/comfyui-custom-node-skills/skills/comfyui-node-inputs
Command: npx skills add https://github.com/TurkeyC/Dotfiles --skill comfyui-node-inputs-turkeyc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ComfyUI users often face complexity when wiring diverse input types and widget controls to nodes. This skill provides a comprehensive guide for creating nodes with INT, FLOAT, STRING, BOOLEAN, COMBO widgets, as well as optional, hidden, lazy, and force_input behaviors.

Core Features & Use Cases

  • Supports a wide range of input types: INT, FLOAT, STRING, BOOLEAN, COMBO
  • Includes optional, hidden, and lazy inputs with clear guidance
  • Demonstrates force_input and socket-based wiring for node workflows

Quick Start

Create a ComfyUI node with diverse inputs and widgets to validate wiring.

Frequently Asked Questions about comfyui-node-inputs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure ComfyUI node inputs and widgets for diverse data types?

Configuring ComfyUI node inputs involves defining a self-contained Skill Unit using frontmatter-based metadata, which lets you specify INT, FLOAT, STRING, BOOLEAN, and COMBO input schemas alongside rich usage guidance.

How do I add optional, hidden, and lazy inputs to a ComfyUI node?

Adding optional, hidden, and lazy inputs to a ComfyUI node is achieved by configuring the node input schema within your Skill Unit, enforcing a YAML frontmatter that defines these specific input behaviors and their wiring rules.

What does force_input do when wiring ComfyUI node sockets?

The force_input behavior controls socket-based wiring for ComfyUI node workflows, ensuring that specific inputs are explicitly connected rather than relying on default widget values, as defined in your node input schema.

Do I need dependencies to create a ComfyUI node with diverse inputs?

No dependencies are required to create a ComfyUI node with diverse inputs; the configuration uses a self-contained Skill Unit format relying solely on YAML frontmatter containing name and description, plus optional scripts and assets directories.

What are the limitations when defining ComfyUI node input schemas?

The primary limitation is that the YAML frontmatter must strictly contain name and description fields, and while optional directories for scripts and assets can be included, the schema focuses on standard input types without external dependencies.