Index of every page on this site: llms.txt
All skills
tradermonty avatar

/exposure-coach

@f95e770
Run it yourself

Generate a one-page Market Posture summary with net exposure ceiling, growth-vs-value bias, participation breadth, and new-entry-allowed vs cash-priority recommendation by integrating signals from breadth, regime, and flow analysis skills.

Use this Skill: https://skilld.dev/gh/tradermonty/claude-trading-skills/exposure-coach

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈64 tokens for metadata: the name and description. ≈2.1k when used: this file. ≈2.6k more on demand in 2 files.

Description uses 3.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈256 characters, or 3.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Exposure Coach

Overview

Exposure Coach synthesizes outputs from market-breadth-analyzer, uptrend-analyzer, macro-regime-detector, market-top-detector, ftd-detector, theme-detector, sector-analyst, and institutional-flow-tracker into a unified control-plane decision. The skill answers the solo trader's core question: "How much capital should I commit to equities right now?" before any individual stock analysis begins.

When to Use

  • Before initiating any new stock positions to determine appropriate capital commitment
  • At the start of each trading week to calibrate portfolio exposure
  • When multiple market signals conflict and a unified posture is needed
  • After significant macro or market events to reassess exposure ceiling
  • When transitioning between market regimes (broadening, concentration, contraction)

Prerequisites

  • Python 3.9+
  • FMP API key (set FMP_API_KEY environment variable) for institutional-flow-tracker data
  • Input JSON files from upstream skills (see Workflow Step 1)
  • Standard library + argparse, json, datetime

Workflow

Step 1: Gather Upstream Skill Outputs

Collect the most recent JSON outputs from integrated skills. Each file provides a specific signal dimension:

Skill Output File Pattern Signal Provided
market-breadth-analyzer breadth_*.json Advance/decline ratios, new highs/lows
uptrend-analyzer uptrend_*.json Uptrend participation percentage
macro-regime-detector regime_*.json Current regime (Concentration, Broadening, etc.)
market-top-detector top_risk_*.json Distribution day count, top probability score
ftd-detector ftd_*.json Follow-Through Day quality (market bottom confirmation)
theme-detector theme_detector_*.json or theme_*.json Active investment themes and rotation
sector-analyst sector_*.json Sector performance rankings
institutional-flow-tracker institutional_*.json Net institutional buying/selling

Step 2: Run Exposure Scoring Engine

Execute the exposure scoring script with paths to upstream outputs:

python3 skills/exposure-coach/scripts/calculate_exposure.py \
  --breadth reports/breadth_latest.json \
  --uptrend reports/uptrend_latest.json \
  --regime reports/regime_latest.json \
  --top-risk reports/top_risk_latest.json \
  --ftd reports/ftd_latest.json \
  --theme reports/theme_latest.json \
  --sector reports/sector_latest.json \
  --institutional reports/institutional_latest.json \
  --output-dir reports/

The script accepts partial inputs; missing files reduce confidence but do not block execution.

When an input declares evaluation_coverage, require valid schema 1.0 counts and verdict: complete. Partial, not-evaluable or malformed coverage is excluded as missing, with a stderr warning; never restore its score or bias manually. Legacy inputs without the block remain supported without a coverage guarantee.

Canonical macro-regime reports must include nested regime.confidence and composite.data_quality with valid integer component counts. Missing or malformed availability metadata, very_low confidence, and zero usable components are treated as missing critical input. They do not contribute a regime score or bias, and the normal missing-input haircut and confidence cap apply. Never override this degradation by manually copying the report's regime label into the exposure decision.

Theme input contract: Consume canonical report_type: theme_detector reports from themes.all once; ignore duplicate sorted groups. Require finite numeric non-boolean heat in [0,100], bullish/bearish direction, and data_quality with ok/warning status and string-list flags. The consumer maps to round(50 + mean(signed_heat)/2) (bullish positive, bearish negative; nearest integer, ties to even). This is an uncalibrated integration heuristic, not a forecast or freshness guarantee. Legacy numeric theme_score and recognized theme_strength labels remain supported; see references/exposure_framework.md.

Verification pitfall: Inspect inputs_provided, inputs_missing, inputs_unparseable and input_warnings (diagnostic fields appear only when nonempty). Omitted theme input is missing; supplied but invalid/unreadable theme input is unparsable, excluded and warned on stderr. Never fold a rejected theme into exposure manually. Upstream quality flags remain visible in JSON/Markdown/stderr. Confidence measures input completeness, not freshness, verified quality or prediction accuracy. Do not interpret eligibility or a numerical score as validation of upstream data.

