Ethereum Readonly
v1.0.0Read-only Ethereum blockchain queries — blocks, transactions, balances, contracts, logs via RPC and Etherscan APIs
⭐ 1· 678·4 current·4 all-time
byJ. Campbell@apexfork
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the runtime instructions. Requiring either `cast` or `curl` is proportionate for making JSON-RPC/Etherscan queries. Examples and RPC provider references align with a read-only explorer utility.
Instruction Scope
SKILL.md stays within read-only operations (RPC calls, logs, contract reads). It shows examples using environment variables for RPC endpoints and API keys (INFURA_PROJECT_ID, ALCHEMY_API_KEY, ETHERSCAN_API_KEY, QUICKNODE_TOKEN) but does not instruct reading unrelated files or secrets. Note: the doc includes examples that assume those optional API keys if the user chooses a provider.
Install Mechanism
No install spec and no code files — instruction-only. This minimizes footprint and disk writes. The required-binaries claim (cast or curl) matches the instructions.
Credentials
The skill does not require any environment variables, but the docs reference several optional provider keys and ETHERSCAN_API_KEY for Etherscan calls. That is expected for optional higher-rate providers, but users should not provision private keys or wallet secrets into environment variables for this skill (they are unnecessary for read-only queries).
Persistence & Privilege
always is false and the skill is user-invocable. There is no indication it modifies agent/system configuration or requests permanent presence. Autonomous invocation is allowed (the platform default) but not a unique risk here.
Assessment
This skill appears to be what it says: a read-only Ethereum query helper that uses `cast` (preferred) or `curl`. It does not require private keys or wallet access. Before installing: (1) avoid setting wallet private keys or secrets as environment variables for this skill — they are unnecessary; (2) understand optional API keys (Infura/Alchemy/QuickNode/Etherscan) increase request quotas but also mean those providers will see your queries; only provide them if you trust the provider and you understand quota/cost; (3) public RPC endpoints may enforce rate limits or log queries — heavy or broad log queries can fail or consume quotas, as the README warns; (4) because this is instruction-only, there is no code to inspect beyond the documentation — proceed if you trust the skill source or are comfortable with the documented commands.Like a lobster shell, security has layers — review code before you run it.
latestvk974kwxm9yt7n70g5za1xjw6hh818rtz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Any bincast, curl
