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.
86
79%
Does it follow best practices?
Impact
100%
1.56xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0x70626a/monad-wingman/monad-wingman/SKILL.mdQuality
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 an explicit 'Triggers on' clause. However, it lacks specificity in describing concrete actions the skill performs (it says what it 'covers' but not what it actively does), and several of its trigger terms are generic enough to conflict with other blockchain development skills.
Suggestions
Replace 'covers' with specific concrete actions like 'Generates Solidity smart contracts, scaffolds dApps using Scaffold-Monad, deploys contracts to Monad testnet, and explains parallel execution EVM concepts.'
Narrow overly generic triggers like 'build' and 'create' by qualifying them (e.g., 'build on Monad', 'create Monad dApp') to reduce conflict risk with other development 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', 'scaffolds dApp projects'). | 2 / 3 |
Completeness | Explicitly answers both 'what' (Monad blockchain development tutor and builder covering Foundry workflow, Scaffold-Monad, parallel execution EVM, deployment patterns) and 'when' (triggers on specific terms like 'build', 'dApp', 'smart contract', etc.). The trigger clause is explicit. | 3 / 3 |
Trigger Term Quality | Includes a strong set of natural trigger terms users would actually say: 'build', 'create', 'dApp', 'smart contract', 'Solidity', 'DeFi', 'Monad', 'web3', 'MON', plus 'blockchain development task'. Good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | While Monad-specific terms like 'Monad', 'MON', 'Scaffold-Monad', and 'parallel execution EVM' are distinctive, generic triggers like 'build', 'create', 'smart contract', 'Solidity', 'DeFi', and 'web3' could easily conflict with other blockchain or general development skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
77%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 workflow clarity and executable examples throughout. Its main weaknesses are verbosity from including general Solidity/EVM knowledge that Claude already possesses (reentrancy, approve patterns, decimal handling) and a monolithic structure that could benefit from progressive disclosure via separate reference files. The Monad-specific content (chain config, --legacy flag, gas limit billing, prague EVM version) is genuinely valuable and well-presented.
Suggestions
Move general Solidity gotchas (reentrancy, approve pattern, SafeERC20, floating point, vault inflation) to a separate GOTCHAS.md reference file, keeping only Monad-specific gotchas inline
Extract the SpeedRun Ethereum challenges table and DeFi protocol patterns into separate reference files (e.g., CHALLENGES.md, DEFI_PATTERNS.md) with brief one-line references from the main skill
Remove explanations of concepts Claude already knows (e.g., what ERC-20 approve does, what reentrancy is) and keep only the code patterns and Monad-specific notes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~400+ lines) and contains some content Claude already knows well (ERC-20 approve pattern, reentrancy attacks, no floating point in Solidity, SafeERC20 usage). The Monad-specific content is valuable and earns its place, but general Solidity gotchas and DeFi patterns inflate the token budget significantly. The SpeedRun Ethereum table and DeFi protocol descriptions add bulk without much actionable Monad-specific value. | 2 / 3 |
Actionability | The skill provides fully executable code throughout: complete foundry.toml configs, deployment scripts with exact flags, curl commands for faucet/verification, Solidity contract examples, and TypeScript frontend hooks. Commands are copy-paste ready with correct Monad-specific parameters (chain IDs, RPC URLs, --legacy flag). | 3 / 3 |
Workflow Clarity | Both Workflow A (Foundry) and Workflow B (Scaffold-Monad) are clearly sequenced with numbered steps. The deployment workflow includes verification as a final step. The 'DO NOT' list serves as explicit validation guardrails. The security review checklist with Monad-specific checks provides a comprehensive pre-deployment validation checkpoint. | 3 / 3 |
Progressive Disclosure | All content is inlined in a single monolithic file with no references to external files for detailed topics. The SpeedRun Ethereum challenges, DeFi protocol patterns, and security gotchas could be split into separate reference files. The document is well-organized with clear headers, but its length (~400+ lines) would benefit from splitting into overview + detailed reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%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 | |
e437c3c
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.