monad-wingman

Monad blockchain development tutor and builder. Triggers on "build", "create", "dApp", "smart contract", "Solidity", "DeFi", "Monad", "web3", "MON", or any blockchain development task. Covers Foundry-first workflow, Scaffold-Monad, parallel execution EVM, and Monad-specific deployment patterns.

1.56x

Quality

76%

Does it follow best practices?

Impact

100%

1.56x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./data/skills-md/0x70626a/monad-wingman/monad-wingman/SKILL.md

Quality

Discovery

82%

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

The description has strong trigger term coverage and good completeness with explicit trigger guidance. However, it lacks specificity in describing concrete actions (what it actually does beyond 'tutor and builder'), and several of its trigger terms are too generic, creating potential conflicts with other blockchain development skills. The Monad-specific elements provide some distinctiveness but are diluted by the broad terms.

Suggestions

Replace vague 'tutor and builder' with specific concrete actions like 'generates Solidity smart contracts, scaffolds dApp projects with Scaffold-Monad, deploys contracts to Monad testnet, explains parallel execution EVM concepts'.

Narrow overly broad trigger terms by qualifying them with 'Monad' context, e.g., change 'Triggers on build, create, smart contract, Solidity' to specify these should be in the context of Monad blockchain specifically, to reduce conflict with general Solidity/blockchain skills.

Dimension	Reasoning	Score
Specificity	Names the domain (Monad blockchain development) and mentions some specific tools/concepts like Foundry-first workflow, Scaffold-Monad, parallel execution EVM, and deployment patterns, but doesn't list concrete actions the skill performs (e.g., 'generates smart contracts', 'deploys to Monad testnet'). 'Tutor and builder' is somewhat vague.	2 / 3
Completeness	Clearly answers both 'what' (Monad blockchain development tutoring and building, covering Foundry workflow, Scaffold-Monad, parallel execution EVM, deployment patterns) and 'when' (explicit trigger terms listed with 'Triggers on...'). The trigger guidance is explicit and well-defined.	3 / 3
Trigger Term Quality	Explicitly lists natural trigger terms users would say: 'build', 'create', 'dApp', 'smart contract', 'Solidity', 'DeFi', 'Monad', 'web3', 'MON', plus 'blockchain development task'. Good coverage of terms a developer would naturally use.	3 / 3
Distinctiveness Conflict Risk	While 'Monad' is distinctive, many trigger terms like 'build', 'create', 'smart contract', 'Solidity', 'DeFi', 'web3' are very broad and would overlap with any general blockchain/Solidity development skill. Only 'Monad', 'MON', 'Scaffold-Monad' are truly distinctive.	2 / 3
	Total	10 / 12 Passed

Implementation

70%

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

This is a highly actionable and well-structured Monad development guide with excellent executable examples and clear workflows. Its main weakness is extreme length and lack of progressive disclosure — everything is crammed into one monolithic file with significant repetition (the --legacy flag and forge script requirements are stated 4-5 times). Splitting into referenced sub-files would dramatically improve token efficiency while preserving the strong actionability.

Suggestions

Split content into referenced files: e.g., GOTCHAS.md (critical gotchas), SECURITY_CHECKLIST.md, DEFI_PATTERNS.md, SPEEDRUN.md — keep only the Monad critical differences and primary workflows in SKILL.md

Remove redundant repetitions of the --legacy flag requirement, forge script mandate, and gas limit billing — state each rule once in the 'Critical Differences' section and reference it elsewhere rather than restating

Move the SpeedRun Ethereum challenges table to a separate file — it's reference material not directly actionable for Monad development

Trim the DeFi protocol patterns section which is mostly generic EVM knowledge (AMM formula, ERC-4626) with minimal Monad-specific content

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~400+ lines) with some redundancy — deployment rules, the --legacy flag requirement, and forge script warnings are repeated 4-5 times across sections. Some content like the SpeedRun Ethereum table and DeFi protocol descriptions (Euler, Morpho) add bulk without providing actionable Monad-specific guidance. However, most content is genuinely useful and not explaining things Claude already knows (e.g., 'what is a blockchain').	2 / 3
Actionability	Excellent actionability throughout — executable bash commands, complete Solidity code examples, specific configuration files (foundry.toml, scaffold.config.ts), curl commands for faucet/verification, and a full deploy script template. Code is copy-paste ready with real RPC URLs, chain IDs, and correct flags.	3 / 3
Workflow Clarity	Both Workflow A (Foundry) and Workflow B (Scaffold-Monad) are clearly sequenced with numbered steps. The deployment workflow includes explicit validation via contract verification. The security review checklist serves as a pre-deployment validation checkpoint. The 'DO NOT' list and critical gotchas section provide clear guardrails. Destructive operations (mainnet deployment) have explicit safety requirements (hardware wallet).	3 / 3
Progressive Disclosure	This is a monolithic wall of text with no bundle files and no references to external documents. All content — chain config, two full workflows, deployment templates, 8 gotchas with code examples, DeFi patterns, SpeedRun curriculum, security checklist — is inlined in a single file. The security checklist, DeFi patterns, SpeedRun table, and gotchas could each be separate referenced files to reduce the token footprint of the main skill.	1 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (568 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: NeverSight/skills_feed
Commit: aa009ea

Reviewed: about 2 hours ago

Table of Contents

Discovery Implementation Validation

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.