End-to-end MegaETH development playbook (Feb 2026). Covers wallet operations, token swaps (Kyber Network), eth_sendRawTransactionSync (EIP-7966) for instant receipts, JSON-RPC batching, real-time mini-block subscriptions, storage-aware contract patterns (Solady RedBlackTreeLib), MegaEVM gas model, WebSocket keepalive, bridging from Ethereum, and debugging with mega-evme. Use when building on MegaETH, managing wallets, sending transactions, or deploying contracts.
94
Quality
92%
Does it follow best practices?
Impact
95%
2.06xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that comprehensively covers MegaETH development capabilities with specific technical details. It uses third person voice correctly, includes a clear 'Use when...' clause with natural trigger terms, and is highly distinctive due to MegaETH-specific terminology. The description effectively balances technical depth with accessibility.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: wallet operations, token swaps (Kyber Network), eth_sendRawTransactionSync, JSON-RPC batching, mini-block subscriptions, storage-aware contract patterns, gas model, WebSocket keepalive, bridging, and debugging with mega-evme. | 3 / 3 |
Completeness | Clearly answers both what (comprehensive list of MegaETH development capabilities) AND when with explicit 'Use when building on MegaETH, managing wallets, sending transactions, or deploying contracts' clause. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'MegaETH', 'wallet', 'token swaps', 'transactions', 'deploying contracts', 'bridging from Ethereum', plus technical terms like 'EIP-7966', 'JSON-RPC', 'WebSocket' that developers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with MegaETH-specific terminology (MegaEVM, mega-evme, mini-block subscriptions, eth_sendRawTransactionSync) that clearly distinguishes it from general Ethereum or other blockchain skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently communicates MegaETH-specific knowledge without over-explaining. The progressive disclosure is excellent and the opinionated defaults are clearly stated. The main weakness is the lack of executable code examples in the main file - the actionable guidance is conceptual rather than copy-paste ready.
Suggestions
Add a minimal executable code example for the most common operation (e.g., sending a transaction with eth_sendRawTransactionSync using viem or ethers.js)
Include a concrete WebSocket keepalive code snippet showing the 30-second eth_chainId ping pattern
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables for configuration, bullet points for decisions, and avoids explaining concepts Claude already knows (EVM, gas, WebSockets). Every section earns its place with specific MegaETH details. | 3 / 3 |
Actionability | Provides specific values (chain IDs, gas costs, RPC URLs) and clear guidance, but lacks executable code examples. The 'Operating procedure' describes what to do conceptually rather than showing concrete commands or code snippets. | 2 / 3 |
Workflow Clarity | Clear 4-step operating procedure with task classification, pattern selection, implementation guidance, and deliverables expectations. The workflow is well-sequenced and includes explicit checkpoints for what to verify (chain ID, gas limit, storage costs). | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and well-signaled one-level-deep references to 9 specialized files. Content is appropriately split between quick-reference decisions and detailed implementation guides. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
5342bca
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.