macro-regime-detector

Detect structural macro regime transitions (1-2 year horizon) using cross-asset ratio analysis. Analyze RSP/SPY concentration, yield curve, credit conditions, size factor, equity-bond relationship, and sector rotation to identify regime shifts between Concentration, Broadening, Contraction, Inflationary, and Transitional states. Run when user asks about macro regime, market regime change, structural rotation, or long-term market positioning.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%

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

The body is well-structured and actionable with executable commands and appropriately split one-level-deep references. Its main weaknesses are minor trigger redundancy with the description and the absence of validation/error-recovery checkpoints in a data-fetching-and-scoring workflow.

Suggestions

Remove the "When to Use" section or trim it to non-duplicate cases, since its bullets restate the description's triggers and add token cost without new information.

Add an explicit validation/error-recovery step to the workflow, e.g. how to handle FMP API failures or insufficient yfinance fallback data before presenting the regime result.

Tighten the FMP-key fallback paragraph to a single sentence noting the yfinance fallback does not remove the FMP key requirement.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tight component/regime tables and an executable workflow, but the "When to Use" bullets largely restate the description's triggers and the FMP-key fallback paragraph is somewhat verbose, so it could be tightened rather than fully lean.	2 / 3
Actionability	Provides a copy-paste-ready command ("uv run python3 .../macro_regime_detector.py --output-dir reports/"), explicit prerequisites (FMP_API_KEY), a script-arguments table, and named output files, matching the score-3 anchor for fully executable guidance.	3 / 3
Workflow Clarity	The 4-step sequence is clearly ordered, but for a pipeline making ~10 live API calls and producing a scored regime classification there are no validation or error-recovery checkpoints (e.g., what to do on API failure or insufficient fallback data), which caps workflow clarity at 2 per the rubric.	2 / 3
Progressive Disclosure	The body is a clear overview pointing one level deep to real, well-signaled reference files (regime_detection_methodology.md, indicator_interpretation_guide.md, historical_regimes.md) listed in both Workflow and Resources, with content appropriately split into references and scripts.	3 / 3
	Total	10 / 12 Passed

Description

100%

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 concise, specific, and complete: it names concrete actions, lists natural trigger terms, and explicitly pairs what-it-does with when-to-run guidance in third person. It carves out a distinct niche unlikely to conflict with adjacent market-analysis skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions such as "Detect structural macro regime transitions" and "Analyze RSP/SPY concentration, yield curve, credit conditions, size factor, equity-bond relationship, and sector rotation", matching the score-3 anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ("Detect structural macro regime transitions...using cross-asset ratio analysis") and when ("Run when user asks about macro regime, market regime change, structural rotation, or long-term market positioning"), matching the score-3 anchor with an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes natural user-facing terms like "macro regime", "market regime change", "structural rotation", "long-term market positioning", and "RSP/SPY" that a user would naturally say, giving good coverage as required by the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (1-2 year structural regime transitions via named cross-asset ratios) with distinct triggers unlikely to fire for tactical or breadth skills, matching the score-3 anchor.	3 / 3
	Total	12 / 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: tradermonty/claude-trading-skills
Path: skills/macro-regime-detector/SKILL.md
Commit: 62a1635

Reviewed: 5 days 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.