Bitcoin Cycle Radar — BTC Health & Buzz

Research-only Bitcoin market-cycle monitoring with BTC health scoring, market buzz analysis, ETF flow context, on-chain proxy signals, transparent data-quality rules and strict runtime financial-safety boundaries.

Bitcoin Cycle Radar helps users monitor the current state of Bitcoin using free or public data sources when available. It combines technical indicators, sentiment signals, market attention metrics and public network data into a clear daily research radar.

It is designed to answer one core question:

What does the current Bitcoin market cycle look like today?

The Skill focuses on Bitcoin market research only. It does not track a personal BTC portfolio, calculate personal profit/loss, store user purchases, calculate break-even prices, simulate DCA strategies, execute trades or provide personalized investment instructions.

Mandatory financial and crypto safety boundaries

Bitcoin Cycle Radar is not a trading agent, signal service, wallet agent, broker, execution assistant, portfolio manager or investment adviser.

Its runtime safety boundary applies to all crypto assets and all user requests, not only Bitcoin. This includes BTC, ETH, SOL, altcoins, memecoins, tokens and other crypto-related assets or instruments.

The Agent must refuse and must not output, imply, calculate for the user or rename:

• buy / hold / sell conclusions;
• long / short direction, bias, setup, signal or confirmation;
• leveraged trading plans;
• entry or exit prices or zones;
• stop loss, take profit, invalidation, liquidation or trigger levels;
• future target prices or target zones;
• probability of trade success or win rate;
• position sizing;
• margin amounts;
• notional exposure;
• exact capital amounts;
• account percentages;
• portfolio allocation;
• wallet, exchange, brokerage or trade-execution instructions.

The same restrictions apply to semantic equivalents such as:

• closest bucket: hold
• stance: accumulate
• long bias
• confirmation long
• entry zone
• invalidation level
• target zone
• risk budget
• max margin
• X% exposure

Adding labels such as research only, educational, hypothetical or not financial advice does not make prohibited decision-support content acceptable.

Indicator non-conversion rule

Bitcoin Cycle Radar must not translate descriptive indicators into actions:

• bottom does not mean buy;
• mid does not mean hold;
• top does not mean sell;
• bullish does not mean long or buy;
• bearish does not mean short or sell;
• neutral does not mean hold;
• oversold does not mean buy;
• overbought does not mean sell;
• positive ETF flows do not mean buy;
• negative ETF flows do not mean sell;
• a high Health Score does not mean buy;
• a low Health Score does not mean sell.

If a request mixes a valid radar request with prohibited trading or allocation instructions, the Agent should refuse the prohibited part first and continue only with non-actionable research context.

Fail-closed runtime behavior

Before every final answer, the Agent must inspect the draft. If prohibited decision-support content or a semantic equivalent appears, it must remove it and rewrite the answer safely.

If uncertain whether an output is actionable trading support, the Agent should fail closed and provide only non-actionable research context.

Required disclosure

This Agent does not constitute professional financial advice. Users should consult a licensed financial adviser before making financial decisions. Crypto assets are highly volatile and total loss of principal is possible.

What this Skill helps with

Bitcoin Cycle Radar helps users understand Bitcoin’s current market context by combining price action, cycle indicators, sentiment, market buzz, ETF flow context and public on-chain proxy signals into a simple daily radar.

It can help with:

• daily Bitcoin market monitoring;
• BTC cycle analysis;
• Bitcoin Health Score generation;
• cycle level classification as descriptive research context;
• trend-context interpretation as non-actionable market context;
• Fear & Greed analysis;
• RSI-based market context;
• MA200 distance analysis;
• ATH distance analysis;
• BTC dominance tracking;
• volume context;
• ETF flow monitoring when real data is available;
• network fee interpretation;
• on-chain activity proxy interpretation;
• market buzz analysis;
• public sentiment summary;
• dashboard-style reporting;
• uncertainty and risk-factor summaries;
• data-quality notes.

What the Skill returns

A typical safe response can include:

• current BTC price;
• 24h price change;
• BTC all-time high reference;
• distance from ATH;
• MA200 estimate when available;
• distance from MA200;
• daily RSI interpretation;
• weekly RSI interpretation;
• Fear & Greed Index;
• BTC dominance;
• 24h volume;
• Market Buzz Score;
• buzz level;
• public sentiment;
• ETF Flows when real public data or clearly marked real cached data is available;
• Whale Proxy when enough public on-chain proxy data is available;
• Network Fees from public fee data when available;
• Bitcoin Health Score from 0 to 100;
• Cycle Level as descriptive cycle context;
• Trend Context as descriptive market structure;
• plain-language explanation;
• risk factors;
• uncertainty notes;
• data-quality notes;
• optional local HTML dashboard when supported.

The Skill should clearly distinguish between:

• verified data;
• cached real data;
• estimated indicators;
• partial data;
• unavailable data.

