macro-regime-detector▌
tradermonty/claude-trading-skills · updated Apr 30, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Detect structural macro regime transitions using monthly-frequency cross-asset ratio analysis. This skill identifies 1-2 year regime shifts that inform strategic portfolio positioning.
Macro Regime Detector
Detect structural macro regime transitions using monthly-frequency cross-asset ratio analysis. This skill identifies 1-2 year regime shifts that inform strategic portfolio positioning.
When to Use
- User asks about current macro regime or regime transitions
- User wants to understand structural market rotations (concentration vs broadening)
- User asks about long-term positioning based on yield curve, credit, or cross-asset signals
- User references RSP/SPY ratio, IWM/SPY, HYG/LQD, or other cross-asset ratios
- User wants to assess whether a regime change is underway
Workflow
-
Load reference documents for methodology context:
references/regime_detection_methodology.mdreferences/indicator_interpretation_guide.md
-
Execute the main analysis script:
python3 skills/macro-regime-detector/scripts/macro_regime_detector.pyThis fetches 600 days of data for 9 ETFs + Treasury rates (10 API calls total).
-
Read the generated Markdown report and present findings to user.
-
Provide additional context using
references/historical_regimes.mdwhen user asks about historical parallels.
Prerequisites
- FMP API Key (required): Set
FMP_API_KEYenvironment variable or pass--api-key - Free tier (250 calls/day) is sufficient (script uses ~10 calls)
6 Components
| # | Component | Ratio/Data | Weight | What It Detects |
|---|---|---|---|---|
| 1 | Market Concentration | RSP/SPY | 25% | Mega-cap concentration vs market broadening |
| 2 | Yield Curve | 10Y-2Y spread | 20% | Interest rate cycle transitions |
| 3 | Credit Conditions | HYG/LQD | 15% | Credit cycle risk appetite |
| 4 | Size Factor | IWM/SPY | 15% | Small vs large cap rotation |
| 5 | Equity-Bond | SPY/TLT + correlation | 15% | Stock-bond relationship regime |
| 6 | Sector Rotation | XLY/XLP | 10% | Cyclical vs defensive appetite |
5 Regime Classifications
- Concentration: Mega-cap leadership, narrow market
- Broadening: Expanding participation, small-cap/value rotation
- Contraction: Credit tightening, defensive rotation, risk-off
- Inflationary: Positive stock-bond correlation, traditional hedging fails
- Transitional: Multiple signals but unclear pattern
Output
macro_regime_YYYY-MM-DD_HHMMSS.json— Structured data for programmatic usemacro_regime_YYYY-MM-DD_HHMMSS.md— Human-readable report with:- Current Regime Assessment
- Transition Signal Dashboard
- Component Details
- Regime Classification Evidence
- Portfolio Posture Recommendations
Relationship to Other Skills
| Aspect | Macro Regime Detector | Market Top Detector | Market Breadth Analyzer |
|---|---|---|---|
| Time Horizon | 1-2 years (structural) | 2-8 weeks (tactical) | Current snapshot |
| Data Granularity | Monthly (6M/12M SMA) | Daily (25 business days) | Daily CSV |
| Detection Target | Regime transitions | 10-20% corrections | Breadth health score |
| API Calls | ~10 | ~33 | 0 (Free CSV) |
Script Arguments
python3 macro_regime_detector.py [options]
Options:
--api-key KEY FMP API key (default: $FMP_API_KEY)
--output-dir DIR Output directory (default: current directory)
--days N Days of history to fetch (default: 600)
Resources
references/regime_detection_methodology.md— Detection methodology and signal interpretationreferences/indicator_interpretation_guide.md— Guide for interpreting cross-asset ratiosreferences/historical_regimes.md— Historical regime examples for context
How to use macro-regime-detector on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add macro-regime-detector
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches macro-regime-detector from GitHub repository tradermonty/claude-trading-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate macro-regime-detector. Access the skill through slash commands (e.g., /macro-regime-detector) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★44 reviews- ★★★★★Pratham Ware· Dec 28, 2024
Registry listing for macro-regime-detector matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Alexander Gupta· Dec 16, 2024
macro-regime-detector is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Amelia Tandon· Dec 8, 2024
Solid pick for teams standardizing on skills: macro-regime-detector is focused, and the summary matches what you get after install.
- ★★★★★Daniel Johnson· Dec 8, 2024
macro-regime-detector fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Aarav Yang· Nov 27, 2024
macro-regime-detector has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Olivia Bansal· Nov 19, 2024
Registry listing for macro-regime-detector matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Olivia Gill· Nov 7, 2024
macro-regime-detector reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Sofia Gupta· Oct 26, 2024
I recommend macro-regime-detector for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Aanya Gill· Oct 18, 2024
Keeps context tight: macro-regime-detector is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Daniel Khanna· Oct 10, 2024
macro-regime-detector fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 44