Verified:GitHub

new-node

Scaffold backend and frontend workflow nodes with Pydantic models and NodeMetadata.

1|1|Updated May 13, 2026

Search Tags:#workflow automation #pydantic #scaffold #LLM tooling #node development #frontend registry #type-safe metadata

Ready to run

npx skills add https://github.com/bibektimilsina00/fuse_monorepo --skill new-node-bibektimilsina00

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: new-node
Source: https://github.com/bibektimilsina00/fuse_monorepo/tree/main/.agents/skills/new-node
Command: npx skills add https://github.com/bibektimilsina00/fuse_monorepo --skill new-node-bibektimilsina00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the repetitive, error-prone setup work of creating new workflow nodes by generating the exact backend and frontend files Fuse needs for auto-discovery.

Core Features & Use Cases

Full node scaffolding: Creates a backend BaseNode subclass with a Pydantic properties model plus NodeMetadata and an execute stub.
Frontend registry-ready definition: Produces the corresponding NodeDefinition in the node-definitions package.
Discovery-safe structure: Ensures the generated file paths, types, and exported registry integration follow the project’s conventions so the node appears in the UI.

Quick Start

Run the new-node skill and answer the prompts to generate a backend node and a frontend node definition that Fuse can automatically discover.

Frequently Asked Questions about new-node

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

FAQPage Schema

How do I scaffold a new workflow node with backend and frontend registration?▼

Scaffolding a workflow node requires creating a backend BaseNode subclass with a Pydantic properties model and an execute stub, plus a matching frontend NodeDefinition for UI auto-discovery.

What files are needed to add a new node type to an agentic workflow system?▼

Adding a node type requires backend files (BaseNode subclass, Pydantic properties model, NodeMetadata) and a frontend NodeDefinition file, all placed in the repository's exact auto-discovery directory structure.

How do I define type-safe configurable properties for a workflow node?▼

You define type-safe configurable properties by implementing a Pydantic model within the backend BaseNode subclass, ensuring validated inputs for the node's execution logic.

Can I add custom error-handling handles and credential types to a workflow node?▼

Yes, scaffolding a new workflow node supports defining optional credential types and optional error-handling handles across both backend execution and frontend UI registration.

Why is my new workflow node not appearing in the frontend UI registry?▼

A new workflow node fails to appear when generated file paths, types, and exported registry integration do not follow the project's required auto-discovery directory conventions.