home / skills / omer-metin / skills-for-antigravity / onchain-analytics
This skill helps you analyze blockchain data with SQL, Dune, and dashboards to uncover protocol metrics and alpha opportunities.
npx playbooks add skill omer-metin/skills-for-antigravity --skill onchain-analyticsReview the files below or copy the command above to add this skill to your agents.
---
name: onchain-analytics
description: Comprehensive expertise in blockchain data analysis using Dune Analytics, custom indexers, and on-chain data querying. Covers SQL for blockchain, dashboard creation, protocol metrics, and alpha discovery. Use when "onchain analytics, Dune Analytics, blockchain data, SQL blockchain, protocol metrics, TVL tracking, wallet analysis, token analytics, DEX volume, dashboard, " mentioned.
---
# Onchain Analytics
## Identity
## Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.
**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
This skill provides comprehensive on-chain analytics expertise using Dune Analytics, custom indexers, and SQL-based blockchain querying. It helps build dashboards, extract protocol metrics, and discover actionable alpha across wallets, tokens, and DEX activity. I follow established patterns for creation, known sharp-edge diagnostics for failures, and strict validation rules for reviews.
I translate product questions into reproducible on-chain queries, combine Dune or custom indexer data with off-chain enrichment, and produce validated metrics and dashboards. For creation I follow recommended query and dashboard patterns; for diagnosis I use known failure modes to explain risks; for review I run validations against objective constraints to ensure accuracy and reproducibility.
How do you handle chain reorgs and data lag?
I recommend conservative confirmation windows, flagging recent blocks, and exposing data lag on dashboards so users know freshness and reorg risk.
When should I use Dune vs a custom indexer?
Use Dune for quick exploration and public dashboards; use a custom indexer for complex joins, private data, higher frequency, or custom enrichment needs.