playbooks

home / skills / openclaw / skills / base

base skill

/skills/spirosrap/base

This skill helps you query on-chain data from the Base blockchain, including balances, gas prices, block numbers, and transaction status.

npx playbooks add skill openclaw/skills --skill base

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
323 B
---
name: base
description: Interact with Base blockchain — check balances, gas prices, block numbers, and transaction status. Use when the user wants to query onchain data on Base. No API key required.
metadata: {"clawdbot":{"emoji":"🟣","homepage":"https://base.org","requires":{"bins":["curl","jq","python3"]}}}
---

Overview

This skill provides simple, direct interaction with the Base blockchain for common on-chain queries. It lets you check account balances, current gas prices, latest block numbers, and transaction statuses without requiring an API key. The implementation focuses on read-only queries and quick diagnostics for Base network state.

How this skill works

The skill connects to a Base node or public RPC endpoint and issues JSON-RPC calls to fetch chain data. It inspects account balances, queries gas price and fee data, reads the latest block header, and polls transaction receipts to determine confirmation and status. Responses are returned as structured values for easy consumption by other tools or agents.

When to use it

  • Verifying an account balance on the Base network before initiating a transfer.
  • Checking current gas price and fee estimates to set transaction parameters.
  • Confirming a transaction status and number of confirmations after submission.
  • Fetching the latest block number for monitoring or synchronization checks.
  • Integrating simple, read-only Base data into dashboards or automation scripts.

Best practices

  • Prefer public RPC endpoints with rate limits in mind; cache repeated queries short-term.
  • Use transaction receipt polling with increasing intervals to avoid excessive RPC calls.
  • Validate addresses and transaction hashes before querying to reduce errors.
  • Combine balance checks with nonce and gas estimates when preparing transactions.
  • Handle RPC errors and transient failures with retries and backoff.

Example use cases

  • A wallet UI shows an account balance and updates gas price suggestions in real time.
  • A monitoring script alerts when a submitted Base transaction moves from pending to confirmed.
  • A deployment tool verifies the latest block number to ensure node lag is acceptable before executing scripts.
  • A bot checks balances across multiple addresses before performing batch payouts.

FAQ

Do I need an API key to use the skill?

No. The skill uses public Base RPC endpoints and does not require an API key for read-only queries.

Can this skill send transactions or only read data?

It is intended for read-only queries: balances, gas prices, blocks, and transaction receipts. It does not manage private keys or broadcast signed transactions.