功能描述

Advanced multi-chain wallet analyzer with USD pricing, collection names, ENS support, and sophisticated bot detection across 8 EVM networks. Use when you nee...

使用说明 (SKILL.md)

WalletLens

Name: Apechain Reader
Author: luigi08001

An advanced multi-chain wallet analyzer that provides detailed wallet profiles with USD pricing, human-readable NFT collection names, ENS domain support, and sophisticated bot detection across 8 major EVM networks.

Key Features

Multi-Chain Support: 8 EVM networks with ApeChain as primary focus
USD Price Integration: Real-time token prices via CoinGecko with graceful degradation
ENS Domain Support: Resolve .eth names across all commands automatically
Collection Name Resolution: Human-readable NFT collection names via Alchemy API + RPC fallback
Natural Language Summaries: Pretty mode includes intelligent wallet insights
Advanced Bot Detection: Sophisticated scoring algorithm to identify automated accounts
Reliable Performance: Automatic retry logic with exponential backoff for network resilience
Dual Output Formats: JSON (default) for agents, --pretty flag for human-readable output
Minimal Dependencies: Uses public RPC endpoints, optional Alchemy API key for enhanced features

Installation

This skill requires Node.js (v16+). No additional dependencies needed - uses built-in fetch API.

# Verify Node.js version
node --version

Quick Start

Basic wallet lookup on ApeChain:

node scripts/wallet-lookup.js 0x8dd6390be6dc732c92b161b9793a3948b56c0126

Same query with human-readable output:

node scripts/wallet-lookup.js 0x8dd6390be6dc732c92b161b9793a3948b56c0126 --pretty

Cross-chain lookup on Ethereum:

node scripts/wallet-lookup.js 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 --chain ethereum --pretty

Commands Reference

All commands support --chain \x3Cname> (defaults to apechain) and --pretty flag for human-readable output.

Wallet Lookup

Purpose: Complete wallet profile with balance, transaction count, and NFT activity summary

node scripts/wallet-lookup.js \x3Caddress> [--chain \x3Cname>] [--pretty]

Returns: Native token balance, transaction count, NFT activity (received/sent), collection count, top holdings

Example Output (JSON):

{
  "address": "0x8dd6390be6dc732c92b161b9793a3948b56c0126",
  "chain": "ApeChain",
  "chainId": 33139,
  "isContract": false,
  "balance": { "APE": 10.1398 },
  "transactionCount": 6352,
  "nftActivity": { "received": 2, "sent": 1 },
  "nftCollectionsHeld": 1,
  "topHoldings": [
    { "contract": "0x6f2a21a8b9cf699d7d3a713a9d7cfbb9e9760f97", "count": 2 }
  ],
  "explorer": "https://apescan.io/address/0x8dd6390be6dc732c92b161b9793a3948b56c0126"
}

Example Output (Pretty):

🔍 Wallet: 0x8dd6390be6dc732c92b161b9793a3948b56c0126
⛓️  Chain: ApeChain (33139)
💰 Balance: 10.1398 APE
📊 Transactions: 6,352
🎨 NFT Activity: 2 received, 1 sent
📦 Collections: 1
🔗 Explorer: https://apescan.io/address/0x8dd6390be6dc732c92b161b9793a3948b56c0126

Contract Information

Purpose: Detailed smart contract analysis including type detection and metadata

node scripts/contract-info.js \x3Caddress> [--chain \x3Cname>] [--pretty]

Returns: Contract type (ERC-20/721/1155), name, symbol, total supply, decimals, owner

Use Cases: Token research, contract verification, due diligence

Transaction History

Purpose: Recent transfer activity with timestamps and transaction details

node scripts/tx-history.js \x3Caddress> [--chain \x3Cname>] [--limit \x3Cnumber>] [--pretty]

Returns: Recent ERC-20 and NFT transfers with direction (IN/OUT), timestamps, contract addresses

Use Cases: Activity analysis, transaction tracking, wallet monitoring

NFT Holdings

Purpose: Current NFT collection with detailed token information

node scripts/nft-holdings.js \x3Caddress> [--chain \x3Cname>] [--collection \x3Ccontract>] [--pretty]

Returns: NFTs currently held, grouped by collection, token IDs, transfer statistics

Use Cases: NFT portfolio analysis, collection tracking, investment research

Bot Detection

Purpose: Advanced behavioral analysis to identify potential automated accounts

node scripts/bot-detect.js \x3Caddress> [--chain \x3Cname>] [--pretty]

Returns: Bot score (0-100), verdict classification, detailed breakdown of scoring factors

Scoring Factors:

