market-regimes
Market regime detection and regime-specific trading strategies. Use when analyzing market conditions to select appropriate strategy.
61
41%
Does it follow best practices?
Impact
100%
1.56xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xhubed/agent-trading-arena/market-regimes/SKILL.mdQuality
Discovery
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 adequately identifies its domain and includes an explicit 'Use when' trigger clause, which is good. However, it lacks specific concrete actions (e.g., what regime detection methods, what types of strategies) and could benefit from more natural trigger terms that users would actually say. The description is functional but could be more distinctive and detailed.
Suggestions
Add specific concrete actions like 'Classifies market states (bull, bear, sideways, high-volatility), selects regime-appropriate trading strategies, and adjusts position sizing based on detected regime.'
Expand trigger terms to include natural variations: 'market state', 'bull/bear market', 'volatility regime', 'regime switching', 'trend identification', 'market environment'.
| Dimension | Reasoning | Score |
|---|---|---|
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 | Answers both 'what' (market regime detection and regime-specific trading strategies) and 'when' (Use when analyzing market conditions to select appropriate strategy) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'market regime', 'trading strategies', and 'market conditions', but misses common natural variations users might say such as 'bull market', 'bear market', 'volatility regime', 'market state', 'trend detection', or 'regime switching'. | 2 / 3 |
Distinctiveness Conflict Risk | The concept of 'market regime detection' is fairly specific, but 'trading strategies' and 'analyzing market conditions' are broad enough to potentially overlap with general trading analysis, backtesting, or portfolio management skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
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 a data dump of 32 regime observations presented as a flat list with massive redundancy—the same regime types repeat with slightly different observations that could be consolidated. It lacks actionable decision criteria for identifying regimes, has no executable code or structured decision logic, and the monolithic format makes it extremely difficult to navigate or use effectively.
Suggestions
Consolidate duplicate regime types (e.g., 8 'Moderate Bull' entries, 10 'Trending Up' entries) into single entries per regime with synthesized recommendations and key statistics.
Add concrete regime identification criteria (e.g., 'Trending Up: all assets >+2% over 24h, volatility index > X') so Claude can actually classify current conditions.
Create a summary decision table at the top mapping regime → action → trade frequency → position bias, with detailed observations moved to a separate reference file.
Replace the vague 'How to Use' workflow with specific steps including data inputs needed, classification thresholds, and validation checkpoints for regime transitions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and repetitive. The same regime (e.g., 'Moderate Bull', 'Trending Up') appears many times with overlapping advice. 32 patterns with near-identical observations could be consolidated into 5-6 regime summaries. Most tokens are spent on redundant data points that could be distilled. | 1 / 3 |
Actionability | Provides some concrete guidance (trade frequency ranges, asset selection, position sizing percentages) but lacks executable code, specific commands, or structured decision logic. The advice is descriptive rather than prescriptive—it tells what happened historically rather than giving clear if/then rules to follow. | 2 / 3 |
Workflow Clarity | The 4-step 'How to Use' section is vague ('identify the current market regime using price action and volatility') with no concrete criteria for regime identification, no validation checkpoints, and no feedback loop for monitoring regime changes. There's no clear decision tree or threshold-based classification system. | 1 / 3 |
Progressive Disclosure | Monolithic wall of 32 pattern entries inline with no references to external files, no summary table linking to details, and no hierarchical organization. The content would benefit enormously from a summary table with links to regime-specific detail files. | 1 / 3 |
Total | 5 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
868a866
- 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.