← Back to Skills Marketplace
127
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install transaction-receipt
Description
Human-readable on-chain transaction receipt. Resolve tx status, fees, and intent: simple transfers, swaps/trades, token approvals, DeFi staking-style calls,...
Usage Guidance
This skill appears to do what it says: it will perform on-chain lookups using either your optional Tokenview API key or public RPC endpoints, enforce per-machine hourly limits, and write a small rate-limit file to your home directory. Before installing: (1) Decide whether you want to provide a TOKENVIEW_API_KEY (optional) and store it in your OpenClaw settings rather than pasting it in chat. (2) Be aware the skill creates a rate-limit state file (default path in SKILL.md: ~/.openclaw/state/transaction-receipt/rate-limit.log — README lists a different path; you may want to confirm which path will be used and/or override TRANSACTION_RECEIPT_RATE_FILE). (3) Check the referenced endpoints (Tokenview, ethereum.publicnode.com, blockstream.info) and the GitHub repository URL in SKILL.md if you want to review source/docs. (4) If you have strict privacy needs, set TRANSACTION_RECEIPT_RATE_FILE to a location you control or run without persistent state (the skill will fall back to in-memory counters). Overall there are no signs of data exfiltration or unrelated credential requests, but review the repository and the Tokenview privacy/usage terms if you plan to supply an API key.
Capability Analysis
Type: OpenClaw Skill
Name: transaction-receipt
Version: 1.1.2
The transaction-receipt skill is a well-structured tool for fetching and interpreting blockchain transaction data from Tokenview or public RPC nodes. It implements robust security and operational practices, including strict input validation (hexadecimal checks for transaction hashes in SKILL.md), rate limiting via a local state file with restricted permissions (chmod 600), and explicit instructions to the AI agent to never reveal or echo the sensitive TOKENVIEW_API_KEY. The use of shell commands (curl, mkdir, wc) is strictly aligned with the stated purpose of data retrieval and local state management, and no indicators of data exfiltration, malicious execution, or prompt injection were found.
Capability Assessment
Purpose & Capability
The skill's name/description (human-readable on-chain receipts) aligns with the instructions: it uses curl to query Tokenview or public RPC/blockstream endpoints, parses responses, and applies rate limits. Required items (curl, optional TOKENVIEW_API_KEY, optional jq/python) are proportionate. Minor inconsistency: README and SKILL.md disagree on the default rate-limit file path (~/.openclaw/state/... in SKILL.md vs ~/.cursor/... in README) which is likely a documentation drift but not a functional mismatch with purpose.
Instruction Scope
Instructions stay within scope: validate hashes, choose Tokenview or public fallback, enforce curl timeouts, and avoid printing raw API keys/responses. The skill will read environment variables (TOKENVIEW_API_KEY, TRANSACTION_RECEIPT_MAX_PER_HOUR, TRANSACTION_RECEIPT_RATE_FILE) and create/update a local rate-limit file in the user's filesystem; this file contains timestamps of queries. This persisted state and file I/O are relevant to rate-limiting but are something to be aware of (privacy/persistence). No instructions request unrelated system secrets or other files.
Install Mechanism
Instruction-only skill with no install spec and no bundled code — minimal installation risk. It does require curl (commonly present); optional jq or python3 is suggested for JSON parsing but not required.
Credentials
Only an optional Tokenview API key is requested (sensible for richer data). The other environment variables control rate limits and file path. No unrelated credentials or broad secret access are requested. The skill explicitly instructs not to ask users to paste their full API key in chat and not to echo keys.
Persistence & Privilege
The skill writes a per-user rate-limit file (default in the user's home directory, with fallbacks) and may create its parent directory and set file permissions. This is appropriate for rate limiting but does create persistent files on disk; there is no special platform privilege (always:false) and it does not change other skills or system-wide agent config.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install transaction-receipt - After installation, invoke the skill by name or use
/transaction-receipt - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.2
- Added a `metadata` section to SKILL.md with repository link and structured environment variable definitions.
- Updated author to "Antalpha AI Team."
- No logic or behavioral changes to the skill itself; documentation and metadata improvements only.
v1.1.1
- Improved fallback handling: if a Tokenview API key is missing or invalid, automatically switch to public sources and inform the user.
- Added environment variables for rate limiting and state file configuration, allowing custom limits and storage paths.
- Enhanced onboarding: first-time users receive guidance on API key setup and public fallback behavior.
- Enforced curl timeouts on all network requests for more robust error handling.
- Comprehensive, friendly error reporting for rate limits, permission issues, and missing transactions.
- Expanded transaction classification to include transfers, swaps, approvals, DeFi actions, and NFT events.
Metadata
Frequently Asked Questions
What is Transaction Receipt?
Human-readable on-chain transaction receipt. Resolve tx status, fees, and intent: simple transfers, swaps/trades, token approvals, DeFi staking-style calls,... It is an AI Agent Skill for Claude Code / OpenClaw, with 127 downloads so far.
How do I install Transaction Receipt?
Run "/install transaction-receipt" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Transaction Receipt free?
Yes, Transaction Receipt is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Transaction Receipt support?
Transaction Receipt is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Transaction Receipt?
It is built and maintained by bevanding (@bevanding); the current version is v1.1.2.
More Skills