nodes-reference

Organize Kailash workflow nodes into category-focused references with YAML frontmatter.

Updated Oct 10, 2025
One-click install
npx skills add https://github.com/FFOO6866/lead2cash --skill nodes-reference-ffoo6866
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nodes-reference
Source: https://github.com/FFOO6866/lead2cash/tree/main/.claude/skills/08-nodes-reference
Command: npx skills add https://github.com/FFOO6866/lead2cash --skill nodes-reference-ffoo6866

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of quickly discovering which Kailash workflow nodes to use for a given task, without manually searching through scattered docs.

Core Features & Use Cases

  • Node catalog by category: Browse AI, API, code execution, data processing, database, files, logic, monitoring, admin, transactions, and transforms in one place.
  • Task-to-node recommendations: Select nodes based on common goals like REST calls, CSV/JSON handling, routing, transformations, and observability.
  • Operational guardrails: Reminds you of important workflow rules to avoid common mistakes (for example, using DataFlow for database access and using string node IDs).

Quick Start

Ask to generate a workflow that fetches data from a REST endpoint, routes it by a condition, transforms the payload, and writes results to a file using the appropriate nodes.

Frequently Asked Questions about nodes-reference

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

FAQPage Schema
How do I find the right Kailash node for my workflow task?

Finding the right Kailash node is done by browsing category-focused references that map 110+ workflow nodes to typical AI, API, database, and logic routing scenarios, enabling fast task-to-node selection.

What are the guardrails for using Kailash workflow nodes correctly?

Kailash workflow node guardrails include using DataFlow for database access and string node IDs to avoid common mistakes, ensuring your workflow logic routing and data transformation follow required operational rules.

How do I select nodes for a REST API integration and data transformation workflow?

Selecting nodes for REST API integration and data transformation uses task-to-node recommendations that map workflow goals like payload handling and routing to specific API and transform nodes within the catalog.

Does this Kailash node reference cover monitoring and file I/O operations?

Yes, this Kailash node reference covers monitoring and file I/O operations by organizing relevant workflow nodes into dedicated categories for CSV/JSON handling and observability alongside logic and database operations.

When should I use DataFlow instead of direct database nodes in Kailash?

You should use DataFlow instead of direct database nodes in Kailash when performing database access operations, as specified by the operational guardrails to prevent common workflow integration mistakes.