new-node

Create Workscript nodes using standardized templates and the single-edge return rule.

Updated Jul 10, 2025
One-click install
npx skills add https://github.com/Narcis13/workscript --skill new-node
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: new-node
Source: https://github.com/Narcis13/workscript/tree/main/.claude/skills/new-node
Command: npx skills add https://github.com/Narcis13/workscript --skill new-node

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured blueprint and templates for building new Workscript engine nodes, ensuring consistent architecture and adherence to the single-edge return rule.

Core Features & Use Cases

  • Standardized node templates (standard, boolean, lookup, multi-outcome, external-api, database) to accelerate development.
  • Clear metadata guidance, AI hints, and test scaffolding to enforce best practices across new node integration.
  • Use cases include creating core nodes, data manipulation nodes, and custom integrations with proper routing edges.

Quick Start

Provide a new node by selecting a template, implement execute() following the single-edge rule, and export the node in the index.

Frequently Asked Questions about new-node

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

FAQPage Schema
How do I build a Workscript node that follows the single-edge return rule?▼

To build a Workscript node following the single-edge return rule, select a standardized template, implement the execute() function with explicit state mutations, and export the node through the index using consistent conventions.

What Workscript node templates are available for production-ready development?▼

Available Workscript node templates include standard, boolean, lookup, multi-outcome, external API, and database operation templates, designed to cover core, data manipulation, and integration node scenarios.

How do I ensure my Workscript node is production-ready?▼

You ensure a Workscript node is production-ready by applying standardized templates, enforcing rigorous input validation, performing explicit state mutations, and adhering to consistent export conventions.

Do I need any external dependencies to create custom Workscript nodes?▼

No external dependencies are required to create custom Workscript nodes. The blueprint provides self-contained templates, metadata guidance, and test scaffolding to enforce best practices during development.

What's the best way to structure a Workscript node for external API integration?▼

The best way to structure an external API integration Workscript node is using the dedicated external-api template, which enforces input validation, explicit state mutations, and proper routing edges for reliable deployments.

Why does my Workscript node deployment fail routing validation?▼

Workscript node deployments fail routing validation when the execute() function violates the single-edge return rule or lacks explicit state mutations, preventing consistent export conventions and reliable edge mapping.