gold-standards

Name: gold-standards
Availability: InStock
Author: aliciapls

Enforce Kailash SDK standards for imports, parameters, testing, and security.

Updated Apr 2, 2026

Search Tags:#testing #tdd #security #workflow-design #gold-standards #kailash #absolute-imports

Ready to run

npx skills add https://github.com/aliciapls/ML-Week-2---Healthcare --skill gold-standards-aliciapls

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gold-standards
Source: https://github.com/aliciapls/ML-Week-2---Healthcare/tree/main/.claude/skills/17-gold-standards
Command: npx skills add https://github.com/aliciapls/ML-Week-2---Healthcare --skill gold-standards-aliciapls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes ambiguity from Kailash SDK development by defining the mandatory standards that prevent import errors, broken workflows, hidden test failures, security mistakes, and inconsistent documentation.

Core Features & Use Cases

Absolute import rules and parameter-passing conventions that keep workflows stable and refactor-friendly.
Testing policy guidance that favors real infrastructure for integration and end-to-end validation.
Security, error handling, documentation, and custom node requirements for production-ready Kailash code. Use it when reviewing a workflow implementation, defining a custom node, planning tests, or checking code against the gold-standard checklist.

Quick Start

Ask for the Kailash gold standards for imports, parameters, testing, security, and workflow design before you implement or review code.

Frequently Asked Questions about gold-standards

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

FAQPage Schema

What are the required import and parameter conventions for Kailash SDK workflows?▼

Kailash SDK workflows require absolute import rules and specific parameter-passing conventions to keep workflows stable and refactor-friendly, preventing import errors and broken workflow execution during development.

How do I enforce testing standards for Kailash SDK integration and end-to-end tests?▼

Kailash SDK testing standards require real infrastructure for integration and end-to-end validation, favoring deterministic execution patterns and explicit validation rules over mocked dependencies to catch hidden test failures.

Does the Kailash SDK require specific security and error handling standards for production-ready code?▼

Yes, production-ready Kailash code requires explicit security measures, compliant error handling, and consistent documentation to prevent security mistakes and ensure stable runtime execution across custom nodes.

What is the best way to review a custom Kailash node against code standards before release?▼

Use the Kailash gold standards checklist to review custom nodes, verifying imports, parameters, testing policies, security requirements, and workflow design compliance before preparing code for production release.

Why do my Kailash workflows break during refactoring despite passing local tests?▼

Workflows break during refactoring when absolute import rules and deterministic execution patterns are not enforced, causing hidden failures in integration tests that rely on mocked infrastructure instead of real validation.

Can I use mocked infrastructure for Kailash SDK integration tests during development?▼

No, Kailash SDK testing policy guidance favors real infrastructure for integration and end-to-end validation, requiring deterministic execution patterns to ensure production-ready code passes explicit validation rules.