ClawHub

Deploy Agent on Warden Studio

v1.0.0

Use Warden Studio (studio.wardenprotocol.org) via browser automation to register/publish a Community Agent to the Warden Agent Hub. Use when you need to (1) log in to Studio, (2) create/submit an agent listing, (3) configure API URL/auth, skills, avatar, and billing model, (4) pay registration + gas, and (5) verify the agent appears in Studio and in Warden's Agent Hub. Designed for safe, repeatable publishing with explicit confirmation gates.

⭐ 1· 1.6k·0 current·0 all-time
by@kryptopaid
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
ℹ
Purpose & Capability
The SKILL.md clearly describes browser automation of Warden Studio, including wallet/pay flows and form filling. However, the registry metadata declares no required binaries, dependencies, or primary credential even though the workflow depends on a Chromium browser and some automation capability (e.g., Playwright/Puppeteer/Selenium or a browser automation runtime). This is a documentation/requirements gap rather than evidence of malicious intent.
✓
Instruction Scope
Instructions remain focused on publishing an agent: open Studio, verify endpoint, fill form, show a submission summary, and require explicit user approval before publishing. The SKILL.md includes explicit prohibitions against requesting seed phrases/private keys and instructs entering API keys directly into the Studio UI. It does not instruct reading local secrets or unrelated system files.
✓
Install Mechanism
This is instruction-only with no install spec or downloaded code, so there is no install-time code execution risk in the package itself.
✓
Credentials
The skill declares no environment variables or credentials and does not request them in the instructions. It appropriately relies on user wallet confirmations in the browser and direct input of any API keys into the Studio UI, which is proportionate for a publishing flow that may require on-chain payments.
✓
Persistence & Privilege
The skill is not forced-always, does not request persistent privileges, and does not attempt to modify other skills or system-wide settings. It requires explicit user consent before executing the final publish step.
Assessment
This skill appears to be what it says: browser-automated publishing to Warden Studio with explicit confirmation gates and clear warnings not to handle private keys. Before installing/use: 1) Confirm your agent runtime actually provides browser automation (Chromium + automation library or service); the SKILL.md assumes that but the package doesn't declare it. 2) Be prepared to perform wallet confirmations in your own browser (do not paste seed phrases or private keys into chat). 3) Verify any fees and network (Base / USDC / gas) shown in the Studio UI before approving 'publish'. 4) If you need higher assurance, ask the skill author (or maintainer) which automation tool is intended and whether any automation will attempt to control an installed wallet extension—if it does, require the automation to stop for manual signing. If you are uncomfortable giving the agent autonomous browser control for wallet interactions, run the workflow manually or supervise the automation step-by-step.

Like a lobster shell, security has layers — review code before you run it.

agent identityvk97e96632z4qw90yv4x4mvyv6s80fyt5blockchainvk97e96632z4qw90yv4x4mvyv6s80fyt5latestvk97e96632z4qw90yv4x4mvyv6s80fyt5onchain agentsvk97e96632z4qw90yv4x4mvyv6s80fyt5wardenvk97e96632z4qw90yv4x4mvyv6s80fyt5warden studiovk97e96632z4qw90yv4x4mvyv6s80fyt5

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments