This source did not publish a separate summary. Review SKILL.md before using the skill.
SKILL.md
Skill: BTC Signals Pro
This skill is free to install. A Pro data plan ($20/mo) is required to access the API. Sign up at btcsignals.pro/pricing to get your API key.
Purpose
You are a Bitcoin trading intelligence assistant with access to institutional-grade market data from 50+ sources. Use the BTC Signals Pro API to provide real-time market analysis, trade recommendations, derivatives flow data, key price levels, live crypto news, and historical market data. Help users make informed trading decisions or build automated trading strategies. Never print the full API key in chat.
Live crypto news feed with headlines, sources, and symbol filtering
/v1/macro
GET
DXY, Gold, VIX, Treasury rates
/v1/calendar
GET
Live economic calendar with actual/estimate/previous values and impact ratings
/v1/account
GET
Subscription status + usage
Execution Steps
When a user asks about Bitcoin markets or trading:
Always check news first — GET /v1/news — warn the user immediately if any alert has severity >= 7.
Get the market snapshot — GET /v1/market/overview and GET /v1/score to establish current conditions.
For trade recommendations — GET /v1/trades/scalp and GET /v1/trades/swing to get AI-generated trade setups.
For deeper analysis — fetch relevant endpoints based on what the user needs (derivatives, levels, heatmaps, macro, etc.).
For crypto news context — GET /v1/news/crypto to get the latest crypto headlines and market narratives.
For macro event risk — GET /v1/calendar to check upcoming high-impact economic events with actual vs estimate data.
For historical analysis — GET /v1/market/history?from=YYYY-MM-DD&to=YYYY-MM-DD for backtesting or trend context.
Curl Examples
# Get current trade score
curl -s "https://api.btcsignals.pro/v1/score" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
# Get latest signal
curl -s "https://api.btcsignals.pro/v1/signal/latest" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
# Get scalp trade setup
curl -s "https://api.btcsignals.pro/v1/trades/scalp" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
# Get swing trade setup
curl -s "https://api.btcsignals.pro/v1/trades/swing" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
# Get market overview
curl -s "https://api.btcsignals.pro/v1/market/overview" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
# Get L/S ratios
curl -s "https://api.btcsignals.pro/v1/market/ls-ratios" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
# Get historical daily OHLCV (last 30 days)
curl -s "https://api.btcsignals.pro/v1/market/history?from=2026-02-11&to=2026-03-13" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
# Get liquidation heatmap
curl -s "https://api.btcsignals.pro/v1/heatmaps" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
# Get key price levels
curl -s "https://api.btcsignals.pro/v1/levels" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
# Get breaking news alerts
curl -s "https://api.btcsignals.pro/v1/news" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
# Get live crypto news feed (latest 20)
curl -s "https://api.btcsignals.pro/v1/news/crypto?limit=20" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
# Get Bitcoin-specific crypto news
curl -s "https://api.btcsignals.pro/v1/news/crypto?symbol=BTCUSD&limit=10" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
# Get signal history (past 7 days)
curl -s "https://api.btcsignals.pro/v1/signal/history?days=7" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
# Get macro indicators
curl -s "https://api.btcsignals.pro/v1/macro" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
# Get live economic calendar
curl -s "https://api.btcsignals.pro/v1/calendar" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
# Check account status
curl -s "https://api.btcsignals.pro/v1/account" \
-H "X-API-Key: {{BTC_SIGNALS_API_KEY}}"
Data Interpretation Rules
Trade Score (0-100)
Score Range
Interpretation
80-100
HIGH CONVICTION BUY
65-79
BUY
35-64
NEUTRAL
20-34
SELL
0-19
HIGH CONVICTION SELL
0 (exact)
HALT — critical news event, do not trade
Score Components
Temporal (-10 to +10): Time-of-day volatility adjustment. Peak volatility = Tuesday 8 AM CST.
Sentiment (-15 to +15): Fear & Greed Index (contrarian weighting) combined with AI-scored news sentiment.
L/S Score (-25 to +25, 1.5x weight): Contrarian Long/Short ratio signal. This is the DOMINANT FACTOR in the trade score. When retail is heavily long, the score pushes bearish, and vice versa.
Liquidity Multiplier (0.5-2.0): Amplifies or dampens the L/S Score based on OI changes, order book imbalance, funding rates, and heatmap proximity.
Use for trend context: compare current price to 7d/30d/90d range.
Calculate simple moving averages or volatility from historical candles.
Useful for backtesting trade score signals against actual price movement.
Swing Trade Status
new — freshly generated, not yet activated
active — entry conditions met, trade is live
modified — parameters updated since original generation (check rationale for changes)
Data Freshness
Data Type
Update Frequency
Trade Score + market data
Every ~2 hours
AI trades (scalp/swing)
6 AM + 6 PM CST
News alerts
Every 2 hours
Live crypto news feed
Real-time (sourced from FMP)
Economic calendar
Real-time (sourced from FMP)
Historical OHLCV
Daily candle updates
Heatmaps
5:45 AM + 5:45 PM CST
Cache responses within a conversation. Do not re-fetch the same endpoint within 60 seconds of the last successful call.
Examples
Example 1: Quick Market Check
User: "What's Bitcoin doing right now?"
Agent behavior:
GET /v1/news — check for critical alerts (severity >= 7).
GET /v1/market/overview — get price, 24h change, Fear & Greed.
GET /v1/score — get trade score and action.
Present a concise summary: current price, 24h change, Fear & Greed reading, trade score with action, and any high-severity news warnings.
Example 2: Full Trade Recommendation
User: "Should I buy or sell BTC right now? Give me a trade."
Agent behavior:
GET /v1/news — check for critical alerts first.
GET /v1/score — get trade score.
GET /v1/trades/scalp — get short-term trade setup.
GET /v1/trades/swing — get multi-day trade setup.
GET /v1/market/ls-ratios — check retail positioning (contrarian).
GET /v1/heatmaps — check nearest liquidation zones.
Present both scalp and swing setups with entry, stop loss, take profit levels, grade, R:R ratio. Include L/S context and nearest heatmap zones as confluence.
Example 3: Derivatives Deep Dive
User: "What's happening in the derivatives market?"
Agent behavior:
GET /v1/market/ls-ratios — L/S ratios across exchanges.
GET /v1/market/funding — funding rates.
GET /v1/market/oi — open interest changes.
GET /v1/derivatives/cvd — cumulative volume delta.
GET /v1/derivatives/liquidations — 24h liquidation data.
GET /v1/derivatives/options — max pain and put/call ratio.
Present a narrative: are derivatives traders positioned long or short? Is funding elevated? Is OI rising or falling? What do liquidations tell us about recent positioning flushes?
Example 4: Key Levels and Confluences
User: "Where are the important price levels for BTC?"
Agent behavior:
GET /v1/levels — full price level data with confluence.
GET /v1/heatmaps — liquidation zone data.
GET /v1/market/order-book — support/resistance from order book.
Present key levels organized by: daily/weekly/monthly opens, pivot points, Fibonacci levels, Volume Profile (POC, VAH, VAL), and highlight confluence zones where multiple levels converge. Overlay heatmap zones to show where liquidation clusters align with technical levels.
Example 5: News and Macro Context
User: "Is there any macro news I should worry about before trading?"
Agent behavior:
GET /v1/news — get all current alerts, flag anything severity >= 7.
GET /v1/news/crypto — get latest crypto headlines for broader market narrative.
GET /v1/macro — DXY, Gold, VIX, Treasury rates.
GET /v1/calendar — live economic calendar with actual/estimate/previous and impact ratings.
Present: any active high-severity news alerts, top crypto headlines, macro environment summary (is DXY strengthening? VIX elevated?), and upcoming calendar events with impact levels. Highlight any "High" impact events with actual: null (not yet released) that could cause volatility. Recommend caution if FOMC or CPI is within 24 hours.
Example 6: Historical Analysis and Backtesting
User: "How has BTC performed over the last month? Show me the price history."
Agent behavior:
GET /v1/market/history?from=2026-02-11&to=2026-03-13 — get daily OHLCV candles for the past 30 days.
GET /v1/market/overview — get current price for context.
GET /v1/signal/history?days=30 — get signal history to overlay trade score trends.
Present: 30-day price range (high/low), percentage change over the period, notable daily moves, and how the trade score tracked price action. Calculate simple metrics like average daily range and volatility.
Example 7: Crypto News Briefing
User: "What are the latest crypto news headlines?"
Agent behavior:
GET /v1/news/crypto?limit=10 — get the 10 most recent crypto news articles.
GET /v1/news — check for any severity-scored breaking alerts.
Present: list the top headlines with source and date. Flag any articles that align with active breaking alerts. Summarize the overall market narrative (bullish/bearish/mixed) based on headline sentiment.
Trading Bot Patterns
Pattern 1: Score-Based Entry
Use the trade score as the primary entry trigger for automated systems.
Fetch GET /v1/score on schedule (every 2 hours).
If trade_score >= 65 and trade_score_action is "BUY" or "STRONG BUY":
Fetch GET /v1/trades/scalp for short-term setup.
Enter long at scalp_entry with stop at scalp_sl.
Take profit at scalp_tp1 (partial) and scalp_tp2 (remainder).
If trade_score <= 34 and trade_score_action is "SELL" or "STRONG SELL":
Fetch GET /v1/trades/scalp for short-term setup.
Enter short at scalp_entry with stop at scalp_sl.
Take profit at scalp_tp1 (partial) and scalp_tp2 (remainder).
If trade_score == 0 (HALT): close all positions, do not open new trades.
If score is between 35-64 (NEUTRAL): no action, wait for next update.
Pattern 2: Contrarian L/S Extreme
Fade retail positioning at extremes for mean-reversion trades.
Fetch GET /v1/market/ls-ratios on schedule.
If avg_ls_ratio > 1.8 (extreme long positioning):
Retail is max long — expect a correction.
Fetch GET /v1/heatmaps to find liquidation zones above price (long squeeze targets).
Open a short position targeting the nearest heatmap zone below.
If avg_ls_ratio < 0.55 (extreme short positioning):
Retail is max short — expect a squeeze.
Fetch GET /v1/heatmaps to find liquidation zones below price (short squeeze targets).
Open a long position targeting the nearest heatmap zone above.
Confirm with GET /v1/derivatives/cvd — if CVD aligns with the contrarian direction, increase position size.
Always set stop loss beyond the nearest support/resistance from GET /v1/levels.
Pattern 3: News-Aware Trading
Protect against sudden volatility from macro events.
Before any trade entry, always check GET /v1/news and GET /v1/news/crypto.
If any alert has severity >= 8: do not enter new trades, tighten stops on existing positions.
If any alert has severity >= 9: close all positions immediately.
Check GET /v1/calendar for upcoming events:
If any "High" impact event has actual: null (not yet released) and is within 4 hours: reduce position sizes by 50%.
If FOMC, CPI, or NFP is within 1 hour: close all positions.
After a high-severity event passes (check expires_at), wait 30 minutes for volatility to settle before resuming trading.
Resume normal operations once no active alerts have severity >= 7.
Pattern 4: Multi-Factor Confirmation
Require confluence from multiple data sources before entering a trade.
confluence_direction == "BULLISH" and strength > 0.5: +1 | "BEARISH" and strength > 0.5: -1 | else: 0
cvd_1h > 0: +1 | cvd_1h < 0: -1 | else: 0
Sum the scores (-5 to +5):
+3 or higher: enter long using scalp trade parameters.
-3 or lower: enter short using scalp trade parameters.
Between -2 and +2: no trade, insufficient confluence.
Use scalp_grade to size the position: A-grade = full size, B-grade = 75%, C-grade = 50%.
Pattern 5: Swing Trade Management
Manage multi-day swing positions with automated monitoring.
Fetch GET /v1/trades/swing at 6 AM and 6 PM CST (after fresh generation).
If swing_status == "new":
Place a limit order at swing_entry.
Set stop loss at swing_sl.
Set take profit orders at swing_tp1 (33%), swing_tp2 (33%), swing_tp3 (34%).
If swing_status == "active":
Position is live. Monitor GET /v1/score every 2 hours.
If trade score flips to opposing direction (e.g., score drops below 35 while in a long), tighten stop to breakeven.
If swing_status == "modified":
Read swing_rationale for what changed.
Update stop loss and take profit levels to match new parameters.
If grade has been downgraded, reduce position size proportionally.
Always check GET /v1/news before modifying positions — halt changes during severity >= 8 events.
Pattern 6: Calendar-Driven Risk Management
Use the live economic calendar to dynamically adjust exposure ahead of high-impact events.
Fetch GET /v1/calendar at the start of each trading session.
Identify all "High" impact events in the next 24 hours where actual: null (not yet released).
For each upcoming high-impact event:
24 hours before: flag the event, no position size increase.
4 hours before: reduce position sizes by 50%.
1 hour before: close all positions, set pending orders only.
After release: compare actual vs estimate. If surprise is > 2x the spread, wait 30 minutes before re-entering. If surprise is minor, resume normal trading within 15 minutes.
Cross-reference with GET /v1/news/crypto after the event for immediate market reaction headlines.
Re-fetch GET /v1/score after the event to get the updated trade score incorporating the new data.
