New to Claude Skills? Learn how to install them →

Dtradermonty on GitHub

Drawdown Circuit Breaker

Free

Manage trade risks with drawdown evaluations.

Get this skill

Free · Opens the source repo

What Drawdown Circuit Breaker does

The Drawdown Circuit Breaker skill is designed to assist traders in evaluating whether they should take new trade risks based on their account's recent performance. By analyzing realized profit and loss (P&L) and recent trade outcomes, this skill provides a structured approach to risk management. It reads from the trader-memory-core thesis YAML files, ensuring that decisions are grounded in the trader's historical data without needing external APIs or network access.

This skill generates a circuit_breaker_decision artifact that complements existing trading strategies by acting as a recommendation tool rather than a replacement for human judgment. It evaluates various circuit breaker rules, including maximum daily losses, losing streak cooldowns, and weekly and monthly drawdown limits. The output informs traders whether they can proceed with new trades or if they should pause and reassess their strategies based on their recent performance.

The Drawdown Circuit Breaker is particularly useful for traders who want to implement a disciplined approach to risk management. It can be employed before entering new trades, after experiencing losses, or during daily planning sessions. The skill is flexible, allowing users to customize thresholds for drawdown limits and cooldown periods, ensuring that it can adapt to individual trading styles and risk appetites.

Ultimately, this skill serves as a safeguard against emotional decision-making in trading, providing a systematic evaluation of risk based on historical performance data. By integrating this tool into their workflow, traders can make more informed decisions and potentially improve their long-term trading outcomes.

When to use it

Use this skill before screening new trade candidates or after a losing trade to assess risk tolerance.

When not to use it

This skill is not suitable for traders who rely on real-time data from external APIs or those who prefer fully automated trading systems.

What you can build with it

Pre-Trade Evaluation

Before entering any new swing trades, use the skill to assess whether current conditions allow for new risk.

Post-Loss Assessment

After a losing trade, run the skill to determine if a cooldown period is active before making new trades.

Daily Planning

Incorporate the skill into your daily trading routine to evaluate whether recent performance meets risk thresholds.

How to install Drawdown Circuit Breaker

View source

1. Install with the skills CLI

npx skills add tradermonty/claude-trading-skills/drawdown-circuit-breaker --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by tradermonty

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 circuit_breaker_decision artifact that complements the market-side exposure_decision 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:

python3 skills/drawdown-circuit-breaker/scripts/check_circuit_breaker.py \
  --state-dir state/theses \
  --account-size 100000 \
  --output-dir reports/

The script scans every th_*.yaml file and reads realized P&L from each thesis status_history[] 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.

If the state directory is missing or is an empty directory, the skill returns TRADING_ALLOWED with data_quality: EMPTY_STATE so a new user is not blocked by the absence of history. If the configured state path exists but is not a directory, the skill fails closed as incomplete state data.

If state exists but a thesis, ledger event, or terminal result must be skipped or conflicts with another recorded value, the skill fails closed with data_quality: PARTIAL, recommendation: HALTED, and an incomplete_state_data rule. Repair the warnings and rerun before taking new risk. The one recoverable exception is a finite terminal outcome.pnl_dollars fallback for a legacy thesis with no realized-P&L ledger entry; it remains visible as PARTIAL but does not by itself override the calculated recommendation. For ACTIVE, PARTIALLY_CLOSED, CLOSED, and INVALIDATED theses, each history event must be an object with a recognized status and parseable at, and the last history status must match the thesis status. ACTIVE and PARTIALLY_CLOSED theses must also carry entry actuals; PARTIALLY_CLOSED must carry a position. Malformed, stale, or skeletal lifecycle history disqualifies terminal fallback and halts. Ledger-shaped events whose realized_pnl is missing, untyped, or non-finite also halt instead of being coerced.

Step 2: Evaluate Circuit Breaker Rules

The default rules are:

RuleDefaultTriggered StateRelease
Max daily loss2.0% of accountHALTEDNext ET weekday
Losing streak cooldown2 terminal losing thesesCOOLDOWN24 hours after latest loss exit
Weekly drawdown halt5.0% of accountHALTEDNext Monday ET
Monthly drawdown halt8.0% of accountHALTEDFirst day of next month ET

