OpenClaw

warden-app

Use the Warden App (agentic wallet) via browser automation to execute crypto tasks (swap, bridge, deposit/withdraw, perps, portfolio/research) and to build an OpenClaw skill wrapper other agents can use. Use when you need to (1) navigate the Warden UI, (2) connect a wallet, (3) place trades/swaps, (4) check balances/positions, or (5) document repeatable Warden workflows safely (no key leakage, explicit confirmations).

deiu0 source installs☆ 0 Repository stars

View source ↗Installation SKILL.md ↗

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

SkillHub CLI

skillhub install deiu/warden-app

Inspect the source and compatibility requirements, then follow its installation steps.

Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.

View source ↗Guides

Skill instructions

Warden App

Automate common actions in the Warden App through a safe, repeatable workflow that other agents can follow.

Safety & constraints (non-negotiable)

Never request or store seed phrases / private keys.
Treat all onchain actions as high-risk: confirm chain, token, amount, slippage, fees before signing.
Prefer read-only actions unless the user explicitly authorizes execution (e.g., they say: "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.

Workflow (UI automation)

0) Preconditions

A Chromium browser is available (Chrome/Brave/Edge/Chromium). (Firefox not supported.)
User is logged into the Warden App (and any required email/2FA is completed).
Wallet connection method is clear:
- embedded Warden wallet, or
- external wallet (e.g., MetaMask/Rabby/etc.).

If any of the above is missing, stop and ask the user to do that step.

1) Open + stabilize the UI

Open the Warden App URL (user-provided).
Wait for the dashboard/home view to load.
Take a snapshot and identify:
- current network
- wallet/account label
- balances overview / portfolio view

2) Read-only actions (default)

Use these first when the user asks “what do we have / what’s going on?”

Portfolio: balances, chains, token list
Positions (perps): open positions, PnL, leverage
Activity/history: recent swaps/trades, deposits/withdrawals
Rewards/points (if applicable): PUMPs / quests / referrals

3) Transactional actions (requires explicit approval each time)

Execution gate: Do not click the final confirm button unless the user explicitly replies with "yes, execute" (or an unambiguous equivalent).

Before clicking a final “Confirm/Swap/Trade” button, summarize:

chain + token in/out + amount
slippage + fees
expected execution (market/l...

Source information

Source: github
Repository: openclaw/skills
Path: skills/deiu/warden-app
Version: —
Commit: bdd3f241c5f07a2a2ad5936bdd2c259b6f424e9a
Classification source: rules
Status: active
Visibility: public

These signals come from indexed source analysis and may lag behind changes. Check the current source files.

Extracted content

SKILL.md

# Warden App

Automate common actions in the Warden App through a safe, repeatable workflow that other agents can follow.

## Safety & constraints (non-negotiable)

- Never request or store seed phrases / private keys.
- Treat all onchain actions as **high-risk**: confirm chain, token, amount, slippage, fees **before** signing.
- Prefer read-only actions unless the user explicitly authorizes execution (e.g., they say: "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.

## Workflow (UI automation)

### 0) Preconditions

1. A Chromium browser is available (Chrome/Brave/Edge/Chromium). (Firefox not supported.)
2. User is logged into the Warden App (and any required email/2FA is completed).
3. Wallet connection method is clear:
   - embedded Warden wallet, or
   - external wallet (e.g., MetaMask/Rabby/etc.).

If any of the above is missing, stop and ask the user to do that step.

### 1) Open + stabilize the UI

- Open the Warden App URL (user-provided).
- Wait for the dashboard/home view to load.
- Take a snapshot and identify:
  - current network
  - wallet/account label
  - balances overview / portfolio view

### 2) Read-only actions (default)

Use these first when the user asks “what do we have / what’s going on?”

- Portfolio: balances, chains, token list
- Positions (perps): open positions, PnL, leverage
- Activity/history: recent swaps/trades, deposits/withdrawals
- Rewards/points (if applicable): PUMPs / quests / referrals

### 3) Transactional actions (requires explicit approval each time)

**Execution gate:** Do not click the final confirm button unless the user explicitly replies with **"yes, execute"** (or an unambiguous equivalent).

Before clicking a final “Confirm/Swap/Trade” button, summarize:
- chain + token in/out + amount
- slippage + fees
- expected execution (market/l...

Related skills

OpenClaw

openbotx

An open-source platform for orchestrating AI agents — secure, simple, and built for everyone. Multi-agent, real-time task board, web control panel, skills system, browser automation, multi-provider, scheduler,...

☆ 83View skill

OpenClaw