Menu
Analyze Ethereum Improvement Proposals by fetching content and optionally deep-diving into implementations
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | eip |
| description | Analyze Ethereum Improvement Proposals by fetching content and optionally deep-diving into implementations |
| argument-hint | <eip-number> |
| disable-model-invocation | true |
| allowed-tools | WebFetch, WebSearch, Read, Task, Bash, Grep, Glob, AskUserQuestion |
| context | fork |
| agent | general-purpose |
Analyze Ethereum Improvement Proposals by fetching content from the official EIP repository and providing comprehensive analysis with optional deep-dives into specification and client implementations.
If $ARGUMENTS is provided: Use that as the EIP number directly.
If $ARGUMENTS is empty: Ask the user:
Which EIP would you like me to analyze? Please provide the EIP number (e.g., 4844, 7691).
https://eips.ethereum.org/EIPS/eip-{number}Present a structured analysis:
# EIP-{number} Analysis
## Overview
- **Title**: [EIP Title]
- **Status**: [Current Status]
- **Type**: [Standards Track, Meta, or Informational]
- **Category**: [Core, Networking, Interface, or ERC]
- **Authors**: [List of authors]
## Summary
[2-3 paragraph executive summary of what this EIP proposes]
## Technical Details
### Motivation
[Why this EIP is needed]
### Specification
[Key technical specifications and changes]
### Implementation Considerations
- [Key implementation points]
- [Backward compatibility issues]
- [Security considerations]
## Impact Analysis
### Benefits
- [Expected improvements]
- [Problems solved]
### Potential Risks
- [Implementation risks]
- [Compatibility concerns]
### Related EIPs
- [List any related or dependent EIPs]
Automatically search for EIP references in specification repositories and check Forkcast tracking status. Do NOT prompt the user - this step runs automatically as part of the analysis.
Use WebSearch to find references:
site:github.com/ethereum/consensus-specs EIP-{number}
Use WebSearch to find references:
site:github.com/ethereum/execution-specs EIP-{number}
Use WebFetch to check EIP tracking status:
WebFetch: https://forkcast.org/eips
Prompt: Find EIP-{number} and extract the tracking status including: fork targeting, inclusion status, and any implementation progress shown
Add Specification References and Forkcast sections to the report:
## Specification References
### Consensus Specs
- **Status**: [Found/Not Found]
- **Files**: [List of relevant files with links]
- **Summary**: [Brief description of spec changes, if found]
### Execution Specs
- **Status**: [Found/Not Found]
- **Files**: [List of relevant files with links]
- **Summary**: [Brief description of spec changes, if found]
## Forkcast Tracking Status
- **Target Fork**: [Fork name, e.g., Cancun, Prague, or "Not Scheduled"]
- **Inclusion Status**: [Confirmed / Proposed / Under Consideration / Not Tracked]
- **Notes**: [Any relevant timeline or implementation progress info]
Note: If the EIP is not found on Forkcast, report "Not Tracked" and note that Forkcast primarily tracks EIPs scheduled for upcoming hard forks.
Always conclude the analysis with a References section that consolidates all links discovered during the analysis. This provides a single place for users to access all relevant resources.
Collect and organize references into these categories:
See ./deep-dive.md for the complete References Template format.
After presenting the complete report with spec findings, Forkcast status, and references, ask using AskUserQuestion:
Would you like me to explore further?
1. **ethresear.ch** - Search for related research discussions and proposals
2. **Client implementations** - Analyze consensus/execution client implementations
If the user selects follow-up options, use the Read tool to load ./deep-dive.md (relative to this skill directory) and execute the analysis as described there.