CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

market-top-detector

Assesses heuristic market top risk using O'Neil Distribution Days, Minervini Leading Stock Deterioration, and Monty Defensive Sector Rotation. Generates a 0-100 composite score with risk zone classification. Use when user asks about market top risk, distribution days, defensive rotation, leadership breakdown, or whether to reduce equity exposure. Focuses on 2-8 week tactical timing signals for 10-20% corrections.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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, highly actionable skill body with a clear three-phase workflow, concrete search queries and CLI invocation, and exemplary reference-file navigation with load conditions. Main weaknesses are redundancy (auto-breadth and API-key instructions repeated multiple times, bilingual trigger duplication) and a reference to a nonexistent requirements.txt.

Suggestions

State the 200DMA auto-breadth behavior and the FMP API key requirement once (in Prerequisites and the Phase 1/2 steps respectively) and remove the duplicate 'API Requirements' section and repeated comments.

Either add the missing requirements.txt to the bundle or drop the 'Install requirements.txt' instruction in favor of the concrete pip command or dependency list.

Condense the English/Japanese 'When to Use' lists into a single trigger list, or keep only one language version and note that the other applies equally, to cut duplicated tokens.

DimensionReasoningScore

Conciseness

The 200DMA auto-breadth instructions are repeated in three places (Phase 1 item 1, Phase 2 comments, and component table notes) and the FMP API key requirement appears in both 'Prerequisites' and a separate 'API Requirements' section; the English/Japanese 'When to Use' lists also duplicate the same triggers. Not a 2 because the body is dense with actionable signal rather than padded explanation of known concepts; not a 4 because the redundancy is more than minor trimming.

3 / 5

Actionability

Provides a fully specified bash command with every CLI flag, exact primary/fallback search queries, valid input ranges ('Valid range: 20-100', '0.30-1.50'), and URL fallbacks with named fields to parse. Not a 5 because it instructs 'Install requirements.txt before running the detector' yet no requirements.txt exists in the bundle, and the script path assumes a specific install layout ('skills/market-top-detector/scripts/...') without noting the in-bundle path.

4 / 5

Workflow Clarity

A clear three-phase sequence (WebSearch collection, script execution, report presentation) with checkpoints: freshness window ('most recent 3 business days'), 'Record the data date', valid ranges, and Phase 3 'Data freshness warnings (if any data older than 3 days)'. Not a 5 because there is no explicit recovery loop for out-of-range or stale inputs (e.g., what to do when a fallback search also fails); not a 3 because validation checkpoints are present, just not exhaustive.

4 / 5

Progressive Disclosure

Four one-level-deep reference files (market_top_methodology.md, distribution_day_guide.md, historical_tops.md, point_in_time_evaluation.md) all exist in the bundle and are surfaced in a 'Reference Documents' section with a 'When to Load References' load-condition guide ('First use', 'Distribution day questions', 'Historical context', 'Regular execution: References not needed'). Body keeps methodology detail in references and delegates scoring to scripts/, matching the anchor-5 structure.

5 / 5

Total

16

/

20

Passed

Description

83%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 description in third person with an explicit trigger clause, named methodologies, a concrete scoring artifact, and a timeframe-based niche that separates it from adjacent skills. Trigger coverage is good but lacks a few natural synonyms, and the action list could be marginally more comprehensive.

DimensionReasoningScore

Specificity

Phrases like 'Generates a 0-100 composite score with risk zone classification' and 'Assesses heuristic market top risk using O'Neil Distribution Days, Minervini Leading Stock Deterioration, and Monty Defensive Sector Rotation' name concrete actions and named methodologies. Not a 5 because action coverage stops at assess/generate/classify, missing e.g. report or recommendation outputs; not a 3 because multiple specific actions are stated with a concrete scoring artifact.

4 / 5

Completeness

Explicitly answers 'what' ('Assesses heuristic market top risk... Generates a 0-100 composite score with risk zone classification') and 'when' with concrete trigger phrases ('Use when user asks about market top risk, distribution days, defensive rotation, leadership breakdown, or whether to reduce equity exposure'). This matches the anchor-5 example structure; a 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

'market top risk, distribution days, defensive rotation, leadership breakdown, or whether to reduce equity exposure' are natural phrases users would say. Not a 5 because common synonyms like 'market peak', 'correction risk', or 'sell-off timing' are absent; not a 3 because coverage spans several natural variations rather than one or two generic keywords.

4 / 5

Distinctiveness Conflict Risk

The tactical framing 'Focuses on 2-8 week tactical timing signals for 10-20% corrections' carves a clear niche distinct from macro bubble-analysis skills, and methodology names are distinctive. Not a 5 because 'whether to reduce equity exposure' is a trigger that overlaps general portfolio-allocation skills; not a 3 because overlap risk is limited to closely related skills.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

tradermonty/claude-trading-skills

Path

skills/market-top-detector/SKILL.md

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.