core-sdk

Build and execute Kailash workflows with correct node wiring and runtime selection.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/aliciapls/ML-Week-2---Healthcare --skill core-sdk-aliciapls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core-sdk
Source: https://github.com/aliciapls/ML-Week-2---Healthcare/tree/main/.claude/skills/01-core-sdk
Command: npx skills add https://github.com/aliciapls/ML-Week-2---Healthcare --skill core-sdk-aliciapls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from building Kailash workflows by giving you the correct patterns for node creation, connections, execution, and safety checks.

Core Features & Use Cases

  • Workflow Construction: Create workflows with string-based nodes, build them correctly, and execute them through the proper runtime.
  • Data Flow and Routing: Connect nodes with the required four-parameter syntax, pass parameters reliably, and route outputs with dot notation and conditional logic.
  • Production-Ready Operations: Handle async execution, error recovery, runtime lifecycle management, MCP integration, tracing, and best-practice PythonCodeNode usage.
  • Use Case: A developer building an ETL pipeline can read source data, transform it with Python code, branch on conditions, pass runtime overrides, and run it safely in CLI, Docker, or FastAPI environments.

Quick Start

Ask me to create a basic Kailash workflow that reads data, transforms it, connects the nodes correctly, and runs it with the appropriate runtime.

Frequently Asked Questions about core-sdk

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

FAQPage Schema
How do I connect nodes in a Kailash workflow without wiring errors?

Kailash workflow connections require a four-parameter syntax to link string-based nodes reliably. Using this exact pattern prevents broken node wiring and ensures data passes correctly between nodes during execution.

When should I use LocalRuntime versus AsyncLocalRuntime for workflow execution?

Choosing between LocalRuntime and AsyncLocalRuntime depends on your execution needs. LocalRuntime handles standard synchronous runs, while AsyncLocalRuntime manages asynchronous execution for workflows requiring non-blocking operations.

How do I add conditional routing and parameter overrides to a Kailash workflow?

Kailash workflows support conditional routing using dot notation and reliable parameter passing for runtime overrides. This allows you to branch outputs dynamically and inject parameters safely during execution.

Does Kailash workflow execution support MCP integration and tracing?

Kailash workflows support MCP integration and tracing for production-ready operations. You can handle runtime lifecycle management and trace execution paths safely across CLI, Docker, or FastAPI environments.

What is the correct build-before-execute discipline for Kailash workflows?

Kailash workflows require a build-before-execute discipline where you construct string-based nodes and connections first, then call the build method, and finally execute through the proper runtime to avoid invalid runtime usage.