agentleFS
Sign inStart free
agenticspringagenticspring/skills/wallet-cluster-recon/SKILL.md

wallet-cluster-recon

Skill0 starsChanged 35 days agoMITView on GitHub

Use when profiling EVM wallet clusters or Arkham links.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Cross-chain check: if the entity has activity on non-Ethereum chains (RH/Base/etc), probe those too — Blockscout instances exist per chain …

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Wallet Cluster Recon

When to Use

  • User shares an Arkham/visualizer link or a list of related EVM addresses and asks to analyze/trace the entity.
  • Tracing fund flow across a cluster of wallets (who funds whom, what they trade).

Analyze a set of related wallets as one entity: who funds whom, what they trade, where funds flow.

Workflow

  1. Arkham links are login-gated (Cloudflare Turnstile + auth). Do not burn time extracting them; go straight to on-chain data. The URL itself still yields intel: the address list, and the positions query param names labeled nodes (binance, stake-com, opensea, relay-link, 0x000...000 mint node) that reveal the entity's context even without access.
  2. Primary data source: Blockscout v2 REST (free, no key):
    • GET https://eth.blockscout.com/api/v2/addresses/{addr} — balance, is_contract, has_tokens
    • .../counters — tx_count, token_transfers_count (fast triage: skip dead wallets)
    • .../transactions — native txs
    • .../token-transfers?type=ERC-20,ERC-721 — token/NFT history
  3. Triage first: pull /addresses + /counters for all wallets in one pass, then deep-dive only active ones.
  4. Profile each active wallet: recent transfers with direction (IN/OUT relative to target), symbol, method, counterparty. Summarize role per wallet (hub/funding, trader, collector, minter, disposal).
  5. Report as a table: wallet short-form, balance, activity pattern; call out fresh/empty wallets (likely future use) and recently-active ones.
  6. Cross-chain check: if the entity has activity on non-Ethereum chains (RH/Base/etc), probe those too — Blockscout instances exist per chain (e.g. https://rpc.mainnet.chain.robinhood.com for RH, no Blockscout but Alchemy works).

Pitfalls

See references/blockscout-v2-quirks.md for exact API gotchas (filter syntax, JSON parsing, deprecated endpoints).

References

  • references/blockscout-v2-quirks.md — working curl patterns and parsing fixes.

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.

Check your setup, free