agentleFS
SKE-LabsSKE-Labs/agent-trading-skills/skills/crypto-trading/on-chain-analysis/SKILL.md

on-chain-analysis

Skill17 starsChanged 4 months agoApache-2.0View on GitHub

Analyze on-chain metrics with provider, entity-adjustment, revision, and normalization controls. Use when evaluating holder behavior, exchange flows, valuation ratios, or network activity as contextual trading features.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat the setup as a testable hypothesis, not a prediction.

    line 67
  2. Distinctive:

    NEVER convert a count of correlated metrics into “high confidence” without testing incremental information

    line 76

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

On-Chain Analysis

Interpret blockchain data to understand market participant behavior and identify macro accumulation/distribution phases.

Note: Agent does not have direct on-chain API access. Use this framework to interpret on-chain data found via get_financial_news.

Exchange Flows

MetricAccumulation hypothesisDistribution hypothesis
Exchange net flowPersistent outflowPersistent inflow
Exchange reservesDecreasingIncreasing
Stablecoin flowsDry-powder hypothesisRedemption or risk-off hypothesis

Wallet Activity

MetricGrowth hypothesisWeakness hypothesis
Whale accumulationHighLow
Long-term holder supplyIncreasingDecreasing
Active addressesGrowingDeclining

Normalization

Do not reuse absolute BTC thresholds across eras or networks. For every metric, record provider, definition, unit, entity-adjustment status, timestamp, revision policy, and a trailing percentile or robust z-score. Multiple metrics derived from the same transaction graph are correlated and do not count as independent votes.

MVRV Ratio

MVRV RangeInterpretationAction
High relative to its own historyLarge aggregate unrealized profitDistribution risk, not an automatic sale
Near 1Market value near realized valueCost-basis context, not fair value
Below 1Aggregate unrealized lossStress context, not an automatic buy

For NVT and activity metrics, match the numerator and denominator frequency and account for batching, L2 migration, exchange-internal transfers, spam, and changes in address clustering. “Active address” is not the same as a user.

Workflow

  1. Gather on-chain intelligence from news sources:
get_financial_news(topic="BTC on-chain exchange outflow whale accumulation")
get_financial_news(topic="BTC MVRV NVT realized cap ratio")
  1. Check current price and momentum for technical confirmation:
get_candles(symbol="BTC/USD", exchange="binance", interval="1d", count=1)
get_indicators(indicator_code="rsi", symbol="BTC/USD", exchange="binance", interval="1d")
get_indicators(indicator_code="macd", symbol="BTC/USD", exchange="binance", interval="1d")
  1. Classify evidence: separate observed metric changes from provider interpretation and from the trading hypothesis. Reconcile contradictory metrics instead of counting votes.
  2. Report macro thesis: on-chain regime, metric alignment count, technical confirmation status, key levels, and confidence level.

Evidence and Validation

  • Treat the setup as a testable hypothesis, not a prediction. Define thresholds, entry, invalidation, and exit before evaluating outcomes.
  • Calibrate on the same instrument, venue, session, and timeframe. Use closed candles and a held-out or walk-forward sample; record every variant tried.
  • Include spread, fees, slippage, borrow or funding, partial fills, and latency. Reject the setup when net expectancy is not positive or depends on one narrow parameter.
  • Return observed inputs, missing data, cost assumptions, entry, invalidation, exit, and a valid, watch, or no-trade status.
  • Research basis: Glassnode's MVRV methodology defines the metric, while entity-adjustment notes explain clustering and revision risk; neither supports universal cutoffs.

Key Rules

  • Match each on-chain metric's timestamp, revision latency, and tested forecast horizon; do not assume one universal horizon.
  • NEVER convert a count of correlated metrics into “high confidence” without testing incremental information
  • Large transfers may be internal exchange movements -- context matters
  • On-chain data is lagging; it confirms trends rather than predicting them
  • LTH selling = distribution phase warning; LTH accumulating = bullish macro signal

Related Skills

  • altcoin-rotation -- on-chain metrics confirm cycle phases driving rotation decisions
  • dca-strategy -- MVRV and realized cap identify macro accumulation zones for enhanced DCA

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.