โ† All skills
Tencent SkillHub ยท Developer Tools

web3-data-skill

Explore Web3 on-chain data using Chainbase APIs. Use this skill when the user asks about blockchain data, token holders, wallet addresses, token prices, NFTs...

skill openclawclawhub Free
0 Downloads
0 Stars
0 Installs
0 Score
High Signal

Explore Web3 on-chain data using Chainbase APIs. Use this skill when the user asks about blockchain data, token holders, wallet addresses, token prices, NFTs...

โฌ‡ 0 downloads โ˜… 0 stars Unverified but indexed

Install for OpenClaw

Quick setup
  1. Download the package from Yavira.
  2. Extract the archive and review SKILL.md first.
  3. Import or place the package into your OpenClaw setup.

Requirements

Target platform
OpenClaw
Install method
Manual import
Extraction
Extract archive
Prerequisites
OpenClaw
Primary doc
SKILL.md

Package facts

Download mode
Yavira redirect
Package format
ZIP package
Source platform
Tencent SkillHub
What's included
README.md, clawhub.json, SKILL.md, CLAUDE.md, scripts/chainbase.sh, references/api-endpoints.md

Validation

  • Use the Yavira download entry.
  • Review SKILL.md after the package is downloaded.
  • Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

  1. Download the package from Yavira.
  2. Extract it into a folder your agent can access.
  3. Paste one of the prompts below and point your agent at the extracted folder.
New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.

Trust & source

Release facts

Source
Tencent SkillHub
Verification
Indexed source record
Version
1.0.0

Documentation

ClawHub primary doc Primary doc: SKILL.md 6 sections Open source page

Web3 Data Explorer (Chainbase)

Query on-chain data via Chainbase Web3 API and SQL API.

Quick Reference

API Key: Use env CHAINBASE_API_KEY, falls back to demo. If rate-limited, direct user to https://console.chainbase.com to upgrade. Script: scripts/chainbase.sh <endpoint> [params...] # Top token holders scripts/chainbase.sh /v1/token/top-holders chain_id=1 contract_address=0xdAC17F958D2ee523a2206206994597C13D831ec7 limit=10 # Address labels scripts/chainbase.sh /v1/address/labels chain_id=1 address=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 # SQL query scripts/chainbase.sh /query/execute --sql="SELECT * FROM ethereum.blocks ORDER BY number DESC LIMIT 5"

Chain IDs

ChainIDChainIDEthereum1Optimism10BSC56Base8453Polygon137zkSync324Avalanche43114Merlin4200Arbitrum42161 Default to Ethereum (chain_id=1) unless user specifies otherwise.

Routing Logic

Match user intent to the right endpoint: User wantsEndpointTop token holders / who holds a tokenGET /v1/token/top-holdersList of holder addressesGET /v1/token/holdersToken priceGET /v1/token/priceHistorical token priceGET /v1/token/price/historyToken info (name, symbol, supply)GET /v1/token/metadataToken transfer historyGET /v1/token/transfersAddress labels/tagsGET /v1/address/labelsWallet transaction historyGET /v1/account/txsSingle transaction detailGET /v1/tx/detailNative token balance (ETH/BNB)GET /v1/account/balanceERC20 token balances of walletGET /v1/account/tokensNFTs owned by walletGET /v1/account/nftsDeFi portfolio positionsGET /v1/account/portfoliosENS domain lookupGET /v1/ens/records or /v1/ens/reverseNFT metadata/owner/rarityGET /v1/nft/metadata, /owner, /rarityTrending NFT collectionsGET /v1/nft/collection/trendingAnything not covered aboveSQL API (POST /query/execute)

Workflow

Identify intent โ€” Determine what data the user needs Resolve identifiers โ€” If user gives token name (e.g. "USDT"), look up the contract address. Common tokens: USDT: 0xdAC17F958D2ee523a2206206994597C13D831ec7 (ETH) USDC: 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 (ETH) WETH: 0xC02aaA39b223FE8D0A0e5c4F27eAD9083C756Cc2 (ETH) DAI: 0x6B175474E89094C44Da98b954EedeAC495271d0F (ETH) WBTC: 0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599 (ETH) If unknown, use GET /v1/token/metadata or ask the user for the contract address Select endpoint โ€” Use the routing table above; fall back to SQL API for complex/custom queries Execute โ€” Run via scripts/chainbase.sh or direct curl Present results โ€” Format data clearly with tables for lists, highlight key insights

SQL API Fallback

When fixed endpoints don't cover the query, translate user intent to SQL: scripts/chainbase.sh /query/execute --sql="SELECT from_address, SUM(value) as total FROM ethereum.token_transfers WHERE contract_address = '0x...' GROUP BY from_address ORDER BY total DESC LIMIT 20" Common table patterns (replace ethereum with chain name): {chain}.blocks โ€” Block data {chain}.transactions โ€” Transactions {chain}.token_transfers โ€” ERC20 transfers {chain}.token_metas โ€” Token metadata {chain}.logs โ€” Event logs SQL constraints: max 100,000 results per query. For complete endpoint parameters and response schemas, read references/api-endpoints.md.

Category context

Code helpers, APIs, CLIs, browser automation, testing, and developer operations.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package
4 Docs1 Scripts1 Config
  • SKILL.md Primary doc
  • CLAUDE.md Docs
  • README.md Docs
  • references/api-endpoints.md Docs
  • scripts/chainbase.sh Scripts
  • clawhub.json Config