risk-config-lint

Audit risk_config.json/yaml configurations and pre-trade gating logic for engineering defects.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/paidaxing1234/latency-hunter-toolkit --skill risk-config-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: risk-config-lint
Source: https://github.com/paidaxing1234/latency-hunter-toolkit/tree/main/skills/risk-config-lint
Command: npx skills add https://github.com/paidaxing1234/latency-hunter-toolkit --skill risk-config-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Risk-config-lint audits risk_config.json/yaml configurations and pre-trade gating logic to identify engineering defects that could lead to unsafe trading, missed protections, or false sense of security in live environments.

Core Features & Use Cases

  • Pre-trade gate validation: ensures all risk limits (notional, exposure, leverage) are enforced before order submission.
  • Configuration schema validation: ensures risk_config.json/yaml has required fields and correct types.
  • Risk coverage reporting: produces a structured risk check report with fatal/high/medium items and actionable fixes.

Quick Start

Load risk_config.json and run a pre-trade gate pass to verify all limits before live trading.

Frequently Asked Questions about risk-config-lint

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

FAQPage Schema
How do I validate pre-trade risk limits in risk_config.json before live trading?

Pre-trade risk limit validation audits risk_config.json to enforce notional, exposure, and leverage limits before order submission. Run a pre-trade gate pass to verify all configurations satisfy fail-closed behavior and schema checks.

What is pre-trade gate validation for risk configurations?

Pre-trade gate validation verifies that all risk limits in risk_config.json or yaml are enforced before order submission. It identifies misconfigurations, missing gates, and post-trade vulnerabilities across multiple trading strategies.

How do I lint risk_config.yaml to find misconfigurations across multiple strategies?

Linting risk_config.yaml involves schema checks to ensure required fields and correct types exist. The audit surfaces exact file:line issues and recommended fixes for misconfigurations and missing gates across strategies.

Does pre-trade risk validation work with yaml and json risk config files?

Pre-trade risk validation applies to both risk_config.json and risk_config.yaml files. It performs schema validation, checks fail-closed behavior, and generates detailed reporting covering misconfig and post-trade vulnerabilities.

Why does my trading system need fail-closed behavior checks for risk configs?

Fail-closed behavior checks prevent unsafe trading by ensuring order-gate flows reject submissions when risk limits are missing or misconfigured. Without them, engineering defects create a false sense of security in live environments.

What is the best way to audit risk configurations for unsafe trading vulnerabilities?

Auditing risk configurations requires validating pre-trade gating logic and schema compliance. This produces a structured risk coverage report with fatal, high, and medium items alongside actionable fixes to prevent unsafe trading.