CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

theme-detector

Detect and analyze trending market themes across sectors. Use when user asks about current market themes, trending sectors, sector rotation, thematic investing, what themes are hot or cold, or wants to identify bullish and bearish market narratives with lifecycle analysis.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 highly actionable, well-sequenced operational skill document with concrete commands, input contracts, and verified bundle references. Its main weakness is token efficiency: large inline duplications (JSON output example, report template) and internal inconsistencies ("3-Dimensional" list of 5, overlapping Overview/Key Features) that could be moved to references or trimmed. Workflow validation is present at the front end but lacks an explicit post-execution recovery loop.

Suggestions

Replace the ~70-line inline JSON output example with a brief field-highlight table or a few key excerpts, and point to references/theme_detection_methodology.md (or a dedicated output-schema reference) for the full structure.

Remove the full report template in Step 6 and reference assets/report_template.md directly, since the template already exists as a bundle file — this removes a direct duplication.

Fix the "3-Dimensional Scoring Model" heading (it enumerates 5 numbered items) and merge the Overview's "Key Features" list with the numbered model list to eliminate redundant framing; also move the version/date footer into a deprecation/CHANGE note context per time-sensitive-info guidance.

DimensionReasoningScore

Conciseness

The body is mostly operational, but noticeably padded in places: a ~70-line inline JSON output example, a full report template in Step 6 that duplicates assets/report_template.md, a "Key Features" list that repeats the Overview, and a "3-Dimensional Scoring Model" heading that actually enumerates 5 items. The version/date footer also embeds time-sensitive information. This fits 'mostly efficient but could be tightened' rather than the leaner anchor 4.

3 / 5

Actionability

Fully executable throughout: copy-paste bash invocations with every flag combination, exact file paths, precise input contracts with field names and numeric thresholds (e.g., "return_5d >= 20", "relative_volume >= 2.0"), expected execution times, and concrete WebSearch query patterns. This matches the copy-paste-ready anchor 5.

5 / 5

Workflow Clarity

Six clearly sequenced steps with an explicit environment-verification checkpoint (Step 1) and documented failure behavior (CLI exits 1 with upgrade guidance, uv fallback for mixed-Python, public-scraper fallback). It falls short of anchor 5 because there is no explicit in-workflow error-recovery loop after script execution or output validation step.

4 / 5

Progressive Disclosure

Good structure: all four references (cross_sector_themes.md, thematic_etf_catalog.md, theme_detection_methodology.md, finviz_industry_codes.md), the report template asset, and the scripts directory exist and are clearly signaled in Step 5 and the Resources section, one level deep. Minor gaps: the full JSON output schema and report template are inlined in SKILL.md rather than split out, which is content that already lives in bundle files.

4 / 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 well-crafted description with an explicit capability statement and a rich, natural-language 'Use when' trigger clause covering multiple phrasings users would actually say. Distinctiveness is good, with only slight overlap risk against sibling sector-analysis skills. Minor improvements possible by naming a couple more output capabilities and synonyms.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Detect and analyze trending market themes across sectors", "identify bullish and bearish market narratives with lifecycle analysis" — with only minor coverage gaps (e.g., no mention of ETF/leadership outputs). It sits above anchor 3 (1-2 actions) because multiple distinct capabilities are named, but below anchor 5 since the actions are not fully comprehensive.

4 / 5

Completeness

Explicitly answers both: what it does ("Detect and analyze trending market themes across sectors") and when to use it ("Use when user asks about current market themes, trending sectors, sector rotation, thematic investing, what themes are hot or cold..."). Clear 'what' plus a concrete 'Use when' clause with trigger phrases matches the anchor 5 example.

5 / 5

Trigger Term Quality

Strong natural phrases users would say: "current market themes", "trending sectors", "sector rotation", "thematic investing", "what themes are hot or cold". A few natural variations are missing (e.g., "crowded trades", "market narrative shifts", "sector performance"), keeping it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The theme/narrative/lifecycle niche is clearly distinct from generic document or data skills, and triggers like "thematic investing" and "market narratives" are specific. Minor overlap risk remains with sector-analysis skills via "trending sectors" and "sector rotation", so it does not fully reach the minimal-conflict anchor 5.

4 / 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 (516 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

tradermonty/claude-trading-skills

Path

skills/theme-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.