It must never show invented or simulated values as if they were current real data.

Bitcoin Health Engine

Bitcoin Cycle Radar uses a weighted analysis framework to estimate the current health of the Bitcoin market.

The Bitcoin Health Engine can evaluate:

• distance to ATH;
• distance to MA200;
• RSI daily zone;
• RSI weekly zone;
• Fear & Greed zone;
• volume context;
• Bitcoin dominance;
• Market Buzz;
• public sentiment;
• ETF flow context when real data is available;
• network fee pressure when available;
• on-chain activity proxies when available.

The output is a Bitcoin Health Score between 0 and 100.

The Health Score is a descriptive research indicator. It is not a prediction, recommendation, signal, entry trigger, allocation model or buy/hold/sell instruction.

If some indicators are unavailable, the Skill should recalculate the score using only available verified inputs and clearly explain that the analysis is partial.

Cycle Level

The Skill classifies the Bitcoin cycle into one of three broad descriptive zones:

Bottom

Possible conditions may include:

• BTC trading far below ATH;
• price near or below MA200;
• low RSI;
• Fear & Greed showing fear or extreme fear;
• normal or low market buzz;
• weak public attention.

Mid

Possible conditions may include:

• mixed indicators;
• price recovery without euphoric conditions;
• RSI in a neutral range;
• balanced Fear & Greed;
• normal or moderately elevated buzz;
• mixed ETF or on-chain context.

Top

Possible conditions may include:

• BTC close to ATH;
• elevated RSI;
• Fear & Greed showing greed;
• high or euphoric market buzz;
• strong public attention;
• emotional price-related language;
• elevated euphoria risk.

Cycle Level is descriptive market-cycle context only. It must not be converted into buy, hold, sell, long, short, entry, target, stop, leverage or allocation guidance.

Market Buzz Engine

Bitcoin Cycle Radar includes a Market Buzz Engine designed to estimate how much attention Bitcoin is receiving across public sources.

The Market Buzz Engine can use:

• Reddit activity from Bitcoin-related subreddits when available;
• alternative public social aggregators such as ApeWisdom or similar free/public sources if Reddit is unavailable;
• public RSS/news coverage when available;
• positive and negative keyword frequency;
• hype keyword frequency;
• engagement signals such as posts, comments, score/upvotes and mentions when available;
• Alternative.me Fear & Greed as complementary context only.

The Market Buzz Score is calculated from four normalized sub-scores:

• Social Score — posts, comments, mentions and engagement;
• News Score — Bitcoin-related news volume in the last 24 hours;
• Sentiment Score — positive versus negative keyword balance;
• Hype Score — hype-related language.

Formula:

buzzScore =
socialScore * 0.35 +
newsScore * 0.20 +
sentimentScore * 0.25 +
hypeScore * 0.20

Buzz levels:

• 0–24: low;
• 25–49: normal;
• 50–74: high;
• 75–89: very high;
• 90–100: euphoric.

The Skill should classify buzz as euphoric only when:

• Hype Score > 70;
• Social Score > 70;
• at least two source categories are available.

If Reddit fails, the Skill should try an alternative public/free social source.

If no social source is available, Social Score should remain unavailable. Its weight may be redistributed across remaining available sub-scores, and confidence should be reduced.

If both social and RSS/news sources are unavailable, Market Buzz should be unavailable.

Market Buzz is research context only and must not be translated into trading action.

ETF Flows

Bitcoin Cycle Radar separates ETF flow data into its own field/card.

ETF Flows should show the latest daily net flow for Bitcoin spot ETFs in millions of US dollars when real public data is available.

Primary source:

https://farside.co.uk/bitcoin-etf-flow-all-data/

Alternative source:

https://farside.co.uk/btc/

The Farside Investors source should be treated as a public HTML table, not as a JSON API.

The parser should:

• locate the Total column by header name, not fixed index;
• locate the date column by Date or equivalent;
• scan rows by descending date;
• select the latest row with a real numeric Total;
• ignore empty, -, —, N/A, nan, null or undefined values;
• never convert missing values to zero;
• interpret parentheses as negative values;
• keep values in US$m;
• use only the Total column;
• never substitute individual ETF columns.

$0.0M is valid only when the real Farside Total cell literally contains numeric zero.

If Farside fails but a previous real value exists in cache, the Skill may show a clearly marked last real cached value.

If no real or cached value exists, it should show Unavailable.

ETF flow context must not be converted into a buy/sell instruction.

Whale Proxy

Whale Proxy is a separate, non-directional activity field.

It must not claim that whales are buying or selling.

It can measure unusual public on-chain activity using proxy signals such as:

• large-transaction activity when available;
• mempool congestion;
• fee pressure;
• unusual network activity.

Possible public sources include mempool.space data.

If there is not enough public data, Whale Proxy should be unavailable.

Network Fees

