gold-standards

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

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Integrum-Global/new_project_template --skill gold-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gold-standards
Source: https://github.com/Integrum-Global/new_project_template/tree/main/.claude/skills/17-gold-standards
Command: npx skills add https://github.com/Integrum-Global/new_project_template --skill gold-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires kailash.

What problem does it solve?

Maintaining high code quality, security, and consistency across a team can be challenging. This Skill provides the official Kailash SDK Gold Standards, offering clear best practices for development, testing, documentation, and security, ensuring your projects meet enterprise-grade excellence.

Core Features & Use Cases

  • Code Quality: Guidelines for absolute imports, custom node development, and robust error handling.
  • Security & Testing: Standards for secure coding, comprehensive testing, and the critical "NO MOCKING" policy.
  • Workflow Design: Best practices for designing maintainable, scalable, and efficient workflows.
  • Use Case: Before a code review, use this Skill to verify your workflow adheres to all Gold Standards, from parameter passing conventions to security best practices, ensuring a smooth approval process.

Quick Start

Gold Standard: Absolute Imports

✅ CORRECT:

from kailash.workflow.builder import WorkflowBuilder

❌ WRONG:

from ..workflow.builder import WorkflowBuilder

Frequently Asked Questions about gold-standards

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

FAQPage Schema
How do I enforce code quality standards across Kailash SDK projects?

Enforce code quality standards by applying Gold Standards guidelines covering absolute imports, parameter passing conventions, error handling, and custom node development. These mandatory best practices ensure consistency and prevent bugs across all SDK projects.

What testing policies should I follow for Kailash SDK development?

Implement a 3-tier testing strategy with a critical NO MOCKING policy in Tiers 2-3. Gold Standards mandate comprehensive testing with dict-based result access and explicit parameter declarations to ensure auditable compliance and robust SDK reliability.

Why is the NO MOCKING policy important in Kailash SDK testing?

The NO MOCKING policy in Tiers 2-3 prevents false test coverage and ensures tests validate real SDK behavior. This constraint enforces genuine integration testing, catching bugs that mocks would hide and maintaining code quality across development stages.

How should I structure imports and parameters in Kailash SDK code?

Use absolute imports (e.g., `from kailash.workflow.builder import WorkflowBuilder`) and enforce 4-parameter connections with explicit parameter declarations. Gold Standards require these structural conventions to improve maintainability and enable consistent code reviews.

What security and documentation standards apply to Kailash workflow design?

Gold Standards mandate secure coding practices, comprehensive documentation, and documented design constraints for custom nodes and workflows. These requirements prevent security gaps, enable team auditing, and ensure scalable, maintainable workflow architecture.

Can I use relative imports in Kailash SDK projects?

No—Gold Standards require absolute imports exclusively. Relative imports like `from ..workflow.builder import WorkflowBuilder` violate standards and create inconsistency. Absolute imports ensure clarity, auditability, and smooth code review approval.