downtrend-duration-analyzer

Analyze historical downtrend durations and generate interactive HTML histograms showing typical correction lengths by sector and market cap.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/downtrend-duration-analyzer/SKILL.md

Quality

Content

68%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 a well-structured, actionable overview with executable commands, concrete output schemas, and real one-level-deep bundle references that were verified to exist. Its main weaknesses are the total absence of validation/verification steps in a batch data-fetching workflow and some trimmable redundancy in the output examples and Key Principles section.

Suggestions

Add validation checkpoints to the workflow, e.g. after Step 1 verify the JSON report is non-empty and covers the requested sector before generating the histogram, and note how to handle FMP API rate limits or partial fetch failures.

Trim redundancy: the markdown report example repeats the JSON example's numbers — show one representative excerpt and reference the JSON schema for the rest, and cut or shrink the 'Key Principles' section.

Fix the command paths to be relative to the skill bundle ('scripts/analyze_downtrends.py') or explain the expected working directory, and explain the glob pattern in the generate_histogram_html.py invocation.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes domain competence — no space is wasted explaining what downtrends or histograms are — but the full sample JSON (~44 lines) and markdown report (~33 lines) duplicates information, and the 'Key Principles' section ('Statistical Rigor', 'Segmentation Matters', 'Realistic Expectations') is advisory padding that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready bash commands with concrete flags (--sector, --lookback-years, --output-dir), explicit output filenames, and complete output schemas; the minor gaps are the hardcoded 'skills/downtrend-duration-analyzer/scripts/...' path prefix that assumes a specific directory layout and an unexplained glob in the second command.	4 / 5
Workflow Clarity	The four steps are clearly sequenced (fetch/analyze, generate HTML, review insights), but there are no validation checkpoints anywhere — no guidance on verifying the JSON report before visualization, handling API failures, or confirming output completeness — and the data fetch is a batch operation over a universe of stocks, which caps workflow clarity at 3 per the rubric's feedback-loop note.	3 / 5
Progressive Disclosure	Good structure: the body stays an overview with workflow and output formats, and the Resources section clearly signals one-level-deep references ('scripts/analyze_downtrends.py', 'scripts/generate_histogram_html.py', 'references/downtrend_methodology.md') that all exist in the actual bundle; references are backticked paths rather than markdown links and the methodology detail is only hinted at, leaving minor organization gaps versus the well-signaled anchor.	4 / 5
	Total	15 / 20 Passed

Description

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

The description clearly conveys what the skill does with domain-specific, concrete language, but it lacks any explicit 'when to use' trigger guidance and misses common synonyms like drawdown or pullback. It is distinct from neighboring skills yet would benefit from a trigger clause to raise completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when traders ask how long corrections typically last, or when estimating recovery timeframes for pullback or mean-reversion strategies.'

Include common synonyms users would naturally say — 'drawdown', 'pullback', 'recovery time' — alongside 'downtrend' and 'correction' to broaden trigger coverage.

Mention the additional concrete outputs (percentile statistics, markdown/JSON reports) to move specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('historical downtrend durations', 'correction lengths by sector and market cap') and exactly two concrete actions — 'Analyze' and 'generate interactive HTML histograms' — but omits other capabilities the skill performs (data fetching, percentile statistics, markdown reports), matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	The 'what' is clear (analyze downtrend durations, generate HTML histograms segmented by sector and market cap), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Includes natural terms a trader would say such as 'downtrend', 'correction lengths', 'sector', and 'market cap', giving good keyword coverage; however, common synonyms like 'drawdown', 'pullback', or 'recovery time' are missing, so it falls just short of the comprehensive-synonyms anchor.	4 / 5
Distinctiveness Conflict Risk	The niche — downtrend duration statistics segmented by sector and market cap — is fairly distinct with specific triggers; only minor overlap risk exists with general stock-analysis or charting skills that also mention sectors or historical prices.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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/downtrend-duration-analyzer/SKILL.md
Commit: eab8d5c

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.