Day, week, and month boundaries use America/New_York. Date-only producer timestamps from trader-memory-core are counted on the named ET date. Set --as-of for deterministic evaluation; date-only --as-of values cover the full ET day, while timestamp values exclude future events after that time:

python3 skills/drawdown-circuit-breaker/scripts/check_circuit_breaker.py \
  --state-dir state/theses \
  --account-size 100000 \
  --as-of 2026-07-02T12:00:00-04:00 \
  --output-dir reports/

Step 3: Override Thresholds When Needed

Override individual thresholds on the CLI:

python3 skills/drawdown-circuit-breaker/scripts/check_circuit_breaker.py \
  --account-size 100000 \
  --max-daily-loss-pct 1.5 \
  --losing-streak-n 3 \
  --cooldown-hours 48 \
  --weekly-drawdown-pct 4 \
  --monthly-drawdown-pct 6

Or provide a JSON config file:

{
  "max_daily_loss_pct": 1.5,
  "losing_streak_n": 3,
  "cooldown_hours": 48,
  "weekly_drawdown_pct": 4.0,
  "monthly_drawdown_pct": 6.0
}

CLI arguments override config-file values.

Step 4: Interpret the Decision

Use the generated decision as a gate for new trade risk:

RecommendationMeaning
TRADING_ALLOWEDNo circuit breaker rule is active; new trade risk may proceed through the rest of the workflow
COOLDOWNDo not open new positions; continue managing existing positions and review the recent losses
HALTEDStop new entries because a drawdown limit is active or account-state data is incomplete; repair/rerun any data warnings before proceeding

Existing position management remains a human decision. The circuit breaker is designed to prevent new risk escalation after realized damage, not to force liquidation.

Time-based rules carry an ISO 8601 active_until. The non-time-based incomplete_state_data rule uses active_until: null; its Markdown report says the halt lasts until the state is repaired and the decision is rerun.

Output Format

The script writes circuit_breaker_decision_YYYY-MM-DD_HHMMSS.json and, unless --json-only is set, a matching markdown report.

{
  "schema_version": "1.0",
  "generated_at": "2026-07-02T16:00:00+00:00",
  "as_of_date": "2026-07-02",
  "recommendation": "COOLDOWN",
  "triggered_rules": [
    {
      "rule": "losing_streak_cooldown",
      "threshold": 2,
      "observed": 2,
      "active_until": "2026-07-02T15:30:00-04:00",
      "detail": "2 consecutive losing closes; last loss exit 2026-07-01T15:30:00-04:00."
    }
  ],
  "metrics": {
    "realized_pnl_today": 0.0,
    "realized_pnl_wtd": -250.0,
    "realized_pnl_mtd": -250.0,
    "consecutive_losses": 2,
    "last_loss_exit_at": "2026-07-01T15:30:00-04:00",
    "theses_scanned": 12
  },
  "account_size": 100000.0,
  "config": {
    "max_daily_loss_pct": 2.0,
    "losing_streak_n": 2,
    "cooldown_hours": 24.0,
    "weekly_drawdown_pct": 5.0,
    "monthly_drawdown_pct": 8.0
  },
  "data_quality": "OK",
  "warnings": [],
  "rationale": "Recent losing closes triggered a cooldown. Avoid new entries until the cooldown expires."
}

Resources

  • scripts/check_circuit_breaker.py - Main CLI and rule engine
  • references/circuit_breaker_framework.md - Rule definitions, defaults, and data-source notes
  • skills/trader-memory-core/schemas/thesis.schema.json - Source schema for thesis state

Key Principles

  1. Realized damage only - Use recorded realized P&L, not unrealized P&L or thesis-level cumulative fields for daily calculations.
  2. Survival first - A circuit breaker exists to prevent escalation after losses.
  3. Advisory, not automatic execution - The output informs the workflow gate; it does not place, cancel, or block broker orders.
  4. Fail closed on incomplete state - Empty state allows a new user to begin, but malformed, discarded, conflicting, or non-finite risk data returns PARTIAL + HALTED without crashing. A finite legacy outcome fallback is reported as recoverable PARTIAL and remains non-blocking.

Frequently asked questions about Drawdown Circuit Breaker

Similar skills