CtrlK
BlogDocsLog inGet started
Tessl Logo

canslim-screener

Screen US stocks using William O'Neil's CANSLIM growth stock methodology. Use when user requests CANSLIM stock screening, growth stock analysis, momentum stock identification, or wants to find stocks with strong earnings and price momentum following O'Neil's investment system.

60

Quality

76%

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/canslim-screener/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 delivers a well-sequenced, genuinely actionable workflow with real commands, flags, and thorough troubleshooting, backed by a real one-level-deep reference bundle. Its main weakness is token efficiency: rating bands, prerequisites, and execution-time figures are repeated multiple times, and internal phase/version history plus marketing-style sections pad the file well beyond what the operational content requires.

Suggestions

State the rating bands, API-key setup, and pip-install instructions exactly once (Prerequisites/Output) and remove the duplicates in the Overview, Step 1, and Step 5 sections.

Move the per-calculator scoring thresholds and the detailed report template into references/scoring_system.md and references/interpretation_guide.md, keeping only a one-line pointer plus component weights in SKILL.md.

Cut the internal-development narrative (Phase 3/3.1/4 history, 'Tested Reliability' stats, 'Last Updated' date) or consolidate it into a short version block, and normalize script paths to a single consistent invocation form.

DimensionReasoningScore

Conciseness

The ~660-line body has noticeably duplicated and padded sections: the rating bands (Exceptional+/Exceptional/Strong/Above Average) are stated three times (Overview, Output, Step 5), API-key and pip-install instructions appear twice (Prerequisites and Step 1), and execution time is repeated three times. It also carries internal dev-history noise ('Phase 3', 'Phase 3.1 additions', 'Phase 4 planned', 'Last Updated: 2026-05-03') and marketing-style padding ('Key Features', 'Tested Reliability: 39/39 stocks'), matching the 2 anchor 'Noticeably verbose; several unnecessary explanations or padded sections'. It is not a 3 because the duplication is pervasive rather than isolated, and per the guidelines time-sensitive version/date information outside a deprecated section further penalizes conciseness.

2 / 5

Actionability

Mostly executable guidance: copy-paste commands with real flags (`--universe AAPL MSFT...`, `--max-candidates 35`, `--rs-benchmark SPY`, `--disable-rs`), pip install lines, report-reading commands (`ls -lt canslim_screener_*.md | head -1`), and troubleshooting with concrete symptoms and fixes. It is not a 5 due to minor gaps: script paths are inconsistent (sometimes `skills/canslim-screener/scripts/screen_canslim.py`, sometimes bare `screen_canslim.py` after a `cd`), and the odd `--output-dir ../../../` example invites confusion; it is well above the 3 anchor because the code shown is executable, not pseudocode.

4 / 5

Workflow Clarity

A clear 6-step sequence (verify API access → determine universe → execute script → parse results → analyze candidates → generate report) with several checkpoints: the API-key check in Step 1, the bear-market override gate before any buy recommendation, and error-recovery paths in Troubleshooting (429 retry, Finviz graceful degradation). It is not a 5 because there is no explicit post-run verification step (e.g., sanity-checking the JSON output or confirming expected API-call counts), a minor validation gap for a batch operation; it is clearly above the 3 anchor whose checkpoints are merely implicit.

4 / 5

Progressive Disclosure

Scored against the actual bundle: all four referenced files (canslim_methodology.md, scoring_system.md, fmp_api_endpoints.md, interpretation_guide.md) exist in references/ and are one level deep, each with size, contents, and a 'when to consult' cue; scripts/ and calculators/ are documented per-file. It is not a 5 because content that belongs in references is inlined (the per-calculator scoring thresholds duplicate scoring_system.md, and the full report template bloats SKILL.md), and some bundle files (scripts/check_institutional_endpoint.py, scripts/tests/) are undocumented; it comfortably exceeds the 3 anchor given the clear signaling and navigation.

4 / 5

Total

14

/

20

Passed

Description

82%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 that clearly states what the skill does and when to use it, with explicit trigger phrases and a distinctive named methodology. The only weakness is that it expresses a single screening action rather than enumerating the skill's several capabilities (composite scoring, ranking, report generation), and it omits a few natural synonyms like 'stock screener' or 'relative strength'.

DimensionReasoningScore

Specificity

The description names one concrete action — "Screen US stocks using William O'Neil's CANSLIM growth stock methodology" — which matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is not a 4 because the description does not list several distinct actions (no ranking, reporting, or analysis verbs beyond screening), and not a 2 because the action named is concrete and domain-specific rather than generic.

3 / 5

Completeness

Explicitly answers both questions: 'what' is "Screen US stocks using William O'Neil's CANSLIM growth stock methodology" and 'when' is a full "Use when user requests..." clause listing four concrete trigger conditions. This matches the 5 anchor ("Clearly and explicitly answers both what AND when with concrete trigger phrases"); the 4 anchor's weaker 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Good keyword coverage with natural phrases users would say: "CANSLIM stock screening", "growth stock analysis", "momentum stock identification", "strong earnings and price momentum", "O'Neil's investment system". It falls short of the 5 anchor because a few natural synonyms are missing (e.g., 'stock screener', 'relative strength', 'IBD-style investing', 'breakout stocks'), while clearly exceeding the 3 anchor's 'missing common variations' level.

4 / 5

Distinctiveness Conflict Risk

The CANSLIM/O'Neil framing is a clear niche with distinct triggers (methodology name, 'earnings and price momentum'), matching the 5 anchor 'Clear niche with distinct triggers; minimal conflict risk'. Even though generic stock-screening skills exist, the description anchors on a named methodology, keeping overlap risk minimal rather than merely 'minor'.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (672 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

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.