Step 3: Interpret the Market Posture Summary

Review the generated posture report containing:

  1. Exposure Ceiling -- Maximum recommended equity allocation (0-100%)
  2. Bias Direction -- Growth vs Value tilt based on regime and flow
  3. Participation Assessment -- Broad (healthy) vs Narrow (fragile) market
  4. Action Recommendation -- NEW_ENTRY_ALLOWED, REDUCE_ONLY, or CASH_PRIORITY
  5. Confidence Level -- HIGH, MEDIUM, or LOW based on input completeness

Step 4: Apply Exposure Guidance

Map the posture recommendation to portfolio actions:

Recommendation Action
NEW_ENTRY_ALLOWED Proceed with stock-level analysis and new positions
REDUCE_ONLY No new entries; trim existing positions on strength
CASH_PRIORITY Raise cash aggressively; avoid all new commitments

Output Format

JSON Report

{
  "schema_version": "1.0",
  "generated_at": "2026-03-16T07:00:00Z",
  "exposure_ceiling_pct": 70,
  "bias": "GROWTH",
  "participation": "BROAD",
  "recommendation": "NEW_ENTRY_ALLOWED",
  "confidence": "HIGH",
  "component_scores": {
    "breadth_score": 65,
    "uptrend_score": 72,
    "regime_score": 80,
    "top_risk_score": 25,
    "ftd_score": 10,
    "theme_score": 68,
    "sector_score": 70,
    "institutional_score": 75
  },
  "inputs_provided": ["breadth", "uptrend", "regime", "top_risk", "ftd", "theme", "sector", "institutional"],
  "inputs_missing": [],
  "rationale": "Broad participation with low top risk supports elevated exposure."
}

Markdown Report

The markdown report provides a one-page summary suitable for quick review:

# Market Posture Summary
**Date:** 2026-03-16 | **Confidence:** HIGH

## Exposure Ceiling: 70%

| Dimension | Score | Status |
|-----------|-------|--------|
| Breadth | 65 | Healthy |
| Uptrend Participation | 72% | Broad |
| Regime | Broadening | Favorable |
| Top Risk | 25 | Low |

## Recommendation: NEW_ENTRY_ALLOWED

**Bias:** Growth > Value
**Participation:** Broad (healthy internals)

### Rationale
Broad participation with low distribution day count supports elevated equity exposure.
New positions allowed within the 70% ceiling.

Reports are saved to reports/ with filenames exposure_posture_YYYY-MM-DD_HHMMSS.{json,md}.

Resources

  • scripts/calculate_exposure.py -- Main orchestrator that scores and synthesizes inputs
  • references/exposure_framework.md -- Scoring rules and threshold definitions
  • references/regime_exposure_map.md -- Regime-to-exposure ceiling mappings

Key Principles

  1. Safety First -- Default to lower exposure when inputs are incomplete or conflicting
  2. Regime Alignment -- Let macro regime set the baseline; breadth adjusts within bounds
  3. Actionable Output -- Always produce a clear recommendation, not just data aggregation

Strict provenance for market-regime-daily

Add --require-provenance --run-id daily-20261017-unique --as-of 2026-10-17T13:00:00Z --max-age-days 3 to validate breadth and uptrend before scoring. Both producers must receive the same unique run ID; pass their exact printed JSON paths. --as-of is the timezone-aware evaluation instant, not an override of the source business date.

The gate checks schema 1.0, expected run ID, UTC retrieval no later than evaluation, nonfuture source date and configured age. Default three calendar days is a conservative policy, not an exchange holiday calendar. Failure stops before report output. Successful output records accepted lineage and verification limits. Optional top-risk/other inputs and auxiliary summary dates remain outside this gate; unknown quality flags stay false. Legacy mode retains its existing schema. Run IDs are consistency markers, not authenticity or point-in-time proof.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2d4 checks · Risk SAFE
  • Gen Agent Trust Hub3d

    The exposure-coach skill is a market analysis tool that aggregates financial data from various JSON reports to provide investment posture recommendations. It follows secure practices by using local data processing, implementing strict data validation (provenance and coverage checks), and avoiding external network requests or dynamic code execution. The use of subprocesses in test files is limited to internal verification and does not pose a risk to the operating environment.

  • Socket2d

    No alerts

  • Snyk3d

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at f95e770. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last week

README badge

README badge for tradermonty/claude-trading-skills/exposure-coach