CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

downtrend-duration-analyzer

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

Quality

74%

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

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 skill body delivers a well-structured, fully executable two-script workflow with real bundle references and concrete output specifications. Its weaknesses are modest redundancy in the doubled output-format examples and — more materially — the complete absence of validation/verification checkpoints in a batch data-fetching workflow, which caps workflow clarity at 3.

Suggestions

Add validation checkpoints: verify FMP_API_KEY is set before the batch fetch, and confirm the analysis JSON exists and is non-empty before invoking generate_histogram_html.py (with a fix-and-retry loop on failure).

Drop one of the two full output examples (the markdown report duplicates the JSON report's statistics) or truncate both to representative fields.

Move the detailed output schema to references/ (e.g. output_schema.md) and keep only field highlights inline.

DimensionReasoningScore

Conciseness

The workflow steps, prerequisites, and key principles are lean and assume competence, but the body inlines two full fabricated output examples — a ~44-line JSON report and a ~33-line markdown report that largely duplicate the same statistics. This is the "mostly efficient but includes some unnecessary explanation or could be tightened" anchor; trimming one format or showing truncated fields would reach 4.

3 / 5

Actionability

Both scripts are invoked with copy-paste-ready bash commands including flags (--sector, --lookback-years, --output-dir, --input), concrete output filenames with timestamp patterns, and worked examples of the JSON and markdown outputs. This matches "fully executable; copy-paste ready code or commands; specific examples cover the common cases"; it is not a 4 because there are no meaningful gaps in the primary workflow.

5 / 5

Workflow Clarity

The four steps are clearly sequenced, but there are no validation checkpoints anywhere — no check that the analysis JSON exists before invoking the histogram generator, no API-key/credential verification before a batch fetch across a universe of stocks. This is a batch data operation, so per the rubric's cap rule for batch workflows without validation, workflow clarity cannot exceed 3 despite the clean sequence.

3 / 5

Progressive Disclosure

The body is a genuine overview with a Resources section listing all three bundle files (scripts/analyze_downtrends.py, scripts/generate_histogram_html.py, references/downtrend_methodology.md), each verified to exist and one level deep with clear descriptions. Not a 5 because the full inline JSON and markdown report examples are content that could partially live in a reference file; not a 3 because references are clearly signaled and nothing that clearly belongs elsewhere is inlined wholesale.

4 / 5

Total

15

/

20

Passed

Description

66%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 gives a specific, third-person account of what the skill does, with good domain keyword coverage and low conflict risk. Its main weakness is the absence of any explicit "Use when..." trigger clause, which caps completeness and leaves activation guidance implied rather than stated.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about correction lengths, drawdown recovery times, or typical downtrend durations for a sector or market cap tier."

Include common synonyms users would say — "drawdown", "pullback", "recovery time" — alongside "downtrend" and "correction".

Mention the summary-statistics/percentile output (median, P25/P75/P90 durations) to round out capability coverage.

DimensionReasoningScore

Specificity

"Analyze historical downtrend durations" and "generate interactive HTML histograms showing typical correction lengths by sector and market cap" name two concrete actions with specific segmentation detail. Not a 5 because it covers only two actions and omits capabilities the body reveals (summary statistics, percentile reporting), and not a 3 because the actions listed are more detailed than the 1-2 generic actions anchor.

4 / 5

Completeness

The "what" is clear (analyze downtrend durations, generate histograms by sector and market cap), but there is no "Use when..." clause or equivalent trigger guidance — the "when" is only weakly implied by the domain terms. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms include "downtrend durations", "correction lengths", "sector", "market cap", "historical" — phrases a trader would plausibly say. Not a 5 because common synonyms like "drawdown", "pullback", "recovery time", or "how long do corrections last" are missing; not a 3 because the existing keyword set goes beyond a bare domain mention with several natural variations.

4 / 5

Distinctiveness Conflict Risk

The niche (downtrend duration statistics segmented by sector and market cap) is clearly distinguishable and unlikely to trigger the wrong skill. Not a 5 because "generate interactive HTML histograms" carries minor overlap risk with generic charting/dataviz skills, placing it at the "mostly distinct; minor overlap risk" anchor.

4 / 5

Total

15

/

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/downtrend-duration-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.