CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

uptrend-analyzer

Analyzes market breadth using Monty's Uptrend Ratio Dashboard data to diagnose the current market environment. Generates a 0-100 composite score from 5 components (breadth, sector participation, rotation, momentum, historical context). Use when asking about market breadth, uptrend ratios, or whether the market environment supports equity exposure. No API key required.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/uptrend-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

The body delivers a clear overview, a concrete run command, and well-organized scoring tables, and its reference file is real and properly signaled. Its weaknesses are redundancy (duplicated zone tables and inlined methodology the script and reference already handle) and a provenance section that references external skills and flags not resolvable within this bundle.

Suggestions

Move the Warning System, Momentum Smoothing, and Historical Confidence Indicator sections into references/uptrend_methodology.md, keeping only a one-line pointer, since the body already states the script handles scoring during regular execution.

Merge the '7-Level Zone Detail' table into the 'Scoring Zones' table (or drop it) to remove the duplicated zone breakdown, and consider compressing the Market Top Detector comparison and bilingual trigger list.

Clarify the 'Same-run provenance' section: either scope it to this skill's verified '--run-id' flag (which scripts/uptrend_analyzer.py supports) or move the external market-regime-daily/Exposure Coach handoff details to the skill that orchestrates those tools; also fix the run command path to match the bundle layout (scripts/uptrend_analyzer.py).

DimensionReasoningScore

Conciseness

The body is mostly compact tables, but it duplicates zone detail across 'Scoring Zones' and '7-Level Zone Detail', inlines scoring internals the script already applies (EMA(3) smoothing, 10v10 acceleration windows, warning penalty stacking), and spends tokens on a comparison table for a different skill, a bilingual trigger list, and a dense provenance section about external tools.

3 / 5

Actionability

Execution guidance is concrete (a runnable python3 command, numbered script behavior, named output files, explicit reference-loading rules), but the command path assumes an install layout ('skills/uptrend-analyzer/scripts/...') rather than the bundle's 'scripts/' location, and the provenance section instructs use of external tools ('market-regime-daily producers', Exposure Coach's '--require-provenance ... --as-of' mode) without resolvable commands.

4 / 5

Workflow Clarity

The two-phase sequence (run script, then present the report with specified highlights) is clear and the script self-validates (malformed primary dates stop report generation), but there is no error-recovery guidance for the multi-tool provenance handoff described in the final section, which is itself under-sequenced.

4 / 5

Progressive Disclosure

The single reference (references/uptrend_methodology.md, verified to exist) is one level deep and well signaled with a 'When to Load References' section, but the body inlines methodology detail (warning system, momentum smoothing, historical confidence indicator) that the reference file already covers, so content that should be separate is inline.

3 / 5

Total

14

/

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: third-person voice, concrete capability statements, and an explicit 'Use when' clause with domain-appropriate trigger terms. The only weaknesses are minor coverage gaps (outputs like exposure guidance and reports) and a small overlap risk with the sibling Market Top Detector skill.

DimensionReasoningScore

Specificity

Concrete actions are stated ('Analyzes market breadth', 'diagnose the current market environment', 'Generates a 0-100 composite score from 5 components') with the components enumerated, but output artifacts like reports and exposure guidance are unmentioned, leaving minor coverage gaps.

4 / 5

Completeness

It explicitly answers both 'what' (analyzes breadth via the dashboard, generates a 0-100 composite from 5 named components) and 'when' ('Use when asking about market breadth, uptrend ratios, or whether the market environment supports equity exposure') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural phrases are present ('market breadth', 'uptrend ratios', 'whether the market environment supports equity exposure', "Monty's Uptrend Ratio Dashboard"), but common synonyms such as 'market participation' or 'rally breadth' are missing.

4 / 5

Distinctiveness Conflict Risk

The Monty dashboard/uptrend-ratio niche is distinct with clear triggers, but it conceptually overlaps a sibling market-environment scorer (the Market Top Detector), creating minor conflict risk with a closely related skill.

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/uptrend-analyzer/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.