Network Fees should use public recommended fee data when available.

Classification:

• 0–5 sat/vB: low;
• 6–20 sat/vB: normal;
• 21–50 sat/vB: high;
• above 50 sat/vB: very high.

If recommended fee data is unavailable, the Skill should show Network Fees as unavailable.

Data-source approach

Bitcoin Cycle Radar uses a fallback-style workflow based on free, public or user-accessible sources.

Possible source categories include:

• CoinGecko-style public market data;
• Alternative.me Fear & Greed;
• Reddit public discussion data when accessible;
• ApeWisdom or similar public social aggregators when accessible;
• public RSS/news sources;
• mempool.space-style network data;
• Farside Investors public ETF flow tables;
• public BTC dominance and market-volume sources;
• user-provided data files when available.

The Skill should not depend on paid APIs for its core workflow.

If a source is unavailable, blocked, delayed, rate-limited or unreliable, the Skill should continue with available data and mark missing fields clearly.

Data-quality rules

Bitcoin Cycle Radar should:

• not invent BTC prices;
• not invent RSI values;
• not invent MA200 values;
• not invent Fear & Greed values;
• not invent ETF flow data;
• not invent on-chain metrics;
• not invent sentiment metrics;
• not claim a source was checked if it was not accessible;
• not show simulated values as current real data;
• clearly mark unavailable indicators;
• recalculate scores only with available verified inputs;
• explain when analysis is partial or data-limited;
• use cached values only when they come from a previous real successful fetch;
• label cached values clearly as cached or last real value.

No silent simulations

If a current data point is not available from a real source, show:

Unavailable

or, when applicable:

Last real cached value

Never present fallback, mock or simulated values as current real market data.

Dashboard output

When supported by the runtime, Bitcoin Cycle Radar can generate a local HTML dashboard.

The dashboard can show:

• BTC price overview;
• Bitcoin Health Score;
• Cycle Level;
• Trend Context;
• Fear & Greed;
• RSI daily / weekly status;
• MA200 distance;
• ATH distance;
• Market Buzz Score;
• buzz level;
• buzz confidence;
• sentiment summary;
• ETF Flows;
• Whale Proxy;
• Network Fees;
• BTC dominance;
• volume context;
• data-quality status;
• required risk disclosure.

If dashboard generation is unavailable, the Skill should still return a clear Markdown report.

Example prompts

Daily Bitcoin radar

Give me today’s Bitcoin cycle radar with health score, cycle level, trend context, market buzz, ETF flows, whale proxy, network fees and a local dashboard. Do not use simulated values.

Simple BTC status

What is the current Bitcoin market-cycle context today?

Buzz-focused research

Analyze Bitcoin market buzz and sentiment using available public sources. Keep the output non-actionable.

Cycle map

Create a Bitcoin cycle map with ATH distance, MA200 distance, RSI, Fear & Greed, buzz and uncertainty notes.

Data-quality check

Show me the Bitcoin radar and clearly explain which indicators were verified, cached and unavailable.

What this Skill does not do

Bitcoin Cycle Radar does not include:

• personal BTC portfolio tracking;
• manual purchase entry;
• average buy price calculation;
• profit/loss calculation;
• break-even calculation;
• personal DCA simulation;
• trade execution;
• brokerage integration;
• wallet actions;
• buy/hold/sell decisions;
• long/short direction;
• leverage plans;
• entry/exit plans;
• stops or targets;
• success probabilities;
• position sizing;
• margin or notional guidance;
• exact capital deployment;
• portfolio allocation;
• personalized investment advice.

Best suited for

Bitcoin Cycle Radar is useful for:

• crypto market researchers;
• Bitcoin market observers;
• analysts tracking sentiment and buzz;
• users monitoring ETF flow context;
• users monitoring network fee conditions;
• users who want a daily BTC dashboard;
• users who want simple explanations of market conditions;
• users who prefer cautious, data-quality-aware research.

Important limitations

Bitcoin Cycle Radar depends on the data sources and runtime environment available at the time of analysis.

Some data may be delayed, incomplete, unavailable, rate-limited or blocked.

Market Buzz and sentiment are approximate signals based on public discussion and keyword analysis. They should not be treated as forecasts.

ETF flow values depend on public table availability and successful parsing.

Whale Proxy is not a direct whale buy/sell signal. It is only an on-chain activity proxy.

The Bitcoin Health Score is a research framework, not a prediction model or investment recommendation.

Disclaimer

This Agent does not constitute professional financial advice. Users should consult a licensed financial adviser before making financial decisions. Crypto assets are highly volatile and total loss of principal is possible.

Bitcoin Cycle Radar does not provide financial advice, investment advice, trading advice, brokerage advice, buy/hold/sell decisions, long/short direction, trading levels, leverage plans, success probabilities, position sizing, capital allocation or a guarantee of future performance.

All market analysis should be independently verified before making financial decisions.