CtrlK
BlogDocsLog inGet started
Tessl Logo

downtrend-duration-analyzer

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

60

Quality

68%

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

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete commands and output schemas, and progressive disclosure is well handled with real one-level references. It loses points on conciseness (redundant inline report examples) and workflow clarity (no validation checkpoints for the batch fetch/analyze/generate pipeline).

Suggestions

Add a validation checkpoint between analysis and HTML generation — e.g. verify reports/downtrend_analysis_*.json is non-empty and well-formed before running generate_histogram_html.py.

Trim the inline JSON and markdown report examples to a minimal schema sketch, or move the full schema into a reference file to reduce token overhead.

Include brief error-recovery guidance for FMP API failures (rate limits, missing symbols) in the workflow steps.

DimensionReasoningScore

Conciseness

Mostly efficient with executable command blocks and a focused structure, but it includes inline JSON and markdown report examples that largely restate the summary statistics already described, and the 'Key Principles' section restates concepts Claude already knows about percentiles and segmentation.

2 / 3

Actionability

Provides concrete, copy-paste-ready bash commands with arguments, names the exact output files, and shows the precise JSON/markdown output schema Claude should expect — fully executable guidance.

3 / 3

Workflow Clarity

Steps are clearly sequenced (fetch → analyze → generate → review), but this batch data-fetching operation has no validation checkpoints: no confirmation that the JSON analysis output exists or is non-empty before generating the HTML, and no error-recovery guidance for API failures.

2 / 3

Progressive Disclosure

SKILL.md is an overview with well-signaled one-level-deep references — the Resources section points to real bundle files (scripts/analyze_downtrends.py, scripts/generate_histogram_html.py, references/downtrend_methodology.md), all verified to exist, and detail is appropriately split rather than nested.

3 / 3

Total

10

/

12

Passed

Description

67%

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 is specific and clearly distinct, naming concrete actions and a narrow niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which leaves the activation conditions implied rather than stated.

Suggestions

Add an explicit trigger clause such as 'Use when a trader asks about typical correction lengths, drawdown recovery times, or holding-period estimates for a sector or market-cap tier.'

Incorporate more natural user phrasings alongside the technical terms (e.g. 'how long do pullbacks last', 'correction recovery time').

Keep the third-person voice while making the 'when to use' guidance as explicit as the 'what it does' guidance.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Analyze historical downtrend durations' and 'generate interactive HTML histograms' with the segmentation dimensions (by sector and market cap) named explicitly.

3 / 3

Completeness

It clearly answers 'what does this do', but there is no 'Use when...' clause or equivalent explicit trigger guidance, so the 'when' dimension is missing — per the rubric this caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant terms like 'downtrend durations' and 'histograms', but lacks common natural variations a user would say ('how long do corrections last', 'drawdown recovery time', 'pullback duration') and the technical phrasing is somewhat jargon-leaning.

2 / 3

Distinctiveness Conflict Risk

The niche (historical downtrend-duration analysis with sector/market-cap segmented HTML histograms) is narrow and specific, with triggers unlikely to overlap with other skills.

3 / 3

Total

10

/

12

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.

Validation16 / 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.