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.

67

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/ibd-distribution-day-monitor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

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

A well-structured, mostly executable skill body with clear rules and workflow; its main weakness is that reference files exist but are not explicitly linked from the overview.

Suggestions

Add explicit pointers to the reference files in the relevant sections, e.g. 'See references/ibd_distribution_methodology.md for full rule definitions' under Core Rules and 'See references/tqqq_exposure_policy.md' under TQQQ Exposure Policy.

Trim the tangential counting-convention translation note ('直近 N 取引日') to a one-line rationale to tighten conciseness.

Add an explicit validate-and-retry note in the Workflow for the data-quality skip step (e.g., re-pull or flag sessions with missing volume before proceeding).

DimensionReasoningScore

Conciseness

Dense and rule-focused with no padding explaining what IBD/QQQ/ETFs are; minor tangential over-explanation in the counting-convention translation note ('直近 N 取引日') and FMP tier detail keeps it just below lean.

4 / 5

Actionability

Provides an executable CLI block with real flags, concrete numeric thresholds, and named output files, plus references to real script functions; minor gap is that core detection/counting logic is delegated to scripts rather than shown inline.

4 / 5

Workflow Clarity

Nine-step workflow is clearly sequenced with a data-quality validation checkpoint and redaction step; as a read-only reporting skill the destructive/batch cap does not apply, but explicit validate-fix-retry feedback loops are light.

4 / 5

Progressive Disclosure

The body is well-sectioned and detailed methodology correctly lives in references/ and scripts/, but the body never explicitly signals or links to those reference files, leaving navigation implicit.

3 / 5

Total

15

/

20

Passed

Description

88%Weight 40%Scale 1-5

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, specific description that clearly states both capabilities and trigger conditions with a useful boundary clause. Slight room to improve trigger-term synonyms for broader discoverability.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions with parameters — detect DDs (close down >=0.2% on higher volume), track 25-session expiration and 5% invalidation, count d5/d15/d25 clusters, classify risk into four named bands, and emit exposure recommendations — giving comprehensive coverage.

5 / 5

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 concrete trigger phrases, plus a boundary ('Does not execute trades').

5 / 5

Trigger Term Quality

Strong natural domain keywords (Distribution Days, QQQ/SPY, TQQQ exposure, FTD/market-state), but missing common synonyms a casual user might say (e.g., 'market sell-off', 'correction risk').

4 / 5

Distinctiveness Conflict Risk

The IBD-style Distribution Day niche with specific tickers is mostly distinct, but closely related sibling skills (ftd-detector, market-top-detector) create minor overlap risk.

4 / 5

Total

18

/

20

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.