Read-only factual data about historical Ethereum mainnet contracts. Use when the user asks about a specific contract address, early Ethereum contracts, deployment era, deployer, bytecode, decompiled code, or documented history (what a contract is and is not). Data is non-opinionated and includes runtime bytecode, decompiled code, and editorial history when available. Base URL https://ethereumhistory.com (or set BASE_URL for local/staging).
Data sourced from ClawHub. View on ClawSkills
Select your agent
Option 1: Install via CLI (recommended)
Recommended (no pre-install needed)
npx clawhub@latest --dir ~/.claude/skills install ethereum-historyOr via clawhub CLI (if already installed)
clawhub --dir ~/.claude/skills install ethereum-historyβ οΈ Requires Node.js 18+. No Node? Use Option 2 below to download the ZIP instead. Install Node.js β
Option 2: Manual install (no Node required)
Download the ZIP, extract it, and place the folder at the path below. Restart your agent to activate.
Install path
~/.claude/skills/ethereum-history/π‘Extract and place the folder at the path above, then restart your agent.
Category
Developer & DevOpsWhat Ethereum History can do for your AI workflow
Read-only factual data about directly from your Claude conversation
Works across Claude, Cursor, OpenClaw β install once, use everywhere
Trusted by 1,532+ developers worldwide
One-command installation β no complex setup required
Combine with other skills to build powerful multi-step AI workflows
Try these prompts with your AI agent after installing Ethereum History
Help me get started with Ethereum History
Explains what Ethereum History does, walks through the setup, and runs a quick demo based on your current project
Use Ethereum History to read-only factual data about historical Ethereum mainnet contracts
Invokes Ethereum History with the right parameters and returns the result directly in the conversation
What can I do with Ethereum History in my developer & devops workflow?
Lists the top use cases for Ethereum History, with example commands for each scenario
Guides & tutorials for AI skills
Ethereum History extends your AI assistant with the ability to read-only factual data about historical Ethereum mainnet contracts. Use when the user asks about a specific contract address, early Ethereum contracts, deployment era, deployer, bytecode, decompiled code, or documented history (what a contract is and is not). Data is non-opinionated and includes runtime bytecode, decompiled code, and editorial history when available. Base URL https://ethereumhistory.com (or set BASE_URL for local/staging). Rather than leaving your conversation to handle this manually, you can ask your Claude agent directly β and it will take care of the task end-to-end, using Ethereum History as its underlying capability.
Ethereum History works across Claude, Cursor, OpenClaw through the Model Context Protocol (MCP) β an open standard that lets AI clients share tools and skills without lock-in. Because MCP is platform-agnostic by design, you install Ethereum History once and it becomes available across all your AI clients. Whether you're working in Claude for focused sessions or Cursor for integrated workflows, the skill behaves consistently.
Getting started with Ethereum History takes about two minutes. Place the skill at `~/.claude/skills/ethereum-history/` (personal, all projects) or `.claude/skills/ethereum-history/` (project-specific), then restart your AI client. From that point, typing `/ethereum-history` in any conversation activates it, or the AI will use it on its own when it detects a relevant request.
Ethereum History has been installed 1,532 times, making it one of the more actively used skills in the Developer & DevOps category. The install rate suggests it solves a real, recurring need rather than a niche edge case. The source code is open on GitHub β you can inspect it, contribute fixes, or fork it to adapt the skill for your specific setup. Like all skills on DiscoverAISkills, it is free to install and use. The broader AI skills ecosystem continues to expand as developers contribute new capabilities across categories like developer tools, data analysis, writing, automation, and more.
Place the skill folder at ~/.claude/skills/ethereum-history/ for personal use (all projects), or .claude/skills/ethereum-history/ for project-specific use. Restart your AI client, then invoke with /ethereum-history or let the AI discover it automatically.
Ethereum History supports Claude, Cursor, OpenClaw. It integrates seamlessly with these AI platforms to extend their capabilities.
Ethereum History is free to install. Check the repository for licensing information.
Read-only factual data about historical Ethereum mainnet contracts. Use when the user asks about a specific contract address, early Ethereum contracts, deployment era, deployer, bytecode, decompiled code, or documented history (what a contract is and is not). Data is non-opinionated and includes runtime bytecode, decompiled code, and editorial history when available. Base URL https://ethereumhistory.com (or set BASE_URL for local/staging).
Links
Automate my developer & devops tasks using Ethereum History
Identifies repetitive steps in your workflow and sets up Ethereum History to handle them automatically
MCP vs traditional plugins: what's the difference?
Ethereum History is categorized under Developer & DevOps. These skills help AI agents perform specialized tasks in this domain.