megaeth-developer
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.
90
86%
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 is highly specific, comprehensive, and distinctive. It lists numerous concrete capabilities with proper technical references, includes natural trigger terms a MegaETH developer would use, and has an explicit 'Use when' clause. The only minor concern is the density of information, but it remains clear and well-structured.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists numerous specific concrete actions and technologies: wallet operations, token swaps (Kyber Network), eth_sendRawTransactionSync (EIP-7966), JSON-RPC batching, mini-block subscriptions, storage-aware contract patterns (Solady RedBlackTreeLib), MegaEVM gas model, WebSocket keepalive, bridging from Ethereum, and debugging with mega-evme. | 3 / 3 |
Completeness | Clearly answers both 'what' (comprehensive list of capabilities from wallet ops to debugging) and 'when' with an explicit 'Use when building on MegaETH, managing wallets, sending transactions, or deploying contracts' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'MegaETH', 'wallet', 'token swaps', 'transactions', 'deploying contracts', 'bridging from Ethereum', 'JSON-RPC', 'WebSocket'. These cover a wide range of terms a developer building on MegaETH would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the MegaETH-specific focus, referencing unique technologies like EIP-7966, MegaEVM gas model, mega-evme debugger, and Solady RedBlackTreeLib. Unlikely to conflict with general Ethereum or other blockchain skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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 excels at conciseness and progressive disclosure — it delivers MegaETH-specific knowledge efficiently and organizes content across files appropriately. Its main weaknesses are the lack of executable code examples for key operations (transactions, WebSocket setup, batch RPC calls) and missing validation/verification steps in the workflow for potentially destructive operations like transaction submission and contract deployment.
Suggestions
Add executable code snippets for the most critical operations: eth_sendRawTransactionSync usage, WebSocket keepalive with miniBlocks subscription, and JSON-RPC batch call syntax (e.g., using viem or ethers.js).
Add validation checkpoints to the operating procedure, especially for transaction submission (verify receipt status), contract deployment (verify deployment address), and bridging (confirm bridge completion).
Include a minimal end-to-end example showing sign → send → verify flow with eth_sendRawTransactionSync to make the most important pattern immediately copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining basic concepts (what Ethereum is, how RPCs work, etc.) and focuses on MegaETH-specific knowledge that Claude wouldn't already know. Every section delivers novel, domain-specific information with minimal padding. | 3 / 3 |
Actionability | The skill provides specific configuration values (chain IDs, gas fees, RPC URLs) and clear opinionated decisions, but lacks executable code examples. There are no copy-paste ready code snippets for key operations like sending transactions with eth_sendRawTransactionSync, WebSocket keepalive implementation, or batch RPC calls — these are described rather than demonstrated. | 2 / 3 |
Workflow Clarity | The operating procedure provides a reasonable 4-step classification and implementation workflow, but lacks validation checkpoints. For operations like transaction submission, contract deployment, and bridging, there are no explicit verify/retry feedback loops. The 'deliverables expectations' section is helpful but doesn't constitute validation steps. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview in the main file and clearly signaled one-level-deep references to 9 specialized files. The references are well-organized by topic with descriptive names, and the main file contains just enough context to guide navigation without being monolithic. | 3 / 3 |
Total | 10 / 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.
- Repository
- NeverSight/skills_feed
- Commit
e437c3c
- Reviewed
Table of Contents
Is this your skill?
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.