market-regime
Analyzes financial market regimes to identify trends, volatility, and shifts in asset classes.
What this skill does
# market-regime
## Purpose
This skill analyzes financial market regimes to detect trends, volatility, and shifts in asset classes like stocks, bonds, or cryptocurrencies. It processes historical data to classify regimes (e.g., bull, bear, sideways) and provides actionable insights for trading or risk management.
## When to Use
Use this skill when you need to evaluate market conditions for decision-making, such as before executing trades, assessing portfolio risk, or building predictive models. Apply it in volatile markets, during economic events, or for backtesting strategies. Avoid if you lack historical data access, as it requires at least 1 year of price data.
## Key Capabilities
- Identifies market regimes using statistical methods like moving averages and Bollinger Bands.
- Analyzes volatility with metrics such as standard deviation or VIX equivalents.
- Detects trend shifts by comparing short-term vs. long-term indicators.
- Supports multiple asset classes via APIs or data feeds (e.g., Yahoo Finance, Alpha Vantage).
- Outputs regime classifications, volatility scores, and regime duration forecasts.
## Usage Patterns
Invoke this skill via CLI for quick analysis or integrate it into Python scripts for automated workflows. Always provide asset symbols and time periods. For CLI, use synchronous calls; for API, handle asynchronous responses. Configure with a JSON file for custom parameters, e.g., set thresholds for volatility detection.
To run a basic analysis:
1. Set environment variable for authentication: `export OPENCLAW_API_KEY=your_api_key_here`.
2. Pass data sources via flags or config files.
3. Chain with other skills, like economic-indicators, for combined insights.
## Common Commands/API
Use the OpenClaw CLI or REST API for interactions. Authentication requires the `$OPENCLAW_API_KEY` environment variable.
- **CLI Command**: `openclaw market-regime analyze --asset AAPL --period 90d --metric volatility`
- Flags: `--asset` (required, e.g., stock symbol), `--period` (e.g., "30d" for 30 days), `--metric` (e.g., "volatility" or "trend").
- Output: JSON with regime type, volatility score, and key metrics.
- **API Endpoint**: POST to `https://api.openclaw.ai/v1/market-regime/analyze`
- Request body: JSON like `{"asset": "BTC-USD", "period": "1y", "metrics": ["volatility", "trends"]}`
- Response: 200 OK with JSON payload, e.g., `{"regime": "bull", "volatility": 0.15}`.
- Headers: Include `Authorization: Bearer $OPENCLAW_API_KEY`.
Code snippet for Python integration:
```python
import requests
api_key = os.environ.get('OPENCLAW_API_KEY')
response = requests.post('https://api.openclaw.ai/v1/market-regime/analyze',
headers={'Authorization': f'Bearer {api_key}'},
json={'asset': 'GOOGL', 'period': '180d'})
print(response.json()['regime']) # Outputs e.g., 'bear'
```
Config format: Use a YAML file for advanced settings, e.g.,
```yaml
asset: SPY
period: 365d
metrics:
- volatility
- trends
thresholds:
volatility_high: 0.2
```
## Integration Notes
Integrate with other OpenClaw skills by piping outputs or using shared data models. For example, combine with trading-strategies skill for automated alerts. Ensure data consistency by using standard formats like OHLCV (Open, High, Low, Close, Volume). If using external data, map it to the skill's expected schema (e.g., CSV with columns: date, open, high, low, close). Test integrations in a sandbox environment first. For web apps, use webhooks to receive regime updates.
## Error Handling
Handle errors by checking HTTP status codes or CLI exit codes. Common errors:
- 401 Unauthorized: Verify `$OPENCLAW_API_KEY` is set and valid.
- 400 Bad Request: Ensure JSON payload is correctly formatted (e.g., valid asset symbol).
- 429 Too Many Requests: Implement retry logic with exponential backoff.
In code, use try-except blocks:
```python
try:
response = requests.post(...) # As above
response.raise_for_status()
except requests.exceptions.HTTPError as err:
print(f"Error: {err.response.status_code} - {err.response.text}")
# Retry or log the error
```
If data fetch fails (e.g., invalid period), the skill returns a specific error code; parse the response for details like "ERR_INVALID_PERIOD".
## Concrete Usage Examples
1. **Example 1: Analyze Stock Volatility**
- Task: Check if Apple (AAPL) is in a high-volatility regime over the last 60 days.
- Command: `openclaw market-regime analyze --asset AAPL --period 60d --metric volatility`
- Expected Output: JSON like `{"regime": "high_volatility", "score": 0.25}`. Use this to trigger a sell alert in a trading bot.
2. **Example 2: Identify Crypto Trends**
- Task: Detect trend shifts for Bitcoin (BTC-USD) over the past year.
- API Call: POST to `/v1/market-regime/analyze` with body `{"asset": "BTC-USD", "period": "1y", "metrics": ["trends"]}`
- Code Snippet:
```python
response = requests.post(..., json={'asset': 'BTC-USD', 'period': '1y', 'metrics': ['trends']})
trends = response.json()['trends'] # e.g., ['upward_shift_at_2023-06-01']
```
- Use the output to update a dashboard or adjust investment allocations.
## Graph Relationships
- Related to: economic-indicators (depends on for macro data), trading-strategies (provides input for strategy decisions).
- Clusters with: financial (core cluster for this skill).
- Tags overlap: finance, volatility-analysis (shared with risk-assessment skills).
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.