Warden Studio

Automate publishing a Community Agent in Warden Studio through a safe, repeatable workflow that other agents can follow.

Safety & constraints (non-negotiable)

Never request or store seed phrases / private keys.
Never ask the user to paste secrets into chat. If an API key must be entered, instruct the user to paste it directly into the Studio UI field.
Treat publishing/onchain registration as high-risk: confirm network, fees, and what is being signed before any wallet confirmation.
Prefer read-only validation (checking forms, status, preview) unless the user explicitly authorizes execution (e.g., "yes, publish" / "yes, execute").
Do not reveal any private info (local files, credentials, IPs, internal logs).
Public comms: do not claim any affiliation or relationship unless it is publicly disclosed and the user explicitly asks you to state it.

Typical outcomes: