Slash Command

Analyze Chain

Comprehensive blockchain metrics monitoring and on-chain analytics system

Type: Slash Command
Repository: jeremylongshore/tons-of-skills-marketplace
GitHub stars: 2.8k
License: MIT
Repo last updated: Sep 27, 2026
Source file: plugins/crypto/on-chain-analytics/commands/analyze-chain.md
Version: 2.0.0
Author: claude-code-plugins

What Analyze Chain is

Analyze Chain is a slash command published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Analyze Chain gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Analyze Chain

Claude Code

Download analyze-chain.md from the repository.
Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
Run it by typing / followed by its name.

Claude Cowork

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
In Customize → Skills, click +, then upload the ZIP.
Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/crypto/on-chain-analytics/commands/analyze-chain.md, shared under the repository's MIT license. Read the full file on GitHub.

Comprehensive blockchain metrics monitoring system that tracks network health, holder distribution, whale movements, exchange flows, supply metrics, and transaction velocity across multiple blockchain networks.

When to Use

Use this command when you need to:

Monitor Network Health: Track hash rate, difficulty, active addresses, and transaction throughput
Analyze Holder Distribution: Identify whale concentration, wealth distribution, and accumulation patterns
Track Exchange Flows: Monitor deposit/withdrawal patterns, exchange reserves, and liquidity movements
Analyze Supply Metrics: Track circulating supply, staked amounts, burned tokens, and inflation rates
Measure Transaction Velocity: Calculate token circulation speed, active address growth, and network utilization
Bitcoin UTXO Analysis: Track unspent transaction outputs, UTXO age distribution, and holder behavior
Ethereum Gas Analytics: Monitor gas prices, network congestion, and smart contract activity
Whale Movement Alerts: Real-time tracking of large transactions and address clustering
Market Research: Data-driven insights for trading strategies and investment decisions
Compliance Monitoring: Track sanctioned addresses, suspicious patterns, and regulatory requirements

DON'T Use When

Real-time Trading: Use dedicated trading APIs for sub-second execution
Price Prediction: On-chain metrics show trends, not future prices
Legal Advice: Consult blockchain forensics experts for legal cases
Single Transaction Tracking: Use block explorers for individual transactions
Historical Data Older Than 7 Years: Most APIs have limited historical depth

Design Decisions

1. Multi-Chain Architecture vs Single Chain Focus

Chosen Approach: Multi-chain with chain-specific adapters

Why: Different blockchains require different metrics and APIs. Bitcoin uses UTXO model while Ethereum uses account-based model. A unified interface with chain-specific implementations provides flexibility while maintaining consistent output formats.

Alternatives Considered:

Single Chain Only: Rejected due to limited market coverage
Chain-Agnostic Generic Metrics: Rejected due to loss of blockchain-specific insights
Separate Tools Per Chain: Rejected due to code duplication and maintenance burden

2. Data Source Strategy: APIs vs Full Node

Chosen Approach: Hybrid API-based with optional full node support

Why: Most users don't run full nodes. Using APIs (Etherscan, Blockchain.com, Glassnode) provides immediate access without infrastructure requirements. Full node support remains optional for advanced users needing maximum decentralization.

Alternatives Considered:

Full Node Required: Rejected due to high infrastructure costs ($500+/month)
APIs Only: Considered but added full node option for enterprise users
Light Client Sync: Rejected due to incomplete data and sync time requirements

3. Whale Detection Threshold Method

Chosen Approach: Dynamic percentile-based thresholds with absolute minimums

Why: Static thresholds (e.g., "1000 BTC = whale") become outdated as prices change. Using percentile-based detection (top 0.1% holders) with absolute minimums (e.g., $1M USD equivalent) adapts to market conditions.

Alternatives Considered:

Fixed Token Amounts: Rejected due to price volatility making thresholds obsolete
USD Value Only: Rejected as it misses on-chain concentration patterns
Machine Learning Clustering: Rejected due to complexity vs accuracy tradeoff

4. Data Storage: Time-Series Database vs Relational

Chosen Approach: Time-series database (InfluxDB) for metrics, PostgreSQL for metadata

Why: On-chain metrics are time-stamped numerical data perfect for time-series databases. InfluxDB provides efficient storage, fast queries, and built-in downsampling. PostgreSQL stores wallet metadata, labels, and relationships.

Alternatives Considered:

PostgreSQL Only: Rejected due to poor time-series query performance
InfluxDB Only: Rejected due to poor relational data handling
ElasticSearch: Rejected due to higher complexity and resource requirements

5. Real-Time vs Batch Processing

Chosen Approach: Hybrid batch + real-time for whale alerts

Before you install

Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
Try it in a test project or a copy of your files before pointing it at real work.
Pin the version you tested, and review changes before updating.
Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Analyze Chain?

Analyze Chain is a slash command for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Comprehensive blockchain metrics monitoring and on-chain analytics system

How do I install Analyze Chain in Claude Code?

Download analyze-chain.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use Analyze Chain in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is Analyze Chain safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.