sector-analyst

This skill should be used when analyzing sector rotation patterns and market cycle positioning. It fetches sector uptrend data from CSV (no API key required) and optionally accepts chart images for supplementary analysis. Use this skill when the user requests sector rotation analysis, cyclical vs defensive assessment, overbought/oversold identification, or market cycle phase estimation. All analysis and output are conducted in English.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/sector-analyst/SKILL.md

Quality

Content

71%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.

A well-architected skill body with strong progressive disclosure, an explicit sequenced workflow, and executable commands. The main weakness is conciseness: the body re-teaches domain concepts and embeds a long output template that Claude largely already knows how to produce.

Suggestions

Move the full Markdown output template and probability guidelines into references/sector_rotation.md (or a separate output-format reference), keeping only a compact example in SKILL.md.

Trim or remove the 'Key Analysis Principles' and 'Probability Guidelines' sections, which restate knowledge Claude already has and which duplicate the referenced knowledge base.

Add one explicit validation checkpoint (e.g. confirm the script exited cleanly and the CSV freshness date is acceptable before proceeding to interpretation) to push workflow clarity to a 5.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and well-organized, but the body contains material Claude already knows (e.g. explaining market cycle phases, restating probability ranges, restating principles like 'Objectivity First') and a somewhat padded Output Format template that could be tightened or moved to a reference file.	3 / 5
Actionability	Provides concrete, executable commands (`python3 scripts/analyze_sector_rotation.py` with --json/--save/--output-dir flags) and a precise output template; minor gaps are the non-executable prose around chart-image analysis which lacks concrete tooling.	4 / 5
Workflow Clarity	Clear five-step sequenced workflow with explicit per-step instructions and a freshness-check checkpoint; the destructive/batch cap does not apply (read-only analysis), but explicit validation steps (e.g. 'verify output parses') are only implicit rather than stated.	4 / 5
Progressive Disclosure	Clear overview pointing one level deep to real bundle files (`references/sector_rotation.md`, `scripts/analyze_sector_rotation.py`, three sample chart assets) that all exist; bulk knowledge base correctly externalized rather than inlined.	5 / 5
	Total	16 / 20 Passed

Description

83%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, well-structured description that clearly states both capability and triggering conditions using natural user language. Minor improvements in synonym coverage and trimming the somewhat formulaic 'This skill should be used when' opening would push it higher.

Suggestions

Lead with the third-person action verbs ('Fetches sector uptrend data...') rather than the meta 'This skill should be used when' phrasing to strengthen specificity and voice.

Add a couple of natural synonyms users might say (e.g. 'sector performance', 'relative strength') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('fetches sector uptrend data from CSV', 'accepts chart images for supplementary analysis') tied to specific analytical outputs (rankings, cyclical vs defensive assessment, overbought/oversold, cycle phase), with only minor coverage gaps relative to the full feature set.	4 / 5
Completeness	Explicitly answers both 'what' (fetches sector uptrend data, ranks sectors, calculates risk regimes, identifies overbought/oversold, estimates cycle phase) and 'when' ('Use this skill when the user requests...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user phrases like 'sector rotation analysis', 'cyclical vs defensive assessment', 'overbought/oversold identification', and 'market cycle phase estimation'; good coverage though it omits a few synonyms (e.g. 'sector performance', file extensions) a user might say.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (sector rotation / market cycle positioning) with distinct triggers and a named data source, minimizing overlap risk; minor overlap possible with general market-analysis skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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/sector-analyst/SKILL.md
Commit: 51c7907

Reviewed: ~7 hours ago

Table of Contents

Discovery Implementation Validation

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.