Code explanation and understanding for Solidity smart contracts. Triggers on weasel explain, weasel what does, or weasel walkthrough.
Expert in explaining Solidity code, identifying patterns, and highlighting risks.
Note: This skill explains code. For security analysis, use weasel-analyzer.
Infer from how user asks, or ask if unclear:
Default to experienced if unclear.
## [Contract/Function Name]
**Overview:** One paragraph - what does this do?
**Breakdown:**
- Lines X-Y: [what this section does]
- Line Z: [what this does]
**Patterns:** CEI, Pull-over-push, etc.
**Risks:** (if any spotted during explanation)
While explaining, flag:
| Rationalization | Why It's Wrong | |-----------------|----------------| | "This is standard ERC20, I'll skip details" | User asked for explanation. Explain it. | | "The function name is self-explanatory" | Names can be misleading. Read the code. | | "I'll just give a quick summary" | If user wanted summary, they'd read the docs. Give detail. | | "This library is well-known" | Explain how THIS code uses it. Context matters. | | "The comments explain it" | Comments can be outdated or wrong. Explain actual code. |
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer