CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

80

2.06x
Quality

73%

Does it follow best practices?

Impact

95%

2.06x

Average score across 3 eval scenarios

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xbreadguy/megaeth-ai-developer-skills/megaeth-developer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, well-organized overview with strong MegaETH-specific directives, but it lacks executable code and validation checkpoints, and its progressive-disclosure references point to files that do not exist in the bundle.

Suggestions

Ship the nine referenced files (references/wallet-operations.md, frontend-patterns.md, rpc-methods.md, smart-contracts.md, storage-optimization.md, gas-model.md, testing.md, security.md, resources.md) so the progressive-disclosure links resolve — or inline the essential parts and drop the dead links.

Add at least one copy-paste executable example per common task (e.g., a complete eth_sendRawTransactionSync request or a WebSocket miniBlocks subscription snippet) to move actionability from directive to runnable.

Insert explicit validation/feedback steps into the operating procedure for destructive/batch operations — e.g., 'after signing, confirm the receipt before reporting success; on revert, re-estimate gas via remote eth_estimateGas'.

DimensionReasoningScore

Conciseness

Mostly lean bullet points with no padding or teaching of known concepts (chain IDs, gas values, method names); the opening 'What this Skill is for' bullet list slightly overlaps the description and could be trimmed.

4 / 5

Actionability

Gives concrete, domain-specific guidance (chain IDs, 0.001 gwei base fee, eth_sendRawTransactionSync, 30s keepalive) but provides no copy-paste executable code or commands, so it reads as directive hints rather than runnable instruction.

3 / 5

Workflow Clarity

A clear four-step operating procedure exists (classify layer → pick patterns → implement with correctness → deliverables), but there are no validation/verification checkpoints for destructive/batch operations (transactions, storage writes), which caps this score at 3.

3 / 5

Progressive Disclosure

References are well-signaled and one level deep, but all nine referenced files (wallet-operations.md, frontend-patterns.md, etc.) are missing from the bundle — navigation is broken, so structure is ineffective.

2 / 5

Total

12

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both what the skill covers and when to use it, with a well-defined MegaETH niche and minimal conflict risk. The only mild gap is trigger-term naturalness, which leans technical over colloquial.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — wallet operations, token swaps (Kyber), eth_sendRawTransactionSync (EIP-7966), JSON-RPC batching, mini-block subscriptions, Solady RedBlackTreeLib storage, MegaEVM gas, WebSocket keepalive, bridging, and mega-evme debugging — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers 'what' with a concrete coverage list and 'when' via an explicit 'Use when building on MegaETH, managing wallets, sending transactions, or deploying contracts' clause with concrete triggers.

5 / 5

Trigger Term Quality

Natural trigger phrases appear ('building on MegaETH, managing wallets, sending transactions, or deploying contracts'), but the bulk is technical jargon (EIP-7966, RedBlackTreeLib) with few synonyms or user-facing variations, leaving a few common terms missing.

4 / 5

Distinctiveness Conflict Risk

Clearly scoped to a niche (MegaETH development) with distinctive, chain-specific triggers, making overlap with other skills minimal.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 9 missing

Warning

Total

15

/

16

Passed

Repository
NeverSight/skills_feed
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.