gno-mcp

Use when reasoning about, reading, or reviewing existing Gno realm code (`/r/` realms, `/p/` pure packages, `gno.land/...` import paths), discussing interrealm semantics (`cross(cur)`, `cur realm`, `PreviousRealm`, crossing functions), on-chain payments (`OriginSend`, `IsUserCall`, `cur.Previous().IsUserCall()`), evaluating realm `Render(path string) string` output for gnoweb, or the Gno memory and data model. Do NOT use this skill directly for tasks owned by its siblings — authoring/building/testing/deploying realms or scaffolding a Gno project goes to gno-build, explicit security audits to gno-audit, failed transactions/calls to gno-debug, first-contact "what is gno" teaching to gno-onboard; those skills load this one's references themselves.

Drive and judge e2e scenarios against the playground AUT (the containerized Claude + gnomcp + gno skill). Load whenever working on the playground harness at all — running or debugging e2e, QAing the MCP or skill end to end, authoring or editing a scenario, changing the driver or its references, or investigating an e2e failure — even if the user doesn't say "e2e". Interactive mode; batch runs go through the playground-driver agent.

Author, build, test, and deploy a Gno realm or pure package. Use whenever the user wants to write a new realm or `/p/` package, add or change a function in one, scaffold a Gno project, or deploy/publish `.gno` code to a chain — even when they only describe the on-chain behavior they want ("make a realm that stores notes", "deploy a counter I can bump", "add a withdraw function") without ever saying "build". This skill owns writing Gno source; reasoning about existing code stays with gno, security audits with gno-audit, failed transactions with gno-debug.

Diagnose and fix failed Gno transactions and calls. Use whenever a gno.land transaction failed, a gnomcp write tool returned an error (insufficient_funds, authentication_required, scope_mismatch, invalid sequence, panic, out of gas), a gno_call/gno_run/gno_addpkg result looks wrong, or the user pastes a chain error message — even if they never say "debug".

Teach gno.land from first contact, adapting to the user's background. Use when someone asks "what is gno", "how do I start with gno.land", "explain gno to me", says they are new to Gno or coming from another stack (Solidity, Solana, web2, anything), or asks beginner questions about realms, gnokey, or testnets — even without the word "onboard".

Run an explicit security audit of a Gno realm or pure package. Use when the user asks to audit a contract, asks "is this realm safe", wants a review before sending funds to or authorizing a session for a realm, or pastes Gno source asking what could go wrong.