nodes-reference
Skill0 starsChanged 7 months agoApache-2.0View on GitHub
Comprehensive node reference documentation for all 110+ Kailash SDK nodes organized by category: AI, API, Code, Data, Database, File, Logic, Monitoring, Admin, Transaction, and Transform nodes. Use when asking about 'node reference', 'available nodes', 'node list', 'AI nodes', 'API nodes', 'code nodes', 'data nodes', 'database nodes', 'file nodes', 'logic nodes', 'monitoring nodes', 'transaction nodes', 'transform nodes', 'which nodes', 'node documentation', or 'node capabilities'.
In this repository37 other files it gives its agents.
- .claude/rules/agents.mdAGENTS.md
- .claude/guides/claude-code/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- core-sdkSkill
- dataflowSkill
- nexusSkill
- kaizenSkill
- kailash-mcpSkill
- cheatsheetsSkill
- development-guidesSkill
- workflow-patternsSkill
- deployment-gitSkill
- frontend-integrationSkill
- testing-strategiesSkill
- architecture-decisionsSkill
- code-templatesSkill
- enterprise-infrastructureSkill
- validation-patternsSkill
- gold-standardsSkill
- security-patternsSkill
- flutter-patternsSkill
- interactive-widgetsSkill
- enterprise-ai-uxSkill
- conversation-uxSkill
- uiux-design-principlesSkill
- value-auditSkill
- ai-interaction-patternsSkill
- eatp-referenceSkill
- coc-referenceSkill
- 29-pactSkill
- claude-code-patternsSkill
- error-troubleshootingSkill
- kailash-mlSkill
- kailash-alignSkill
- co-referenceSkill
- managementSkill
- projectSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 49
All nodes follow the canonical 4-parameter pattern from /01-core-sdk:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Kailash Nodes - Complete Reference
Comprehensive reference for all 110+ workflow nodes in Kailash SDK, organized by category.
Quick Access
- nodes-quick-index - Quick node lookup index
By Category
| Category | File | Key Nodes |
| AI & ML | nodes-ai-reference | LLMNode, AnthropicNode, OpenAINode, VisionNode, AudioNode, EmbeddingNode, OllamaNode |
| API & Integration | nodes-api-reference | HTTPRequestNode, WebhookNode, GraphQLNode |
| Code Execution | nodes-code-reference | PythonCodeNode, JavaScriptNode, BashNode |
| Data Processing | nodes-data-reference | CSVReaderNode, JSONParserNode, DataValidatorNode, FilterNode, MapNode |
| Database | nodes-database-reference | SQLQueryNode, AsyncSQLNode, DatabaseReadNode (+ DataFlow auto-generated) |
| File Operations | nodes-file-reference | FileReaderNode, FileWriterNode, FileWatcherNode, ZipNode |
| Logic & Control | nodes-logic-reference | SwitchNode, IfElseNode, LoopNode, MergeNode, SplitNode, CycleNode |
| Monitoring | nodes-monitoring-reference | LoggerNode, MetricsNode, AlertNode, HealthCheckNode |
| Admin | nodes-admin-reference | ConfigNode, SecretManagerNode, SchedulerNode, CacheNode |
| Transactions | nodes-transaction-reference | TransactionBeginNode, SagaNode, TwoPhaseCommitNode |
| Transform | nodes-transform-reference | MapperNode, AggregatorNode, EnrichNode, NormalizeNode |
Node Selection by Use Case
| Task | Recommended Node |
| Text generation | LLMNode, OpenAINode, AnthropicNode |
| Vision / Audio | VisionNode, AudioNode |
| Local LLMs | OllamaNode |
| REST APIs | HTTPRequestNode |
| Webhooks / GraphQL | WebhookNode, GraphQLNode |
| Custom Python logic | PythonCodeNode (most flexible) |
| Database CRUD | DataFlow auto-generated nodes (not raw DB nodes) |
| CSV / JSON / XML | CSVReaderNode, JSONParserNode, XMLParserNode |
| File read / write | FileReaderNode, FileWriterNode |
| Conditional routing | SwitchNode, IfElseNode |
| Loops / cycles | LoopNode, CycleNode |
| Logging / metrics | LoggerNode, MetricsNode |
Critical Node Patterns
All nodes follow the canonical 4-parameter pattern from /01-core-sdk:
workflow.add_node("PythonCodeNode", "node1", {"code": "result = input_data * 2"})
workflow.add_connection("node1", "result", "node2", "input_data")CRITICAL Gotchas
| Rule | Why |
| NEVER use raw database nodes | Use DataFlow instead |
| ALWAYS use string-based node IDs | Variables cause issues |
NEVER forget .build() | Required before execution |
Related Skills
- 01-core-sdk - Core workflow patterns
- 06-cheatsheets - Node usage patterns
- 07-development-guides - Custom node development
- 02-dataflow - Auto-generated database nodes
Support
pattern-expert- Node pattern recommendationsdataflow-specialist- DataFlow-generated nodes
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.