gold-standards

Enforce gold-standard engineering practices for Kailash workflows, testing, and security.

Updated Oct 10, 2025
One-click install
npx skills add https://github.com/FFOO6866/lead2cash --skill gold-standards-ffoo6866
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gold-standards
Source: https://github.com/FFOO6866/lead2cash/tree/main/.claude/skills/17-gold-standards
Command: npx skills add https://github.com/FFOO6866/lead2cash --skill gold-standards-ffoo6866

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents bugs, inconsistencies, and security/testing gaps by enforcing mandatory “gold standards” for Kailash workflows, node design, imports, parameter passing, error handling, and release-critical regression coverage.

Core Features & Use Cases

  • Absolute imports & canonical workflow contracts: Enforces fully-qualified imports, the 4-parameter connection pattern, build-before-execute, and consistent result access to avoid integration drift.
  • Tiered testing compliance (NO mocking in Tiers 2–3): Ensures integration/E2E tests run against real infrastructure rather than mocks, reducing false confidence.
  • Production-grade safety & reliability: Requires explicit error handling, cleanup in finally, secure patterns (no hardcoded secrets, input validation, SQL injection prevention), and documentation that explains “WHY” with examples.
  • Use cases: Best-practice enforcement for workflow design, custom node development, security hardening, and consistent regression testing for public km.* surfaces.

Quick Start

Ask the AI to apply the gold-standards checklist to your workflow request, including import style, connection/parameter patterns, error handling, and which test tier should use real infrastructure.

Frequently Asked Questions about gold-standards

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

FAQPage Schema
How do I enforce security best practices and error handling in Kailash workflows?

Enforce security best practices and error handling in Kailash workflows by applying a mandatory gold-standards checklist requiring explicit error handling, secure coding without hardcoded secrets, and cleanup in finally blocks.

What is the canonical 4-parameter connection pattern for workflow design?

The canonical 4-parameter connection pattern is a mandatory workflow standard ensuring consistent parameter passing and result access in Kailash workflows, preventing integration drift through build-before-execute execution flow.

How do I stop using mocks for integration testing in my workflow?

To stop using mocks for integration testing, apply tiered testing compliance standards requiring Tiers 2 and 3 to run against real infrastructure, reducing false confidence in your workflow reliability.

Can I use absolute imports to prevent integration drift in custom node development?

Yes, you can use absolute imports to prevent integration drift in custom node development by enforcing fully-qualified import standards as part of your mandatory workflow engineering practices.

What's the best way to establish release-blocking regression tests for public API surfaces?

The best way to establish release-blocking regression tests for public API surfaces is to enforce tiered testing compliance with real infrastructure and document the regression expectations for public km.* surfaces.