risk-check

Name: risk-check
Availability: InStock
Author: enesmeyzin98

Audit risk gates across runtime, experiments, operator actions, and startup flows.

Updated Apr 22, 2026

Search Tags:#automation #validation #compliance #safety #risk #paper-trading #risk-gating

Ready to run

npx skills add https://github.com/EnesMeyzin98/Meridian --skill risk-check-enesmeyzin98

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: risk-check
Source: https://github.com/EnesMeyzin98/Meridian/tree/main/agents/skills/risk-check
Command: npx skills add https://github.com/EnesMeyzin98/Meridian --skill risk-check-enesmeyzin98

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that the trading bot cannot bypass safety mechanisms by any code path, ensuring paper-only execution, hard risk gates, and strict exposure controls across runtime, experiments, and operator interactions.

Core Features & Use Cases

Verifies non-bypassable risk gates before position entry and during lifecycle.
Audits operator panel actions, experiment controls, and startup flows for safety compliance.
Provides actionable pass/fail results with concrete reasons for remediation.

Quick Start

Run this check after any configuration change to verify hard risk gates remain enforced across all flows.

Frequently Asked Questions about risk-check

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

FAQPage Schema

How do I verify risk gates and safety compliance in a paper trading bot?▼

To verify risk gates and safety compliance, run a validation check that identifies bypassed or non-enforced risk gates across runtime, experiments, and operator actions to maintain paper-only execution. It audits hard gates and exposure limits for remediation.

What is paper-only execution risk gating and when do I need it?▼

Paper-only execution risk gating ensures a trading bot cannot bypass safety mechanisms by any code path. You need it when modifying app/risk, app/execution, app/config, or operator_panel actions to verify hard risk gates remain enforced across all flows.

How do I audit operator panel actions and startup flows for safety compliance?▼

You audit operator panel actions and startup flows by applying a validation check to changes touching app/risk, app/execution, and app/config. This verifies exposure limits and isolation policies align with AGENTS.md and FINAL_SYSTEM_VISION.

Does this risk validation check hard gates before and during position lifecycle?▼

Yes, the risk validation check verifies non-bypassable risk gates before position entry and during the lifecycle. It audits experiment controls and startup flows to ensure strict exposure controls and paper-only execution are maintained.

Why does my trading bot bypass exposure limits during runtime experiments?▼

Your trading bot bypasses exposure limits during runtime experiments because non-enforced risk gates exist. Run a safety validation check to identify bypassed gates and verify isolation policies align with FINAL_SYSTEM_VISION for remediation.