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 specific technology references, includes a clear 'Use when' clause with natural trigger terms, and is clearly scoped to the MegaETH ecosystem, minimizing conflict risk with other blockchain-related skills.
| 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 eth_sendRawTransactionSync (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, serving as an effective overview/routing document for MegaETH development. Its main weaknesses are the lack of executable code examples in the top-level file (relying entirely on linked files for implementation details) and missing validation checkpoints in the workflow for potentially risky operations like transaction submission and contract deployment.
Suggestions
Add at least one executable code snippet for the most common operation (e.g., sending a transaction with eth_sendRawTransactionSync using viem/ethers) to make the main skill immediately actionable.
Add explicit validation/verification steps to the operating procedure, such as 'verify transaction receipt status' after submission and 'validate contract deployment' after deploy, with error recovery guidance.
| 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 Claude wouldn't already have. Every section delivers novel, domain-specific information with minimal padding. | 3 / 3 |
Actionability | The skill provides specific configuration values (chain IDs, gas fees, keepalive intervals) and clear opinionated decisions, but lacks executable code examples. Key patterns like eth_sendRawTransactionSync, JSON-RPC batching, and WebSocket keepalive are described but not shown with copy-paste ready code snippets. The detailed implementations are deferred to linked files. | 2 / 3 |
Workflow Clarity | The 4-step operating procedure provides a reasonable workflow (classify → pick patterns → implement → deliver), but lacks explicit validation checkpoints. For operations involving transactions and contract deployment (potentially destructive), there are no verify/retry feedback loops in the main skill file. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The main file serves as a concise overview with opinionated defaults, and clearly signals 9 one-level-deep references to detailed topic files. Navigation is well-organized and easy to scan. | 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
f772de4
- 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.