gaps

Plan ordered Ethernauta library migration steps for animatronik builds.

1|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/niconiahi/ethernauta --skill gaps-niconiahi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gaps
Source: https://github.com/niconiahi/ethernauta/tree/main/.claude/skills/gaps
Command: npx skills add https://github.com/niconiahi/ethernauta --skill gaps-niconiahi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams resolve Ethernauta codebase gaps that block a migration to building animatronik end-to-end using only @ethernauta/* libraries, avoiding invented JSON-RPC methods and manual shims.

Core Features & Use Cases

  • Actionable migration punch list: Provides an ordered set of changes so later work does not break earlier dependencies.
  • Correct method/shaping guidance: Identifies mis-typed writable methods that must become signable, and explicitly deletes an invented method file and its exports.
  • Transport and generator alignment: Lays out required resolver/context surface changes and the ABI generator rewrite so view methods dispatch eth_call and state-changing methods compose onto eth_signTransaction.
  • Contract interface regeneration plan: Specifies regenerating ERC 20/165/721 methods from OpenZeppelin sources to satisfy animatronik’s ERC-721 Enumerable needs.
  • Consumer workflow cleanup: Documents the required changes in apps/playground and animatronik routing so signing flows use the correct Ethernauta primitives.

Quick Start

Use the gaps action list to plan and execute the ordered Ethernauta updates needed for the animatronik dog-fooding migration, starting with deleting or retyping mis-shaped methods and updating the transport context and ABI generator accordingly.

Frequently Asked Questions about gaps

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

FAQPage Schema
How do I plan an Ethernauta library migration for an end-to-end Ethereum build?

To plan an Ethernauta library migration, you need an ordered execution plan that addresses refactoring package shapes, transport context threading, ABI generator correctness, and ERC interface regeneration without breaking earlier dependencies.

What's the best way to fix mis-typed writable methods in Ethernauta contracts?

Fixing mis-typed writable methods requires identifying methods that must become signable, explicitly deleting invented method files and their exports, and ensuring correct transport context type propagation for Readable and Signable flows.

How does the ABI generator dispatch eth_call versus eth_signTransaction for view methods?

The ABI generator dispatches view methods via eth_call and composes state-changing methods onto eth_signTransaction by applying specific JSON-RPC method mapping rules and rewriting the generator to align with the transport context.

Do I need to regenerate ERC-721 interfaces from OpenZeppelin for an animatronik migration?

Yes, regenerating ERC 20, 165, and 721 methods from OpenZeppelin sources is required to satisfy animatronik’s ERC-721 Enumerable needs during the Ethernauta migration.

Why does my Ethernauta migration break when updating transport and generator components?

Ethernauta migrations break when updates are applied out of order, which is why an ordered punch list is required to ensure resolver/context surface changes and ABI generator rewrites do not invalidate earlier dependency fixes.

Can I use manual shims and invented JSON-RPC methods to unblock an animatronik build?

No, avoiding manual shims and invented JSON-RPC methods is the core problem this process solves, relying instead on correct JSON-RPC method mapping and OpenZeppelin-sourced contract method generation for Ethernauta primitives.