cheatsheets

Provides quick reference cheatsheets for Kailash SDK workflow patterns, nodes, and best practices.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Dchuuuuuu/disease-risk-classifier --skill cheatsheets-dchuuuuuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cheatsheets
Source: https://github.com/Dchuuuuuu/disease-risk-classifier/tree/main/.claude/skills/06-cheatsheets
Command: npx skills add https://github.com/Dchuuuuuu/disease-risk-classifier --skill cheatsheets-dchuuuuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers working with the Kailash SDK often need fast answers about node selection, cyclic workflow patterns, production deployment, and common pitfalls without reading full documentation. This Skill consolidates 42 quick reference guides into one searchable entry point. ## Core Features & Use Cases - Pattern Cheatsheets: Covers cyclic workflows, distributed transactions, saga patterns, query building, and data integration with working code examples. - Production Guidance: Includes production readiness checklists, monitoring and alerting patterns, resilience patterns, security configuration, and multi-tenancy guidance. - Mistake Prevention: Catalogs common mistakes and critical gotchas such as always calling .build() before runtime.execute() and avoiding raw SQL in favor of DataFlow. - Use Case: When building a cyclic workflow that fails to converge, consult the cycle-debugging cheatsheet to fix NameError on first iteration, wrong result.* mapping prefixes, and infinite loop conditions. ## Quick Start Ask the AI to show the Kailash cheatsheet for debugging a cyclic workflow that never converges.

Frequently Asked Questions about cheatsheets

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

FAQPage Schema
How do I fix a Kailash cyclic workflow that never converges?▼

Add debug logging nodes to track iteration progress, verify the convergence condition uses correct types (numeric comparison, not string), and ensure the cycle mapping uses the result.* prefix for PythonCodeNode outputs. Always call workflow.build() before creating the cycle.

How do I choose the right node for a Kailash workflow?▼

Use the node-selection-guide cheatsheet, which provides a decision guide for choosing between nodes like PythonCodeNode for data transformation, HTTPRequest for API calls, and LLMNode for AI tasks. It is marked as a critical reference for node selection.

Does Kailash SDK support cyclic workflows?▼

Cyclic workflows are a planned feature not yet implemented in SDK v0.9.31 according to the cycle-debugging cheatsheet. Current alternatives include Python loops, recursive workflows, or SwitchNode state machines.

How do I avoid connection exhaustion with AsyncSQL in multi-worker deployments?▼

Use external pool injection by creating one shared asyncpg pool at application startup and passing it to AsyncSQLDatabaseNode via the external_pool parameter. The SDK borrows the pool without closing it, preventing 240+ connections across Gunicorn workers.

What are the most common Kailash SDK mistakes to avoid?▼

The common-mistakes-catalog lists critical rules: never use raw SQL (use DataFlow instead), always call .build() before runtime.execute(), never use relative imports, and never mock in Tier 2-3 tests where real infrastructure is required.