CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

market-breadth-analyzer

Quantifies market breadth health using TraderMonty's public CSV data. Generates a 0-100 composite score across 6 components (100 = healthy). No API key required. Use when user asks about market breadth, participation rate, advance-decline health, whether the rally is broad-based, or general market health assessment.

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.

The body is well-structured and highly actionable, with a clean two-phase workflow, validation checkpoints, and exemplary progressive disclosure of a single methodology reference. Its main weakness is token efficiency: the trigger section duplicates the description and the provenance section buries operational detail that belongs in a reference.

Suggestions

Remove or drastically shorten the "When to Use This Skill" section (both English and Japanese lists) — the frontmatter description already states the triggers, so this duplication costs ~14 lines of context.

Move the detailed "Same-run provenance" flag semantics (adjustment/point-in-time/survivorship flag values, Exposure Coach integration) into a reference document or the script's --help, keeping only the essential "pass --run-id to both producers" instruction in SKILL.md.

Integrate the provenance flags into the Phase 1 example command (or show a second complete example) so the full invocation is copy-paste ready, and tighten the output-dir troubleshooting paragraph to a one-line note.

DimensionReasoningScore

Conciseness

Mostly table- and command-driven, but the "When to Use This Skill" section (English + Japanese, ~14 lines) duplicates the frontmatter description, the output-dir troubleshooting paragraph rambles, and the "Same-run provenance" section is in-the-weeds ("Unknown adjustment, point-in-time, survivorship and corporate-action flags are false"). These are more than minor trim opportunities, matching anchor 3 rather than anchor 4.

3 / 5

Actionability

Provides a copy-paste-ready bash command with full URLs, flags, and output directory, plus an enumerated list of what the script does and a concrete presentation checklist. Minor gaps keep it below anchor 5: the `<routine-or-date>` placeholder requires substitution, and the `--run-id`/provenance flags described later are not integrated into the Phase 1 command.

4 / 5

Workflow Clarity

A clear two-phase sequence (execute script, then present results) with validation checkpoints (data freshness warning, "Missing or malformed primary dates stop report generation", automatic weight redistribution) and a feedback loop (rerun once with a repo-relative path if the nested output-dir fails). It falls short of anchor 5 because the provenance/--run-id integration with Exposure Coach is described in a disconnected, hard-to-follow way rather than as an explicit workflow step.

4 / 5

Progressive Disclosure

A clear overview with one well-signaled, one-level-deep reference (`references/breadth_analysis_methodology.md`, verified to exist) and explicit when-to-load guidance ("First use: Load methodology reference" / "Regular execution: References not needed"). The large scripts bundle is correctly surfaced only via the entry-point script, matching anchor 5.

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: concrete capability statements, explicit "Use when..." triggers covering natural user phrasings, and a distinct data-driven niche. The only weaknesses are a couple of missing breadth synonyms and no disambiguation from the closely related Breadth Chart Analyst skill.

DimensionReasoningScore

Specificity

"Quantifies market breadth health using TraderMonty's public CSV data" and "Generates a 0-100 composite score across 6 components (100 = healthy)" name concrete actions with data source, output format, and score semantics. Minor gaps in coverage (e.g., trend tracking, report generation are not mentioned), matching anchor 4 rather than the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both "what" ("Quantifies market breadth health... Generates a 0-100 composite score across 6 components") and "when" ("Use when user asks about market breadth, participation rate..."), with concrete trigger phrases — a direct match to anchor 5. Not anchor 4 because the "when" clause is already fully explicit and specific.

5 / 5

Trigger Term Quality

"market breadth, participation rate, advance-decline health, whether the rally is broad-based, or general market health assessment" are natural phrases users would say. A few common synonyms are missing (e.g., "market internals", "A/D line", "breadth thrust"), so it fits anchor 4 rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The TraderMonty CSV source and 0-100 composite output carve a clear niche, but the body reveals a sibling "Breadth Chart Analyst" skill sharing "market breadth" triggers that the description does not disambiguate, giving minor overlap risk with a closely related skill — anchor 4 rather than 5.

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-breadth-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.