gold-standards

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Kailash SDK development fails when teams use relative imports, mock integration tests, skip the .build() call, or hardcode secrets, causing runtime errors, hidden bugs, and security vulnerabilities. ## Core Features & Use Cases - Mandatory Code Patterns: Enforces absolute imports, 4-parameter connections, dict-based result access, and required .build() calls before workflow execution. - Testing Policy Enforcement: Defines a 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 committing a new Kailash workflow, run the compliance checklist to verify absolute imports, real-infrastructure tests, explicit error handling, and no hardcoded credentials. ## Quick Start Ask the AI to validate my Kailash workflow code against the gold standards checklist before committing.

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, and always call workflow.build() before passing it to runtime.execute. Access results via 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 Docker infrastructure such as PostgreSQL, Redis, and mock-api services, because mocks hide real connection and timing issues.

How do I create a custom node in Kailash SDK?▼

Extend the Node base class, implement get_parameters() returning NodeParameter definitions, and implement run() with type hints and docstrings. Declare all parameters explicitly for security and validation; the only reserved name is _node_id.

Why does runtime.execute fail on my Kailash workflow?▼

The most common cause is passing the workflow object directly instead of calling workflow.build() first. Other causes include missing required parameters, which raise ValueError, and incorrect 2-parameter connection syntax.

How should secrets be handled in Kailash workflows?▼

Never hardcode credentials in node configurations. Load API keys and connection strings from environment variables using os.environ, use parameterized SQL queries to prevent injection, and validate all user inputs before processing.