CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ftd-detector

Detects Follow-Through Day (FTD) signals for market bottom confirmation using William O'Neil's methodology. Dual-index tracking (S&P 500 + NASDAQ) with state machine for rally attempt, FTD qualification, and post-FTD health monitoring. Use when user asks about market bottom signals, follow-through days, rally attempts, re-entry timing after corrections, or whether it's safe to increase equity exposure. Complementary to market-top-detector (defensive) - this skill is offensive (bottom confirmation).

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 content is a well-structured, highly actionable operational guide with a clear execution workflow, explicit state machine, and verified one-level-deep references. Its main weaknesses are verbose, partially duplicated data-gap handling inline in SKILL.md, some organizational misplacement (orphaned notes after the references section), and a duplicated bilingual trigger list.

Suggestions

Move the detailed 'Data gaps' edge-case rules (per-field JSON semantics, power-trend and volume-0 specifics) into a reference file such as references/data_gaps.md, keeping only the headline rule and the 'do not increase exposure' checkpoint in SKILL.md.

Relocate the two orphaned bullets that follow 'When to Load References' (FTD-day-low quality cap of 59, lifecycle-low gap) into the 'FTD lifecycle and evidence contract' or 'Quality Score' section so no content dangles after the navigation guidance.

Consolidate the repeated 'exposure not assessed' / Day 1 low caveats into the evidence-contract section and reference it once from the workflow and score tables instead of restating it in each section.

DimensionReasoningScore

Conciseness

The body is mostly dense and useful, but the 'Data gaps' subsection spans ~10 highly detailed paragraphs, the 'When to Use' list is duplicated in English and Japanese, and key caveats ('exposure not assessed', Day 1 low rules) are repeated across the contract, workflow, and score sections. It could be tightened by moving data-gap edge-case detail into a reference; not 2 because it never explains concepts Claude already knows and is not padded with fluff.

3 / 5

Actionability

Provides an executable command ("python3 skills/ftd-detector/scripts/ftd_detector.py --api-key $FMP_API_KEY"), concrete state-machine and score tables, named output files, and state-specific guidance for presenting results. Not 5 because there is no example of the JSON/Markdown output shape or error-recovery commands; not 3 because the primary path is fully executable rather than pseudocode.

4 / 5

Workflow Clarity

Clear three-phase sequence (Execute Script → Present Results → Contextual Guidance) with per-state branches and explicit data-gap checkpoints ("Treat this as 'no usable confirmation': do not increase exposure on it"). Not 5 because recovery steps for API failures or retry behavior are only implied ("retries may add calls") rather than given as an explicit validate→fix→retry loop.

4 / 5

Progressive Disclosure

Both referenced files exist in the bundle (references/ftd_methodology.md, references/post_ftd_guide.md) and are summarized with a 'When to Load References' loading guide — a clear one-level-deep structure. Not 5 because the long inline 'Data gaps' contract and two orphaned trailing notes after 'When to Load References' (the quality-cap-59 and lifecycle-low-gap bullets) are misplaced content that belongs in the references or an earlier section.

4 / 5

Total

15

/

20

Passed

Description

92%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 is a strong example: third-person voice, concrete multi-part capability statement, an explicit 'Use when' trigger clause with natural user phrases, and explicit differentiation from the sibling market-top-detector skill. The only weakness is slightly incomplete synonym coverage in its trigger terms.

DimensionReasoningScore

Specificity

Quotes: "Detects Follow-Through Day (FTD) signals for market bottom confirmation", "Dual-index tracking (S&P 500 + NASDAQ) with state machine for rally attempt, FTD qualification, and post-FTD health monitoring" — multiple specific, concrete capabilities that comprehensively cover detection, tracking mechanics, and post-event monitoring. Not the 4 anchor because coverage is full rather than having minor gaps; not below because every clause names a concrete action.

5 / 5

Completeness

Explicitly answers 'what' ("Detects Follow-Through Day (FTD) signals... Dual-index tracking... state machine") and 'when' with a concrete "Use when user asks about..." clause listing multiple trigger phrases. Matches the score-5 anchor exactly; a missing or weak 'Use when' clause would cap it at 3, which is not the case here.

5 / 5

Trigger Term Quality

Quotes: "market bottom signals, follow-through days, rally attempts, re-entry timing after corrections, or whether it's safe to increase equity exposure" — strong natural phrases users would actually say. Not 5 because a few common variations are missing (e.g., "is the market bottoming", "correction over", "buy signal"); not 3 because coverage clearly goes beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Quotes: "Complementary to market-top-detector (defensive) - this skill is offensive (bottom confirmation)" — a clear niche with distinct triggers and an explicit differentiation from the closest related skill. Minimal conflict risk; matches the score-5 anchor.

5 / 5

Total

19

/

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/ftd-detector/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.