Sato Hub
← Skills

Uniswap V4ClawHub · openclaw-consensus-bot

2,330 installs

Swap tokens and read pool state on Uniswap V4 (Base, Ethereum). Use when the agent needs to: (1) swap ERC20 tokens or ETH via Uniswap V4, (2) get pool info (price, tick, liquidity, fees), (3) find the best pool for a token pair, (4) quote expected swap output via the on-chain V4Quoter, (5) set up Permit2 approvals for the Universal Router, or (6) execute exact-input swaps with proper slippage prot

Executes fetched or decoded codeGenerates or handles private keys
Hosts contacted: mainnet.base.org
Credentials it expects: PRIVATE_KEY
Evidence lines
  • executes_fetched_code — SKILL.md: - No `eval()`, no `exec()`, no shell commands — pure TypeScript
  • generates_or_handles_keys — SKILL.md: need a private key via env var.
  • generates_or_handles_keys — SKILL.md: 3. **Approve tokens?** → `src/approve.ts` (write, ~100K gas, needs `PRIVATE_KEY`)
  • generates_or_handles_keys — SKILL.md: 4. **Execute swap?** → `src/swap.ts` (write, ~300-350K gas, needs `PRIVATE_KEY`)
  • generates_or_handles_keys — SKILL.md: PRIVATE_KEY=0x... npx tsx src/approve.ts \
  • generates_or_handles_keys — SKILL.md: **Env:** `PRIVATE_KEY` (required), `BASE_RPC_URL`

Registry's own scan (clawhub): suspicious on 2026-05-28 — their verdict, not ours. Our disclosure is a static description of what the skill declares and does; it is not a safety verdict. Source record: clawhub.ai/openclaw-consensus-bot/skills/uniswap-v4.

Install

openclaw skills install openclaw-consensus-bot/uniswap-v4

Copied from the registry's documented install form. Read the disclosure above first; it is the whole point of this page.

Observed record

First seen 2026-09-02. The weekly re-scan will record install growth and any change to the skill's content hash; one observation so far.

Cite this page

Sato Hub. "Uniswap V4 — skill disclosure on Sato Hub." Sato Hub, accessed 2026-09-06. https://satohub.ai/skills/clawhub%3Aopenclaw-consensus-bot%2Funiswap-v4

This page is refreshed daily. Citations include the date so a reader can tell which snapshot a claim came from.