CtrlK
BlogDocsLog inGet started
Tessl Logo

ibd-distribution-day-monitor

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.

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, actionable skill body with executable CLI guidance and clear rule tables. The main gaps are the absence of an explicit error-recovery feedback loop in the workflow and the failure to point readers to the existing reference files.

Suggestions

Add an explicit feedback loop to the workflow, e.g. after step 2 (validate data quality): if sessions are skipped or volume is unreliable, re-run with a longer lookback or flag the run as unreliable before proceeding.

Link the reference files from the body — e.g. under Core Rules add 'See [references/ibd_distribution_methodology.md](references/ibd_distribution_methodology.md) for full rule derivation' and under TQQQ Exposure Policy point to references/tqqq_exposure_policy.md.

Surface the scripts/ entry point and module roles (e.g. risk_classifier.py, exposure_policy.py) so a reader knows where each workflow step is implemented without listing the directory.

DimensionReasoningScore

Conciseness

Lean, table-driven body that assumes Claude's competence — it states rules and thresholds without explaining what a distribution day or EMA is, and every section earns its place.

3 / 3

Actionability

Provides a copy-paste-ready CLI invocation plus concrete thresholds (0.2%, 25 sessions, 5%), named API functions, and exact output paths rather than abstract direction.

3 / 3

Workflow Clarity

The 9-step workflow is clearly sequenced and includes a data-quality validation step, but there is no explicit validate→fix→retry feedback loop for the batch data operation, leaving checkpoints implicit.

2 / 3

Progressive Disclosure

The body is well-sectioned and detailed methodology/policy are split into references/ files, but those reference files are never linked or signaled from the body, so navigation to them is missing.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that states concrete capabilities and explicit use-when triggers for a well-scoped trading niche. No fluff, over-claims, or voice violations.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Detect IBD-style Distribution Days', 'track 25-session expiration and 5% invalidation', 'count d5/d15/d25 clusters', 'classify market risk', 'emit TQQQ/QQQ exposure recommendations') rather than vague language.

3 / 3

Completeness

Explicitly answers both what (detect/track/count/classify/emit) and when ('Use after market close, before TQQQ exposure changes, or as input to FTD/market-state frameworks'), with an explicit 'Use ...' trigger clause.

3 / 3

Trigger Term Quality

Covers the natural terms a user of this niche would actually say — 'Distribution Days', 'QQQ/SPY', 'TQQQ exposure', 'FTD/market-state frameworks' — with good variation rather than generic jargon.

3 / 3

Distinctiveness Conflict Risk

A clear niche (IBD distribution-day monitoring for QQQ/SPY with TQQQ exposure policy) with distinct triggers that would not plausibly fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tradermonty/claude-trading-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.