CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

breadth-chart-analyst

This skill should be used when analyzing market breadth charts, specifically the S&P 500 Breadth Index (200-Day MA based) and the US Stock Market Uptrend Stock Ratio charts. Use this skill when the user provides breadth chart images for analysis, requests market breadth assessment, positioning strategy recommendations, or wants to understand medium-term strategic and short-term tactical market outlook based on breadth indicators. Also works WITHOUT chart images by fetching CSV data directly from public sources. All analysis and output are conducted in English.

Quality

83%

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

73%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 highly actionable, well-sequenced analysis workflow with concrete commands, explicit thresholds, validation checklists, and real one-level-deep bundle references. Its main weakness is verbosity — the language mandate, color-check warnings, and confirmation criteria are each repeated many times, and chart-strategy details are duplicated between SKILL.md and the methodology reference.

Suggestions

State the English-only requirement once (e.g., in Prerequisites) and remove the other six repetitions, including the full 'Special Notes — Language Requirement' section — a single CRITICAL statement suffices.

Delete the 'Example Usage Scenarios' section or compress it to a few lines, since all three examples restate Steps 0–7 verbatim without adding new information.

Move the chart element/threshold/strategy details from 'Chart Types and Purposes' into references/breadth_chart_methodology.md, keeping only a one-line-per-chart summary in SKILL.md, and consolidate the signal-confirmation criteria (currently in Steps 4.1.5, 4.4, and Error 5) into one location.

DimensionReasoningScore

Conciseness

Noticeably verbose with several padded sections: the English-only mandate is stated at least seven times (Overview, Prerequisites, 'Language Note', Core Principle 4, Step 7 'IMPORTANT', QA item 1, and a full 'Special Notes — Language Requirement' CRITICAL section); the '8MA = ORANGE, 200MA = GREEN' color check is repeated in Step 4.1.5, QA item 2, and Error 1; signal-confirmation criteria are duplicated across Steps 4.1.5, 4.4, and Error 5; and the ~50-line 'Example Usage Scenarios' section restates the workflow steps verbatim. It is not 1 because it does not explain general concepts Claude already knows — the padding is domain-specific repetition, not educational filler — but it is below 3 because entire sections could be deleted without losing information.

2 / 5

Actionability

Fully executable, copy-paste-ready guidance: 'python3 skills/breadth-chart-analyst/scripts/fetch_breadth_csv.py' (with a --json variant), 'python3 skills/breadth-chart-analyst/scripts/extract_chart_right_edge.py <image_path> --percent 25', exact thresholds (73%/23%, 10%/40%), enumerated BUY/SELL criteria with confirmation rules, concrete output filenames ('breadth_combined_analysis_[YYYY-MM-DD].md'), a sample expected-output block, and a report template asset. Common cases (charts-only, CSV-only, both) are all covered explicitly.

5 / 5

Workflow Clarity

Steps 0–8 are clearly sequenced with explicit validation checkpoints and feedback loops: a Step 0 post-fetch validation checklist, the two-stage analysis protocol with a precedence rule ('If Stage 1 and Stage 2 values differ significantly, Stage 2 takes precedence'), the Step 4.1.5 mandatory cross-check questions, failed-reversal detection with explicit recovery behavior ('DO NOT ENTER, WAIT FOR NEXT TROUGH'), and a 14-item QA checklist plus final sanity checks. Matches the top anchor's validate→fix→retry pattern; analysis (non-destructive) work, so the batch-operation cap does not apply.

5 / 5

Progressive Disclosure

Good structure with well-signaled one-level-deep references that all exist and are substantive: 'Read: references/breadth_chart_methodology.md' (590 lines), the report template and sample chart images in assets/, and four scripts documented in a Resources section. However, content is not cleanly split — the 'Chart Types and Purposes' section (~40 lines of chart elements, thresholds, and strategy rules) duplicates what breadth_chart_methodology.md already covers, and deprecated scripts are documented both inline (Step 5.0) and in Resources. Not 5 because of this duplication; not 3 because navigation is easy, references are clearly signaled, and nothing is nested beyond one level.

4 / 5

Total

16

/

20

Passed

Description

87%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 that explicitly covers what the skill does and when to use it, with concrete trigger phrases and a distinct niche anchored to two named breadth indicators. The main weaknesses are mild redundancy in the opening ('This skill should be used when... Use this skill when...') and a few missing natural trigger variations.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'analyzing market breadth charts, specifically the S&P 500 Breadth Index (200-Day MA based) and the US Stock Market Uptrend Stock Ratio charts', 'fetching CSV data directly from public sources', positioning recommendations — but several capabilities are framed as user-request triggers ('requests market breadth assessment, positioning strategy recommendations') rather than clean capability statements, and the opening two sentences are redundant padding. Not 5 because the action coverage is wrapped in trigger phrasing with minor gaps; not 3 because multiple concrete actions and both operating modes (with and without chart images) are explicitly covered.

4 / 5

Completeness

Clearly answers both questions: what — 'analyzing market breadth charts, specifically the S&P 500 Breadth Index (200-Day MA based) and the US Stock Market Uptrend Stock Ratio charts' plus 'Also works WITHOUT chart images by fetching CSV data'; when — an explicit 'Use this skill when the user provides breadth chart images for analysis, requests market breadth assessment, positioning strategy recommendations, or wants to understand medium-term strategic and short-term tactical market outlook' with concrete trigger phrases. Matches the top anchor; not 4 because the 'when' clause is explicit and specific, not merely present-but-improvable.

5 / 5

Trigger Term Quality

Good keyword coverage with natural phrases users would say: 'market breadth', 'breadth chart images', the two specific chart names, 'positioning strategy', 'market outlook', 'CSV data'. Not 5 because common variations are missing (e.g., 'breadth analysis', 'stocks above the 200-day moving average', 'market internals'); not 3 because coverage goes beyond a couple of generic keywords and includes the specific indicator names plus both input modes.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers: the two named indicators ('S&P 500 Breadth Index (200-Day MA based)', 'US Stock Market Uptrend Stock Ratio') are highly specific and unlikely to collide with general market-analysis or stock-picking skills. Not 4 because the triggers are near-unique chart names rather than a pair of overlapping document formats.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (768 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

tradermonty/claude-trading-skills

Path

skills/breadth-chart-analyst/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.