market-regimes
Market regime detection and regime-specific trading strategies. Use when analyzing market conditions to select appropriate strategy.
70
Quality
54%
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 provides a clear structure with both capability and trigger guidance, meeting the completeness requirement well. However, it lacks specific concrete actions (what types of regimes, what specific strategies) and could benefit from more natural trigger terms that users would actually say when needing this skill.
Suggestions
Add specific regime types and actions, e.g., 'Detects bull/bear markets, high/low volatility periods, and trending vs ranging conditions'
Expand trigger terms to include natural phrases like 'market state', 'current market environment', 'volatility regime', 'trend detection'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (market regime detection, trading strategies) and mentions some actions (analyzing, selecting), but lacks concrete specifics about what regime detection entails or what strategies are available. | 2 / 3 |
Completeness | Clearly answers both what (market regime detection and regime-specific trading strategies) and when (analyzing market conditions to select appropriate strategy) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'market regime', 'trading strategies', 'market conditions', but misses common variations users might say such as 'bull market', 'bear market', 'volatility', 'trend analysis', or 'market state'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to regime detection but could overlap with general trading analysis skills, market analysis skills, or strategy selection tools. The term 'trading strategies' is broad enough to cause potential conflicts. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides useful market regime concepts and specific trading recommendations with confidence levels, but suffers from poor organization with duplicate regime names (Moderate Bull appears 10x, Trending Up 12x) creating a confusing, bloated document. The content would benefit from consolidation of similar regimes and separation of detailed patterns into referenced files.
Suggestions
Consolidate duplicate regime entries (e.g., merge all 'Moderate Bull' patterns into a single section with sub-bullets for different observations)
Move detailed regime patterns to a separate PATTERNS.md file, keeping only summary guidance in the main skill
Add a regime identification workflow with specific indicators/thresholds and validation steps for confirming regime classification
Include executable code snippets for regime detection (e.g., volatility calculation, trend identification logic)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is moderately efficient but contains significant redundancy - 'Moderate Bull' regime appears 10 times with overlapping advice, and 'Trending Up' appears 12 times. The repetitive structure inflates token count without proportional value. | 2 / 3 |
Actionability | Provides specific guidance like trade frequency ranges (120-200 trades/24h) and position sizing (25% equity), but lacks executable code or concrete implementation steps. The advice is directional rather than copy-paste ready. | 2 / 3 |
Workflow Clarity | The 4-step 'How to Use' section provides a basic workflow, but lacks validation checkpoints or feedback loops for regime detection errors. No guidance on what to do if regime identification is uncertain or changes mid-trade. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with 32 regime patterns listed inline. No references to external files for detailed strategies, no collapsible sections, and duplicate regime names make navigation difficult. | 1 / 3 |
Total | 7 / 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
5342bca
- 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.