Agent skill · data analytics · tradermonty
drawdown-circuit-breaker
Evaluate account-level drawdown circuit breaker rules from trader-memory-core state and decide whether new trade risk is allowed today. Uses realized P&L, losing-streak cooldowns, and weekly/monthly drawdown limits without any external API.
Why this skill is useful
Adds a specialized script for evaluating drawdown circuit breaker rules based on trader memory state, which is not commonly found in public resources.
What it needs
Requires python installed locally. About 5k tokens when loaded. Last updated 2026-08-06. 2,581 stars on the source repository.
What this skill does
Drawdown Circuit Breaker Overview Evaluate whether the trader should take new trade risk today based on account-level realized P&L and recent terminal trade outcomes. This skill reads trader-memory-core thesis YAML files only. It produces a circuitbreakerdecision artifact that complements the market-side exposuredecision from exposure-coach. The circuit breaker is a recommendation and recordkeeping tool. It does not replace human judgment, and it does not enforce broker-side blocks or automated order rejection. When to Use Before screening or sizing any new swing trade candidate After a losing trade or partial trim to check whether a cooldown is active During daily planning when trader-memory-core contains recent closed or partially closed positions As a workflow gate before swing-opportunity-daily proceeds to candidate generation When reviewing whether daily, weekly, or monthly loss limits have been breached Prerequisites Python 3.9+ Local trader-memory-core thesis YAML files, usually under state/theses/ Account size in dollars No API keys or network access required Workflow Step 1: Read Trader Memory State Point the script at the thesis state directory: The script scans every th.yaml file and reads realized P&L from each thesis statushistory[] ledger entry. It does not use index.json for P&L, because the index is a lightweight lookup file and does not contain the required realized-P&L ledger. After validating each file, the script groups valid theses by the case-sensitive, whitespace-trimmed thesisid. If two or more valid files share an ID, it excludes the entire duplicate group from P&L and losing-streak calculations, reports every actual source path, and returns PARTIAL + HALTED until the duplicate state is repaired and the decision is rerun. metrics.thesesscanned counts only accepted theses with unique IDs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills tradermonty/drawdown-circuit-breaker