Live survey304 models · 14 providers · 23,592 auditsAudited implement · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

ibd-distribution-day-monitor

skill · tradermonty/claude-trading-skillsMIT licenceAudited 14 Nov 2026 · source d78aeaaa7b03

★ 4,270pushed today
✓SAFEGrade B · 89/100 · 14 Nov 2026 · d78aeaa
4,270repo stars · whole tradermonty/claude-trading-skills

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit d78aeaaa7b03 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Detect IBD-style Distribution Days for QQQ/SPY (close down at least 0.2% on higher volume), track 25-session expiration and 5% invalidation, count d5/d15/d25 clusters, classify market risk (NORMAL/CAUTION/HIGH/SEVERE),…

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “ibd-distribution-day-monitor (tradermonty/claude-trading-skills)”. Retrieved 14 Nov 2026. https://modelsatlas.com/skills/tradermonty/ibd-distribution-day-monitor

Trust audit

Audit 0.4.1 · source read 14 Nov 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium2 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 17,406 of 18,389 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesNot pinnedSome versions float
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS1
L1 Static sourceSecrets, path traversal, supply chain, hidden codePASS1
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (2)

LOWSupply chainsupply.unpinned · requirements.txt
F-08 Supply chainCWE-829 · CWE-1357Layer L1
PyYAML, requests
Why
2 requirement(s) not pinned with ==
Fix
pin exact versions

Audit 0.4.1 · source sha d78aeaaa7b03 · 14 Nov 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • Publishertradermonty GitHub userOwner of the repository this skill is read from
  • Source foldertradermonty/claude-trading-skills/skills/ibd-distribution-day-monitorThe exact folder we audited
  • LicenceMITAs the repository states it
  • Commit pinned for this verdictd78aeaaa7b03A new audit runs when the source changes
  • Repository statusNot archivedPushed today
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its description: Detect IBD-style Distribution Days for QQQ/SPY (close down at least 0.2% on higher volume), track 25-session expiration and 5% invalidation, count d5/d15/d25 clusters, classify market risk (NORMAL/CAUTION/HIGH/SEVERE),…

---
name: ibd-distribution-day-monitor
description: Detect IBD-style Distribution Days for QQQ/SPY (close down at least 0.2% on higher volume), track 25-session expiration and 5% invalidation, count d5/d15/d25 clusters, classify market risk (NORMAL/CAUTION/HIGH/SEVERE), and emit TQQQ/QQQ exposure recommendations. Use after market close, before TQQQ exposure changes, or as input to FTD/market-state frameworks. Does not execute trades.
---

# IBD Distribution Day Monitor

## Purpose
Detect IBD-style Distribution Days for major market ETFs (QQQ as Nasdaq proxy, SPY as S&P 500 proxy) and produce a daily market deterioration signal plus a TQQQ/QQQ exposure recommendation. Designed for post-market review.

## When to Use
Invoke this skill:
- Daily after the US market close.
- Before increasing TQQQ exposure or rebalancing leveraged positions.
- When evaluating whether an uptrend is becoming vulnerable to a correction.
- As an upstream input to FTD (Follow-Through Day) detection or other market-state frameworks.

Do NOT use this skill to:
- Execute trades or modify orders.
- Generate discretionary market predictions outside of the IBD ruleset.

## Prerequisites

- **FMP API key:** Required. Pass `--api-key`, set `config.data.api_key`, or set the `FMP_API_KEY` environment variable, in that priority order.
- **Other API keys:** None used.
- **Python:** 3.9+ with `PyYAML>=6.0` and `requests>=2.31.0` (see `requirements.txt`).

## Inputs
- Symbols (default: QQQ, SPY) and lookback (default 80 trading sessions).
- Optional `--as-of YYYY-MM-DD` for backtesting against a historical session.
- Strategy context: instrument (TQQQ or QQQ), current exposure %, base trailing stop %.
- FMP API key via `--api-key`, `config.data.api_key`, or `FMP_API_KEY` env var (in that priority order).

## Core Rules
A Distribution Day is detected when:
1. Today's close is at least 0.2% below yesterday's close.
2. Today's volume is greater than yesterday's volume.

A Distribution Day is removed from the active count when either:
- More than 25 trading sessions have elapsed since the DD.
- The index has gained 5% from the DD close (using post-DD high by default; configurable to close-source).

Today's DD is never invalidated immediately because there are no post-DD sessions to evaluate the 5% gain against.

## Counting Conventions
- `d5_count` / `d15_count` / `d25_count` count active records with `age_sessions <= N`.
- This means **N+1 sessions** are inspected (age 0..N inclusive). Reports therefore say "within N elapsed sessions" rather than "直近 N 取引日" to avoid ambiguity.

