gold-standards

Enforces mandatory coding standards for Kailash SDK workflows, testing, and security.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers working with the Kailash SDK often introduce inconsistent imports, improper parameter passing, mocked integration tests, and insecure patterns that cause runtime failures and maintenance issues. This Skill provides the mandatory gold standards that prevent these problems before code is committed. ## Core Features & Use Cases - Code Pattern Enforcement: Mandates absolute imports, 4-parameter workflow connections, .build() before execution, and dict-based result access. - Testing Policy: Defines the 3-tier testing strategy where mocking is prohibited in Tier 2 integration and Tier 3 E2E tests, requiring real Docker infrastructure like PostgreSQL and Redis. - Security & Documentation Standards: Requires environment variables for secrets, parameterized SQL queries, input validation, and docstrings for all public APIs. - Use Case: Before submitting a pull request for a new Kailash workflow, run through the compliance checklist to verify absolute imports, real-infrastructure tests, explicit error handling, and no hardcoded credentials. ## Quick Start Ask the AI to review my Kailash workflow code against the gold standards checklist and flag any violations.

Frequently Asked Questions about gold-standards

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

FAQPage Schema
How do I write compliant Kailash SDK workflow code?▼

Use absolute imports like from kailash.workflow.builder import WorkflowBuilder, connect nodes with the 4-parameter add_connection syntax, always call .build() before runtime.execute, and access results via the dict pattern results["node_id"]["result"].

What is the mocking policy for Kailash integration tests?▼

Mocking is allowed only in Tier 1 unit tests. Tier 2 integration and Tier 3 E2E tests must use real infrastructure such as Docker-based PostgreSQL, Redis, and mock API services, because mocks hide real connection and timing issues.

How do I create a custom node that meets the gold standard?▼

Extend the Node base class, implement get_parameters() with explicit NodeParameter declarations, implement run() rather than execute(), add type hints and docstrings, and write unit plus integration tests. The only reserved parameter name is _node_id.

Why does workflow execution fail with a TypeError in Kailash SDK?▼

The most common cause is passing the workflow object directly to runtime.execute without calling .build() first. The gold standard requires runtime.execute(workflow.build()) to produce a validated, executable workflow.

What security practices are required for Kailash workflows?▼

Never hardcode secrets; load credentials from environment variables. Use parameterized SQL queries to prevent injection, validate all user inputs, enforce authentication and authorization checks, and log sensitive operations for audit.