Wrapped Token Usage (30pts): Frequency of using wrapped native tokens
Fast Flipping (25pts): Quick buy-sell cycles within 24 hours
Fast Listing (20pts): Immediate listing after purchase (within 30 minutes)
Aggressive Pricing (15pts): Price manipulation patterns
Cross-Collection Activity (10pts): Activity spread across many collections

Score Interpretation:

75-100: Definite bot
60-74: Likely bot
40-59: Suspicious
20-39: Probably human
0-19: Human

Use Cases: Due diligence, airdrop filtering, community verification

Supported Networks

See references/CHAINS.md for comprehensive chain information including reliability status and performance characteristics.

Reliable Chains ✅

ApeChain (primary) - Fastest, most reliable
Ethereum - Stable, high-value addresses
Base - Fast L2 performance
Arbitrum - Reliable L2 with official RPC

Intermittent Chains 🟡

Polygon - May timeout, use with retry logic
Optimism - Occasional performance issues
BNB Chain - Variable reliability
Avalanche - Limited testing, use with caution

Output Formats

All scripts support two output modes:

JSON Format (Default)

Structured data ideal for programmatic consumption and agent workflows:

node scripts/wallet-lookup.js \x3Caddress>
# Returns formatted JSON

Pretty Format (Human-Readable)

Clean, emoji-enhanced output for human review:

node scripts/wallet-lookup.js \x3Caddress> --pretty
# Returns formatted text with emojis and clear sections

Environment Variables

No environment variables required. The skill uses public RPC endpoints configured in scripts/lib/rpc.js.

Custom RPC Endpoints (Advanced)

To use custom RPC endpoints, modify the CHAINS object in scripts/lib/rpc.js:

const CHAINS = {
  apechain: { 
    id: 33139, 
    rpc: "your-custom-rpc-url", 
    name: "ApeChain", 
    symbol: "APE", 
    explorer: "https://apescan.io" 
  },
  // ... other chains
};

Error Handling & Reliability

Automatic Retry Logic

3 retry attempts with exponential backoff (500ms, 1s, 2s)
10-second timeout per request
Graceful failure with clean error messages

Input Validation

Address format validation (0x + 40 hex characters)
Chain name validation against supported list
Clean error messages without stack traces

Common Error Messages

{"error": "Invalid address format. Address must be 0x followed by 40 hexadecimal characters"}
{"error": "Unsupported chain \"invalidchain\". Supported chains: apechain, ethereum, base, arbitrum, polygon, optimism, avalanche, bsc"}
{"error": "RPC request timed out after 10000ms"}

Performance & Limitations

Response Times

Fast (\x3C 1s): ApeChain, Arbitrum
Good (1-2s): Ethereum, Base
Variable (1-5s): Polygon, Optimism, BSC, Avalanche

Data Coverage

Recent Activity: 500K-2M blocks depending on chain performance
Historical Limitations: Very old transactions may not appear
NFT Detection: ERC-721 and ERC-1155 support via Transfer events
Bot Analysis: Requires minimum 3 NFT purchases for scoring

Resource Usage

Memory: Minimal - processes data in streams
Network: Burst usage during queries, then idle
CPU: Low - mostly I/O bound operations

Troubleshooting

Network Issues

# If RPC timeouts occur, try different chain:
node scripts/wallet-lookup.js \x3Caddress> --chain ethereum

# For intermittent chains, retry usually succeeds:
node scripts/wallet-lookup.js \x3Caddress> --chain polygon

Empty Results

Verify address is active on the selected chain
Try different chain if cross-chain activity expected
Increase block scan range for older activity

Performance Optimization

Use --limit parameter to reduce transaction history size
Choose reliable chains (ApeChain, Ethereum, Base, Arbitrum) for consistent performance
Monitor response times and adjust expectations per chain

Advanced Usage

Batch Analysis

# Analyze multiple addresses
for addr in 0xaddr1 0xaddr2 0xaddr3; do
  echo "=== Analysis for $addr ==="
  node scripts/wallet-lookup.js $addr --pretty
  node scripts/bot-detect.js $addr --pretty
  echo
done

Cross-Chain Investigation

# Check same address across multiple chains
for chain in apechain ethereum base arbitrum; do
  echo "=== $chain ==="
  node scripts/wallet-lookup.js 0x8dd6390be6dc732c92b161b9793a3948b56c0126 --chain $chain --pretty
done

Collection Analysis

# Focus on specific NFT collection
node scripts/nft-holdings.js \x3Caddress> --collection 0x\x3Ccontract> --pretty

References

Chain Details: references/CHAINS.md - Comprehensive chain status and performance data
Bot Scoring: references/bot-scoring.md - Detailed bot detection methodology

