CtrlK
BlogDocsLog inGet started
Tessl Logo

technical-analyst

This skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs. Use this skill when the user provides chart images and requests technical analysis, trend identification, support/resistance levels, scenario planning, or probability assessments based purely on chart data without consideration of news or fundamental factors.

75

Quality

92%

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

85%

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 clear sequenced workflows, explicit validation/fail-closed checkpoints, and well-structured one-level-deep progressive disclosure. Its only weakness is conciseness: it re-explains basic technical-analysis concepts Claude already knows.

Suggestions

Trim or collapse the 'Core Principles', 'Quality Standards', and 'When to Use' sections and remove definitions of concepts Claude already knows (e.g., what hammers/shooting stars are) to reduce padding.

Move the per-element breakdowns in Steps 3.1-3.6 into references/technical_analysis_framework.md and keep only the high-level sequence in SKILL.md, since that file is already referenced for the detailed methodology.

Consolidate the repeated trigger phrasing between the description, 'When to Use', and 'Example Usage Scenarios' to avoid restating the same activation criteria multiple times.

DimensionReasoningScore

Conciseness

The ~390-line body restates concepts Claude already knows (defining trend/S/R/candlestick patterns like 'hammers, shooting stars, engulfing patterns') and repeats triggers in 'When to Use' and 'Core Principles' sections, so while much of it is efficient it could be tightened to avoid padding; this is mostly efficient with some unnecessary explanation rather than fully lean.

2 / 3

Actionability

It provides concrete file reads ('Read: references/technical_analysis_framework.md'), executable CLI commands with full flags, a precise YAML output contract, and exact file-naming conventions, making the guidance copy-paste ready.

3 / 3

Workflow Clarity

Steps 1-6 are clearly sequenced with an explicit checkpoint ('Complete and save each report before moving to the next', 'Do not batch analyses'), and the contrarian mode adds fail-closed validation ('INSUFFICIENT_DATA never advances the pipeline') and a conservative disagreement rule, matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

The body is a clear overview pointing to one-level-deep, well-signaled references — all verified to exist (references/technical_analysis_framework.md, references/contrarian-confirmation-checklist.md, assets/analysis_template.md, scripts/check_weekly_price_action.py) — with content appropriately split into framework, template, checklist, and script files.

3 / 3

Total

11

/

12

Passed

Description

100%

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, trigger-rich, complete (explicit what + when), and clearly distinct in its niche. It is one of the strongest descriptions, using third-person voice throughout with no first/second-person penalty.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions such as 'analyzing weekly price charts', 'technical analysis', 'trend identification', 'support/resistance levels', 'scenario planning', and 'probability assessments', matching the score-3 anchor of multiple specific concrete actions.

3 / 3

Completeness

It explicitly answers both what (weekly chart analysis producing trends, S/R, scenarios) and when via an explicit 'Use this skill when the user provides chart images and requests...' trigger clause, satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

Natural user-facing terms are well covered ('technical analysis', 'trend identification', 'support/resistance levels', 'scenario planning', 'probability assessments', 'chart images'), giving good coverage of phrases users would actually say.

3 / 3

Distinctiveness Conflict Risk

The weekly-timeframe, pure-chart-data, no-news/fundamentals framing carves a clear niche unlikely to conflict with other skills, matching the distinct-triggers score-3 anchor.

3 / 3

Total

12

/

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.