# Eip

> Analyze Ethereum Improvement Proposals by fetching content and optionally deep-diving into implementations

- Skill: `ethpandaops/eip` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add ethpandaops/eip`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ethpandaops/eip/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ethpandaops (https://skillmd.com/u/ethpandaops)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ethpandaops/eip

---


# EIP (Ethereum Improvement Proposal) Analysis

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.

## Instructions

### Step 1: Get EIP Number

**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).
```

### Step 2: Fetch and Analyze EIP

1. Use WebFetch to retrieve the EIP from `https://eips.ethereum.org/EIPS/eip-{number}`
2. If the page returns 404, inform the user and suggest checking the number
3. Extract and analyze key information

### Step 3: Provide Comprehensive Summary

Present a structured analysis:

```markdown
# 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]
```

### Step 4: Automatic Spec Search & Forkcast Lookup

**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.

#### Search Consensus Specs
Use WebSearch to find references:
```
site:github.com/ethereum/consensus-specs EIP-{number}
```

#### Search Execution Specs
Use WebSearch to find references:
```
site:github.com/ethereum/execution-specs EIP-{number}
```

#### Check Forkcast Status
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
```

#### Include in Report
Add Specification References and Forkcast sections to the report:

```markdown
## 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.

### Step 5: Compile References

**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:
1. **Official Sources** - The EIP itself and any referenced EIPs
2. **Specification Repositories** - Links to consensus-specs and execution-specs files found in Step 4

See `./deep-dive.md` for the complete References Template format.

### Step 6: Offer Follow-Up Options

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.

## Notes

- Always verify the EIP exists before attempting analysis
- Focus on practical implications for developers and users
- Highlight any contentious or discussion points mentioned in the EIP
- When doing deep-dives, look for actual implementation code, not just documentation
- Be prepared to explain complex technical concepts in accessible terms