skills/macro-regime-detector/SKILL.md
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.
npx skillsauth add MileniumTick/skills macro-regime-detectorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Load reference documents for methodology context:
references/regime_detection_methodology.mdreferences/indicator_interpretation_guide.mdExecute the main analysis script:
python3 skills/macro-regime-detector/scripts/macro_regime_detector.py
This 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.md when user asks about historical parallels.
FMP_API_KEY environment variable or pass --api-key| # | 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 |
macro_regime_YYYY-MM-DD_HHMMSS.json — Structured data for programmatic usemacro_regime_YYYY-MM-DD_HHMMSS.md — Human-readable report with:
| 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) |
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)
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 contextdevelopment
Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.
development
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.
development
Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.
tools
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.