CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

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/uptrend-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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, largely actionable overview for a script-driven skill, with a real reference file and a clear two-phase workflow. Its weaknesses are redundancy (bilingual trigger list, repeated API-key notes) and inlining methodology detail that belongs in the reference, plus a script path that doesn't match the bundle layout.

Suggestions

Remove the duplicated Japanese trigger list and the repeated "no API key" statements (keep one), and drop the EMA expansion — the acronym is sufficient.

Move the Warning System thresholds, Momentum Smoothing, and Historical Confidence details into references/uptrend_methodology.md, keeping only a one-line summary in SKILL.md.

Fix the execution path to the bundle-relative location (scripts/uptrend_analyzer.py) and add a short error-recovery step for CSV download failures or stale data.

DimensionReasoningScore

Conciseness

Mostly efficient tables of skill-specific data, but noticeable padding: the Japanese "When to Use" list duplicates the English one, "no API key required" is repeated four times (description, Prerequisites, Phase 1, API Requirements), and "EMA(3) (Exponential Moving Average, span=3)" spells out a concept Claude already knows. Not a 2 because the bulk is genuinely non-redundant scoring detail.

3 / 5

Actionability

The workflow is executable: "python3 skills/uptrend-analyzer/scripts/uptrend_analyzer.py" plus a concrete list of what the script does and exactly what to present from the output files. Not a 5 because the script path doesn't match the bundle-relative location (scripts/uptrend_analyzer.py), and there is no guidance for the common failure case (CSV fetch failing).

4 / 5

Workflow Clarity

The two-phase workflow (execute script → present results) is clearly sequenced with concrete checkpoints (script steps, report highlights, output filenames). Not a 5 because there are no validation or error-recovery steps (e.g., stale data check, network-failure handling), though the read-only nature of the operation keeps it above 3.

4 / 5

Progressive Disclosure

Good structure: the body is an overview with one clearly signaled, one-level-deep reference (references/uptrend_methodology.md, verified to exist and cover the claimed topics) plus explicit "When to Load References" guidance, and the calculators/tests live appropriately in the script bundle. Not a 5 because detailed methodology (warning thresholds, EMA smoothing, confidence indicator) is inlined in SKILL.md where the reference would be the natural home.

4 / 5

Total

15

/

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 voice with a clear what/when structure and a distinctive niche anchored to a named data source. Its only gaps are a few missing natural trigger synonyms and slightly incomplete coverage of the skill's full output capabilities.

Suggestions

Add natural trigger variations such as "how broad is the rally" or "market participation" to the Use-when clause.

Mention the key outputs (composite score zones with exposure guidance, sector heatmap report) so the capability list is comprehensive.

DimensionReasoningScore

Specificity

"Analyzes market breadth", "diagnose the current market environment", and "Generates a 0-100 composite score from 5 components (breadth, sector participation, rotation, momentum, historical context)" name several concrete, specific actions. Not a 5 because it omits other capabilities (report/heatmap generation, exposure guidance output), leaving minor gaps in coverage.

4 / 5

Completeness

Clearly answers what ("Analyzes market breadth... Generates a 0-100 composite score from 5 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 exactly.

5 / 5

Trigger Term Quality

"market breadth", "uptrend ratios", "market environment", and "equity exposure" are natural phrases a user would say. Not a 5 because common variations like "how broad is the rally", "market participation", or the dashboard's plain name are missing.

4 / 5

Distinctiveness Conflict Risk

The named proprietary dashboard ("Monty's Uptrend Ratio Dashboard") and breadth-specific triggers carve a clear niche. Not a 5 because the broader phrasing "whether the market environment supports equity exposure" could overlap with a general market-risk or top-detector 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
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.