gold-standards

Name: gold-standards
Availability: InStock
Author: ssssssssassssss

Enforce mandatory Kailash SDK compliance through automated checks and validators.

Updated Apr 2, 2026

Search Tags:#security #code-quality #best-practices #workflow-design #gold-standards #testing-policy

Ready to run

npx skills add https://github.com/ssssssssassssss/disease-risk-classifier --skill gold-standards-ssssssssassssss

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gold-standards
Source: https://github.com/ssssssssassssss/disease-risk-classifier/tree/main/.claude/skills/17-gold-standards
Command: npx skills add https://github.com/ssssssssassssss/disease-risk-classifier --skill gold-standards-ssssssssassssss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Gold Standards skill enforces mandatory coding, testing, and security practices across Kailash SDK projects to prevent import errors, hidden integration failures, inconsistent workflows, and credential leaks during development and releases.

Core Features & Use Cases

Compliance Enforcement: Automated checks for absolute imports, four-parameter connections, .build() usage, and result access patterns.
Testing & Infrastructure Policy: Enforces a 3-tier testing strategy and requires real infrastructure for integration and E2E tests where specified.
Security & Documentation Guidance: Validates secrets management, input validation, audit logging, and documentation/test creation (TDD-first).
Use Case: Run as a pre-commit, CI gate, or code-review checklist to audit workflows, custom nodes, and test suites for mandatory compliance.

Quick Start

Use the gold-standards skill to run a full compliance audit of your repository and produce a prioritized list of violations.

Frequently Asked Questions about gold-standards

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

FAQPage Schema

How do I enforce Kailash SDK best practices for code organization and imports?▼

You can enforce Kailash SDK best practices by running automated compliance checks that validate absolute imports, four-parameter connections, and .build() usage to prevent import errors and inconsistent workflows.

What testing strategy should I use for Kailash SDK integration and E2E tests?▼

Kailash SDK integration and E2E tests require a 3-tier testing strategy that mandates real infrastructure, ensuring hidden integration failures are caught during development and release processes.

How do I prevent credential leaks during Kailash SDK development and releases?▼

Prevent credential leaks by applying automated security validators that check secrets management, input validation, and audit logging across your Kailash SDK projects during code review and CI.

Can I use this compliance audit as a pre-commit hook or CI gate?▼

Yes, you can run the compliance audit as a pre-commit hook, CI gate, or code-review checklist to produce a prioritized list of violations across workflows, custom nodes, and test suites.

Why do my Kailash SDK workflows fail hidden integration tests?▼

Hidden integration test failures often occur when workflows bypass real infrastructure testing policies, which the 3-tier testing strategy enforces to validate actual infrastructure connections.

Do I need explicit error handling for custom node development in Kailash SDK?▼

Yes, custom node development requires explicit error handling, result access pattern validation, and documentation creation following TDD-first policies to meet mandatory compliance standards.