Version History

v2.0: Added retry logic, input validation, pretty formatting, comprehensive chain documentation
v1.0: Initial release with basic multi-chain support and bot detection

Need help? Check the references directory for detailed documentation or run any command without arguments for usage instructions.

安全使用建议

This skill appears to be what it claims: a Node.js-based wallet analyzer that queries public RPC endpoints, CoinGecko, and optionally Alchemy. Before installing, consider: (1) the scripts will make network calls to third‑party RPC providers (listed in references/CHAINS.md) — those providers will see the addresses you query, (2) eth_getLogs over large block ranges can be heavy and may hit rate limits or cause large data transfers, (3) if you care about privacy or API quotas, provide your own RPC/Alchemy endpoints or API keys rather than using defaults, and (4) review the full scripts (especially scripts/lib/rpc.js which handles network endpoints/behaviour) yourself if you want to ensure no hidden telemetry or unexpected outbound endpoints are present. If you need higher assurance, run the scripts in a sandboxed environment and/or configure custom RPC endpoints before use.

功能分析

Type: OpenClaw Skill Name: apechain-reader Version: 3.1.0 The skill is designed for multi-chain wallet analysis, interacting with public blockchain RPCs, CoinGecko, and optionally Alchemy API for legitimate data retrieval. All network calls are to known, trusted services. Input validation is implemented for addresses and chain names, mitigating shell injection risks. The `package.json` lists no external dependencies, relying solely on Node.js built-ins. Documentation (SKILL.md, README-MARKETPLACE.md) provides clear instructions for using the skill and does not contain any prompt injection attempts to manipulate the agent into malicious actions. The `process.env.ALCHEMY_API_KEY` is used for an optional, documented feature (NFT collection name resolution) and is not exfiltrated. A critical bug related to the zero address causing indefinite hanging was identified and fixed, demonstrating a focus on robustness. While ENS resolution is explicitly disabled in `scripts/lib/rpc.js` due to a perceived dependency issue (despite the `namehash` function being present), this effectively closes a potential, albeit minor, attack vector. There is no evidence of intentional harmful behavior such as data exfiltration, unauthorized execution, or persistence mechanisms.

能力评估

✓ Purpose & Capability

Name/description (multi‑chain wallet analysis, NFT resolution, bot detection) align with the included scripts (wallet-lookup, nft-holdings, tx-history, contract-info, bot-detect) and the documented optional ALCHEMY_API_KEY/CoinGecko usage. The declared lack of required env vars and optional Alchemy key is coherent with the code and README.

ℹ Instruction Scope

SKILL.md instructs running the included Node.js scripts which call chain RPCs, CoinGecko and optionally Alchemy. This matches the stated purposes, but the scripts perform eth_getLogs over a large block range (latest - 1,000,000) and make multiple RPC calls — expected for this domain but can be heavy, reveal queried addresses to RPC providers, and may hit rate limits. No instructions ask the agent to read unrelated local files or transmit data to unexpected endpoints in the provided content.

✓ Install Mechanism

No install spec; code is bundled with the skill and relies only on Node.js (v16+). No external arbitrary download or post-install steps are present in metadata. This is low risk from an install-mechanism perspective.

✓ Credentials

The skill declares no required credentials and only an optional ALCHEMY_API_KEY for improved name resolution. That is proportionate to the features (collection name resolution). There are no requests for unrelated secrets or system credentials.

✓ Persistence & Privilege

always is false and the skill does not request elevated or persistent system privileges. It does not attempt to modify other skills or system-wide configs in the provided files. Autonomous invocation is allowed (platform default) but not combined with other red flags.

版本历史

v3.1.0

Fix: declared optional credentials in metadata

元数据

Slug apechain-reader

版本 3.1.0

许可证 —

累计安装 0

当前安装数 0

历史版本数 1

常见问题

Apechain Reader 是什么？

Advanced multi-chain wallet analyzer with USD pricing, collection names, ENS support, and sophisticated bot detection across 8 EVM networks. Use when you nee... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件，目前累计下载 591 次。

如何安装 Apechain Reader？

在 OpenClaw 或 Claude Code 对话框中运行命令「/install apechain-reader」即可一键安装，无需额外配置。

Apechain Reader 是免费的吗？

是的，Apechain Reader 完全免费（开源免费），可自由下载、安装和使用。

Apechain Reader 支持哪些平台？

Apechain Reader 跨平台运行，可在任意部署了 OpenClaw / Claude Code 的环境中使用（cross-platform）。

谁开发了 Apechain Reader？

由 Luigi08001（@luigi08001）开发并维护，当前版本 v3.1.0。

Apechain Reader