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 covers both what the skill does and when to use it, with an explicit 'Use when' clause. However, it lacks specificity in the concrete actions it performs and could benefit from more natural trigger terms that users would actually say. The domain is somewhat niche but the phrasing is broad enough to risk overlap with general trading or market analysis skills.
Suggestions
Add specific concrete actions such as 'classify bull/bear/sideways/high-volatility regimes, select regime-appropriate strategies, backtest regime transitions'
Expand trigger terms to include natural variations like 'bull market', 'bear market', 'volatility regime', 'market state', 'trend identification', 'regime switching'
| 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 change'. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'trading strategies' is fairly broad and could overlap with other trading/finance skills. 'Market regime detection' is more distinctive, but 'analyzing market conditions' could trigger for general market analysis skills as well. | 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 an auto-generated data dump of 32 trading observations masquerading as a strategy guide. Its core problems are massive redundancy (same regime types repeated with overlapping advice), lack of actionable implementation details (no code, no detection criteria, no decision trees), and poor organization that forces the reader to scan through all 32 entries to find relevant guidance. The content needs fundamental restructuring: consolidate by regime type, add regime detection criteria, and provide executable implementation guidance.
Suggestions
Consolidate duplicate regime entries (e.g., merge 10 'Moderate Bull' entries into one with synthesized recommendations and a confidence-weighted summary)
Add concrete regime detection criteria with specific thresholds (e.g., 'Trending Up: >2% gain across 3+ assets in 24h, volatility > X') so the workflow step 'Identify the current market regime' becomes actionable
Provide a decision tree or lookup table at the top that maps observable market conditions to regime types and their top-line strategy, with detailed evidence below
Add validation steps: how to confirm regime identification is correct, when to re-evaluate, and what to do when signals conflict between regime types
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely repetitive - there are 10 'Trending Up' entries, 10 'Moderate Bull' entries, and 3 'Mixed Choppy' entries, many saying nearly the same thing (e.g., 'asset selection matters' repeated 6+ times, 'zero-trade strategies preserve capital' repeated 4+ times). This massive redundancy wastes tokens. The content could be condensed to ~1/4 its size by consolidating duplicate regime entries. | 1 / 3 |
Actionability | The strategies provide some concrete guidance (specific trade frequencies, asset preferences, position sizing percentages), but there are no executable code examples, no specific commands or API calls, and no clear decision tree for identifying which regime is active. The guidance is descriptive rather than instructional - it tells what happened historically rather than giving copy-paste-ready implementation steps. | 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 are no validation checkpoints, no criteria for regime identification, no feedback loops for when regime detection is wrong, and no clear decision process for choosing among multiple entries for the same regime (e.g., which of the 10 'Moderate Bull' entries to follow). | 1 / 3 |
Progressive Disclosure | This is a monolithic wall of 32 pattern entries with no organization beyond flat listing. Duplicate regime types are not consolidated, there are no references to external files, and no hierarchical structure. The content would benefit enormously from grouping by regime type with summary tables and detailed entries in separate 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
25d5403
- 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.