brief-protocol-change

Produces a structured briefing report for an Ethereum protocol change before scaffolding an exploration.

4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/feelyourprotocol/website --skill brief-protocol-change-feelyourprotocol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brief-protocol-change
Source: https://github.com/feelyourprotocol/website/tree/main/.cursor/skills/brief-protocol-change
Command: npx skills add https://github.com/feelyourprotocol/website --skill brief-protocol-change-feelyourprotocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deciding whether an Ethereum protocol change (EIP, ERC, or research proposal) is worth building an interactive exploration for requires reading specs, governance threads, and sibling code — this Skill structures that research into a consistent briefing report with a suitability verdict before any code is written. ## Core Features & Use Cases - Spec-grounded briefing: Fetches the canonical EIP markdown from ethereum/EIPs, the discussions-to thread, and ethereum/pm AllCoreDevs issues instead of relying on model memory. - Suitability verdict and taxonomy: Produces a GO / GO with caveats / not-a-fit verdict, plus proposed topic, timeline, and tags validated against the repo's TOPICS.ts, TIMELINE.ts, and TAGS.ts files. - Exploration and MCP outline: Drafts the widget center, query shape (simulate vs transaction), MCP docs page plan, and a proposed CANONICAL TypeScript object matching ProtocolChangeCanonical. - Use Case: Before building an interactive exploration for EIP-7702, run this Skill to get a cited report covering who cares, the core question, fork candidacy, and whether the MCP engine can actually run the change today. ## Quick Start Ask the agent to brief EIP-7702 using the brief-protocol-change skill and stop for sign-off before scaffolding anything.

Frequently Asked Questions about brief-protocol-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate whether an EIP is worth building an interactive exploration for?▼

Run this briefing skill, which fetches the EIP spec, discussion thread, and AllCoreDevs issues, then returns a GO, GO-with-caveats, or not-a-fit verdict. It judges whether there is a teachable widget slice and an honest MCP story, not whether the EIP is important.

What sources does the briefing use for Ethereum protocol changes?▼

It fetches the canonical markdown from ethereum/EIPs (defaulting to master), follows the preamble discussions-to link for 1-3 hot points, and searches ethereum/pm issues for fork candidacy and objections. It explicitly avoids briefing from model memory.

Does this skill create the exploration folder or code?▼

No. It only produces a report and a proposed CANONICAL object in chat. The exploration folder, widget, and engine module are created in later phases only after the human gives an explicit GO.

Can it brief ERCs or research proposals instead of EIPs?▼

Yes. For ERCs it reads from ethereum/ERCs, and for research it uses the URL or note the human provided. The same report structure and suitability verdict apply.

What are the limitations of the briefing phase?▼

The report is advisory and does not pin spec versions, implement widgets, or verify engine support beyond a quick check of EthereumJS or execution-specs. Taxonomy proposals must be confirmed by the human, and new tags are flagged as caveats.