market-regimes

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

1.56x

Quality

47%

Does it follow best practices?

Impact

100%

1.56x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xhubed/agent-trading-arena/market-regimes/SKILL.md

Quality

Content

27%

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

The content is essentially an auto-generated log of observed trading patterns: repetitive, poorly organized, and padded with zero-observation metadata. It offers some concrete numbers but lacks a clean workflow with validation and is far from token-efficient.

Suggestions

Collapse the ~30 near-duplicate entries into one consolidated section per regime type (Trending Up, Moderate Bull, Moderate Bearish, Mixed Choppy, Sideways, Low Volatility) to fix the monolithic-organization and conciseness problems.

Drop or relocate the 'Total observations: 0' metadata and per-entry dates into a separate data file or an 'old patterns' section, since they are time-sensitive and add no actionable value inline.

Add explicit validation checkpoints to the 'How to Use' workflow (e.g. confirm regime with a second indicator before acting, re-check after N hours) so workflow_clarity can reach 3.

Dimension	Reasoning	Score
Conciseness	The body is a ~250-line data dump of ~30 near-duplicate regime entries padded with redundant 'Total observations: 0' metadata and inline time-sensitive dates (2026-01-17), none placed in an old-patterns section, matching anchor 1's verbose padded-with-unnecessary-context.	1 / 3
Actionability	Some entries give concrete numbers ('120-200 trades/24h', '2% equity, 2:1 R:R'), but the 'How to Use' steps are abstract ('Adjust your trading approach accordingly') and many entries are vague, so guidance is incomplete rather than copy-paste ready.	2 / 3
Workflow Clarity	A 4-step 'How to Use This Skill' sequence is present, but it lacks validation checkpoints and the task (trading) is risky, so per the rubric's cap workflow_clarity cannot exceed 2.	2 / 3
Progressive Disclosure	The skill is a monolithic wall of text with duplicate headers (repeated 'Moderate Bull', 'Trending Up'), no grouping by regime, and no external references despite being well over 50 lines, matching anchor 1's monolithic poorly-organized case.	1 / 3
	Total	6 / 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 is well-formed: it uses third person, states a clear domain, and includes an explicit 'Use when' clause that secures a high completeness score. Its weakness is trigger-term coverage and specificity, where the language stays high-level rather than enumerating concrete actions or natural keyword variations.

Suggestions

Add concrete actions to the description, e.g. 'Detect the current market regime and select a matching trading strategy' to lift specificity toward 3.

Broaden trigger terms with natural phrasings users would say, e.g. 'trending, choppy, or sideways markets', 'bull/bear regime', so trigger_term_quality reaches full coverage.

Sharpen the trigger to the regime niche (e.g. 'Use when deciding whether to trade or hold based on the current market regime') to reduce overlap with generic trading skills.

Dimension	Reasoning	Score
Specificity	The phrase 'Market regime detection and regime-specific trading strategies' names the domain and two high-level actions, but it does not list multiple specific concrete actions the way anchor 3 requires.	2 / 3
Completeness	It states what ('Market regime detection and regime-specific trading strategies') and an explicit when ('Use when analyzing market conditions to select appropriate strategy'), satisfying the anchor 3 requirement of answering both with an explicit trigger.	3 / 3
Trigger Term Quality	'market conditions' and 'trading strategy' are natural terms a user might say, but coverage is limited and lacks common variations, matching anchor 2 rather than the broad coverage of anchor 3.	2 / 3
Distinctiveness Conflict Risk	'Market regime detection' is a reasonably clear niche, but the trigger 'analyzing market conditions' is somewhat generic and could overlap with broader trading skills, matching anchor 2 rather than a fully distinct niche.	2 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Path: data/skills-md/0xhubed/agent-trading-arena/market-regimes/SKILL.md
Commit: 9eeba1e

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

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.