CtrlK
BlogDocsLog inGet started
Tessl Logo

market-regimes

Market regime detection and regime-specific trading strategies. Use when analyzing market conditions to select appropriate strategy.

61

1.56x
Quality

41%

Does it follow best practices?

Impact

100%

1.56x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./data/skills-md/0xhubed/agent-trading-arena/market-regimes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

14%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is an auto-generated dump of 32 trading observations that suffers from extreme redundancy, poor organization, and lack of actionable structure. The same regime types appear repeatedly with overlapping advice, all based on single observations with zero confirmed samples. The content would benefit enormously from consolidation by regime type, a clear regime detection algorithm, and a structured decision framework rather than a flat list of historical anecdotes.

Suggestions

Consolidate duplicate regime types into single entries that synthesize all observations (e.g., one 'Moderate Bull' section combining all 7 entries into a coherent strategy with key principles)

Add a concrete regime detection algorithm or decision tree with specific thresholds (e.g., 'If all assets >+2%: Trending Up; if mixed ±1%: Mixed Choppy') so Claude can actually identify regimes

Replace the vague 4-step workflow with a structured decision framework: detect regime → validate with specific criteria → select strategy → set specific exit/monitoring conditions

Add a summary lookup table at the top mapping each regime to its core strategy in one line, with detailed sections below for reference

DimensionReasoningScore

Conciseness

Extremely repetitive - the same regime types (especially 'Moderate Bull' and 'Trending Up') appear many times with overlapping advice (e.g., 'asset selection matters' repeated 5+ times, 'zero-trade strategies preserve capital' repeated 4+ times). This could be condensed to ~1/4 the length by grouping observations per regime type. All observations have 0 samples and 'seen 1x', making most entries low-value noise.

1 / 3

Actionability

The content provides some concrete guidance (specific trade frequencies, asset selection, position sizing percentages) but lacks executable code, commands, or structured decision logic. The advice is descriptive rather than prescriptive - it tells what happened historically but doesn't provide a clear algorithm or decision tree for regime detection or strategy selection.

2 / 3

Workflow Clarity

The 4-step 'How to Use' section is extremely vague ('Identify the current market regime using price action and volatility' - how exactly?). There's no regime detection algorithm, no validation checkpoints, no criteria for when to switch regimes, and no feedback loop for monitoring regime changes. The workflow is essentially 'figure it out, then look it up.'

1 / 3

Progressive Disclosure

This is a monolithic wall of 32 pattern entries with no organization beyond flat listing. Duplicate regime types (7 'Moderate Bull', 10 'Trending Up') are not grouped or consolidated. There are no references to external files, no summary table for quick lookup, and no hierarchical structure to help navigate the content efficiently.

1 / 3

Total

5

/

12

Passed

Description

67%

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 covers the basics with a clear 'what' and 'when' clause, establishing it as a regime-detection focused trading skill. However, it lacks specific concrete actions (e.g., what regime detection entails, what strategies are applied) and could benefit from richer trigger terms that users would naturally use when seeking this capability. The distinctiveness is moderate—it could be confused with general market analysis or trading strategy skills.

Suggestions

Add specific concrete actions such as 'classify market into bull/bear/sideways/high-volatility regimes, select momentum or mean-reversion strategies based on detected regime, generate regime transition signals'.

Expand trigger terms to include natural user language like 'bull market', 'bear market', 'volatility regime', 'market state', 'trend identification', 'regime switching', or 'adaptive strategy selection'.

Differentiate from general trading/market analysis skills by specifying the unique methodology or outputs, e.g., 'Uses hidden Markov models or statistical indicators to classify regimes and map them to pre-defined strategy sets'.

DimensionReasoningScore

Specificity

Names the domain (market regime detection, trading strategies) and some actions (analyzing market conditions, selecting strategy), but doesn't list specific concrete actions like 'classify bull/bear/sideways markets, backtest regime-specific signals, generate allocation recommendations.'

2 / 3

Completeness

Explicitly answers both 'what' (market regime detection and regime-specific trading strategies) and 'when' ('Use when analyzing market conditions to select appropriate strategy'), satisfying the requirement for an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes some relevant terms like 'market regime', 'trading strategies', and 'market conditions', but misses common user variations such as 'bull market', 'bear market', 'volatility regime', 'trend detection', 'market state', or 'regime change'.

2 / 3

Distinctiveness Conflict Risk

The term 'trading strategies' is fairly broad and could overlap with other trading/finance skills. While 'regime detection' is somewhat distinctive, 'analyzing market conditions' could trigger for general market analysis skills as well.

2 / 3

Total

9

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
NeverSight/skills_feed
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.