## Risk Classification
| Risk | Trigger |
|------|---------|
| NORMAL | `d25 <= 2` |
| CAUTION | `d25 >= 3` |
| HIGH | `d25 >= 5` OR `d15 >= 3` OR `d5 >= 2` |
| SEVERE | `d25 >= 6` OR `d15 >= 4` OR (`market_below_21ema_or_50ma` AND `d25 >= 5`) |

When both QQQ and SPY are loaded, QQQ-weighted overall logic applies (TQQQ-aware): a single SEVERE escalates to SEVERE; QQQ HIGH escalates to overall HIGH; QQQ NORMAL + SPY HIGH still escalates to HIGH (broad-market spillover).

## TQQQ Exposure Policy
| Risk | Action | Target Exposure | Trailing Stop |
|------|--------|-----------------|---------------|
| NORMAL | HOLD_OR_FOLLOW_BASE_STRATEGY | 100% | base |
| CAUTION | AVOID_NEW_ADDS | 75% | min(base, 7%) |
| HIGH | REDUCE_EXPOSURE | 50% | min(base, 5%) |
| SEVERE | CLOSE_TQQQ_OR_HEDGE | 25% | min(base, 3%) |

QQQ uses a less aggressive policy (HIGH=75%, SEVERE=50%) since it lacks 3x leverage.

## Workflow
1. Load OHLCV for the configured symbols via FMP (`get_historical_prices`).
2. Validate data quality; record skipped sessions in audit.
3. Rebase via `prepare_effective_history` so `effective_history[0]` is the evaluation session.
4. Detect raw Distribution Days; enrich with `high_since`, invalidation event, and status.
5. Count `d5` / `d15` / `d25` active records.
6. Compute 21EMA and 50SMA filters; flag `market_below_21ema_or_50ma` (None if data insufficient).
7. Classify each index, then combine using QQQ-weighted policy.
8. Generate portfolio action for the configured instrument.
9. Write JSON + Markdown reports to `--output-dir` with API keys redacted.

## Outputs
Saved to `reports/` (or `--output-dir`):
- `ibd_distribution_day_monitor_YYYY-MM-DD_HHMMSS.json`
- `ibd_distribution_day_monitor_YYYY-MM-DD_HHMMSS.md`

JSON is UTF-8 with `ensure_ascii=False` (Japanese explanations preserved). Sensitive keys (`api_key`, `fmp_api_key`, `token`, etc.) are redacted automatically.

## Operating Principles
- Do not override the IBD rule definitions unless `config/default.yaml` is changed deliberately.
- Always explain which dates contributed to the active count.
- Treat missing or unreliable volume data as a warning (audit_flag), not as a Distribution Day.
- Do not place trades. The portfolio action is a risk-management suggestion, not an execution instruction.

## CLI
```bash
python3 skills/ibd-distribution-day-monitor/scripts/ibd_monitor.py \
  --symbols QQQ,SPY \
  --lookback-days 80 \
  --instrument TQQQ \
  --current-exposure 100 \
  --base-trailing-stop 10 \
  --output-dir reports/
```

## API Requirements
FMP API key required. Free tier (250 calls/day) is sufficient for daily QQQ + SPY runs.

## Related Skills
- `ftd-detector`: Bottom confirmation via Follow-Through Days (counterpart of this top-side signal).
- `market-top-detector`: Composite 0-100 top probability score using O'Neil distribution + other components.
- `position-sizer`: Convert risk-management recommendations into share counts.

Excerpt, first 5,523 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit d78aeaa

Download folder ↗
git clone https://github.com/tradermonty/claude-trading-skills
git -C claude-trading-skills checkout d78aeaaa7b03

The author documents no install command, so this uses the repository directly. Our verdict covers commit d78aeaaa7b03 only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source d78aeaaa7b03

README badge

For maintainers · shows the latest audit

ModelsAtlas: SAFE BMODELSATLASSAFE · B
[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/tradermonty/ibd-distribution-day-monitor/badge.svg)](https://modelsatlas.com/skills/tradermonty/ibd-distribution-day-monitor/)

The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.

Similar skills

Add this badge to your README

[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/tradermonty/ibd-distribution-day-monitor/badge.svg)](https://modelsatlas.com/skills/tradermonty/ibd-distribution-day-monitor/)

Questions about ibd-distribution-day-monitor

What does the ibd-distribution-day-monitor skill do?
Claude Code skills for equity investors and traders — market analysis, technical charting, economic calendars, screeners, and trading strategy development.
Is ibd-distribution-day-monitor safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can ibd-distribution-day-monitor access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (d78aeaaa7b03), read on 2026-11-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.