wagmi-read-contract

Query on-chain contract data with type-safe ABIs and read options.

Updated Nov 5, 2025
One-click install
npx skills add https://github.com/cyotee/crane --skill wagmi-read-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wagmi-read-contract
Source: https://github.com/cyotee/crane/tree/main/.claude/skills/wagmi-read-contract
Command: npx skills add https://github.com/cyotee/crane --skill wagmi-read-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read contract data in a type-safe way by querying views and pure functions via a defined ABI, reducing runtime errors and mismatched types.

Core Features & Use Cases

  • Type-safe reads: query balanceOf, totalSupply and other view functions using a defined ABI.
  • Flexible read options: specify blockTag, blockNumber, and chainId to target historical or cross-network data.
  • Seamless integration: works with Wagmi readContract and readContracts patterns in client apps to fetch on-chain data.

Quick Start

Query a contract's read-only data by supplying a typed ABI, contract address, and function arguments.

Frequently Asked Questions about wagmi-read-contract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I read Ethereum contract state in a type-safe way using wagmi?

To read Ethereum contract state type-safely with wagmi, supply a typed ABI to the readContract function. This fetches on-chain data via view or pure functions while reducing runtime type mismatch errors.

Can I query historical contract data at a specific block number using wagmi?

Yes, you can query historical contract data by specifying blockTag or blockNumber options. This targets specific blocks when reading contract state across networks using wagmi core readContract calls.

How do I fetch data from multiple Ethereum contracts across different chains?

Fetch data from multiple contracts across chains by using the readContracts pattern with a typed ABI and chainId. This allows querying cross-network on-chain state safely within client applications.

Do I need a typed ABI to call view functions like balanceOf with wagmi?

Yes, a typed ABI is required to safely call view functions like balanceOf or totalSupply. Using a defined ABI ensures type safety when querying contract reads and prevents mismatched argument types.

What is the best way to prevent type mismatch errors when reading Ethereum contract data?

The best way to prevent type mismatch errors is querying contract data with a type-safe ABI. Defining typed ABI inputs ensures arguments match expected types when calling view and pure functions.

Why are my wagmi readContract calls returning mismatched types in my frontend?

Mismatched types occur when querying contract data without a properly defined typed ABI. Supplying typed ABI inputs for view and pure function calls ensures type safety and prevents runtime errors.