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

32%Weight 40%Scale 1-5

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

The skill is an auto-generated data dump of repetitive regime patterns with no bundle files, no validation workflow, and weak actionability. It functions as a reference table rather than actionable guidance, and its bulk should be externalized.

Suggestions

Move the per-regime pattern entries into a separate data file (e.g. references/regimes.json or REGIMES.md) and keep SKILL.md as a concise overview that links to it, lifting progressive disclosure and conciseness.

Deduplicate and consolidate the repeated regime sections into one canonical entry per regime (Moderate Bull, Trending Up, etc.) instead of 30 overlapping copies.

Replace the vague 4-step usage list with an explicit, validated workflow: identify regime via specific price-action/volatility criteria, select the matching strategy, define risk/position limits, then define a re-evaluation trigger to detect regime changes.

Dimension	Reasoning	Score
Conciseness	The body is a 250+ line dump of ~30 near-identical regime entries with heavily duplicated labels (e.g. 'Moderate Bull' repeated 8 times, 'Trending Up' 10 times) and verbose, repetitive blockquotes; this is noticeably padded rather than the lean overview a SKILL.md should be.	2 / 5
Actionability	Each regime offers a semi-concrete directive (e.g. '<25 trades/24h', 'avoid shorting entirely', 'prefer BNB'), which is more than abstract description, but there are no executable steps, commands, or a clear procedure to apply them.	3 / 5
Workflow Clarity	A 4-step 'How to Use' sequence exists but steps are vague ('Adjust your trading approach accordingly') and there are no validation checkpoints for a financially consequential activity; the missing-validation cap and poorly defined steps keep this at the 'rough sequence, many gaps' anchor.	2 / 5
Progressive Disclosure	No bundle files exist and the entire regime-pattern dataset is inlined as one monolithic block that clearly belongs in a separate data file; section headers alone do not compensate for the lack of file separation or navigation.	2 / 5
	Total	9 / 20 Passed

Description

62%Weight 40%Scale 1-5

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 cleanly answers both what and when in third person, but the capabilities and trigger terms are generic rather than comprehensive. It is solid and distinct but leaves room for more concrete actions and richer natural keywords.

Suggestions

List concrete capabilities explicitly (e.g. detect regime from price action/volatility, map regime to a strategy, monitor for regime transitions) to lift specificity toward 5.

Add natural trigger phrases users would actually say (e.g. 'market conditions', 'bull/bear/choppy market', 'which trading strategy to use', 'regime change') to improve trigger-term coverage.

Tighten the 'when' clause with concrete triggers such as 'Use when selecting a trading strategy for the current market regime or deciding whether to trade at all'.

Dimension	Reasoning	Score
Specificity	Names the domain ('market regime detection') and two concrete actions (detection, regime-specific strategies), but does not enumerate several specific capabilities; fits the '1-2 concrete actions' anchor rather than the 'lists several specific actions' anchor above.	3 / 5
Completeness	Explicitly states both what ('Market regime detection and regime-specific trading strategies') and when ('Use when analyzing market conditions to select appropriate strategy'); the 'when' is present but somewhat generic, so it does not reach the concrete-trigger-phrase level of 5.	4 / 5
Trigger Term Quality	Includes relevant terms like 'market conditions', 'analyzing market conditions', and 'strategy', but these are generic and miss natural synonyms or concrete variations a user might say; not comprehensive enough for a 4.	3 / 5
Distinctiveness Conflict Risk	Targets a fairly specific niche (market regimes / trading strategy selection) with low conflict risk; only minor overlap with adjacent trading-analysis skills keeps it just below 5.	4 / 5
	Total	14 / 20 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: 2f57aec

Reviewed: about 22 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.