grimoire-uniswap

Retrieves Uniswap router metadata using the Grimoire venue CLI. Use when you need router addresses, adapter information, or Uniswap V3/V4 details.

By franalgaba · 1,061 installs

npx skills add franalgaba/grimoire --skill grimoire-uniswap

Source repository · Upstream listing

Grimoire Uniswap Skill Use this skill to inspect Uniswap metadata and produce token/pool snapshots for spells. Preferred invocations: grimoire venue uniswap ... npx y @grimoirelabs/cli venue uniswap ... (no install) bun run packages/cli/src/index.ts venue uniswap ... (repo local) grimoire uniswap ... (direct binary from @grimoirelabs/venues ) Recommended preflight: grimoire venue doctor adapter uniswap chain 1 rpc url <rpc json Commands grimoire venue uniswap info — adapter metadata grimoire venue uniswap routers [ chain <id ] — router addresses per chain grimoire venue uniswap tokens [ chain <id ] [ symbol <sym ] [ address <addr ] [ source <url ] — token list lookup grimoire venue uniswap tokens snapshot [ chain <id ] [ symbol <sym ] [ address <addr ] [ source <url ] — generate spell params: block for tokens (agent only) grimoire venue uniswap pools token0 <address symbol token1 <address symbol [ chain <id ] [ fee <bps ] [ limit <n ] [ source <url ] [ endpoint <url ] [ graph key <key ] [ subgraph id <id ] [ rpc url <url ] [ factory <address ] — find pools for a token pair grimoire venue uniswap pools snapshot token0 <address symbol token1 <address symbol [ chain <id ] [ fee <bps ] [ limit <n ] [ source <url ] [ endpoint <url ] [ graph key <key ] [ subgraph id <id ] [ rpc url <url ] [ factory <address ] — generate spell params: block for pools (agent only) Pool Data Sources Pools can be fetched from The Graph (subgraph) or directly from on chain factory contracts: Subgraph (default when GRAPH API KEY is set): queries The Graph decentralized network. Built in subgraph IDs for Ethereum, Optimism, Polygon, Base, Arbitrum. RPC (fallback): if no usable graph config is present, pools uses on chain factory lookups (with rpc url / RPC URL when provided, otherwise chain default RPC where available). To force RPC mode: provide rpc url and omit graph key . Environment Variables Variable Description GRAPH API KEY The Graph API key for subgraph queries (get one at https://thegraph.com/studio/apikeys/) RPC URL Fallback RPC URL for on chain pool lookups Examples Use tokens snapshot or pools snapshot to emit a params: block for spell inputs. These are agent only commands (output suppressed in interactive mode). Metric Surface (Spell Comparisons) Uniswap V3 and V4 expose quote out for protocol comparison: Selector fields: required: asset out optional: amount (defaults to 1 unit of input asset), fee tier V4 optional: tick spacing Spell Constraints When writing swap actions in .spell files targeting Uniswap, use with clauses to set constraints: fee tier is required. The adapter throws if fee tier is not specified. It is an action parameter (not a constraint) and is extracted from the with() clause. Common fee tiers: 500 (0.05%), 3000 (0.3%), 10000 (1%). Parameter Type Description fee tier integer (bps) Required. Uniswap pool fee tier (e.g. 500 , 3000 , 10000 ) Constraint Type Description max slippage integer (bps) Maximum slippage in basis points (e.g. 50 = 0.5%) min output integer (wei) Minimum output amount floor max input integer (wei) Maximum input amount cap deadline integer (seconds) Transaction deadline from now require quote boolean Fail if on chain quote fetch fails require simulation boolean Fail if simulation unavailable max gas integer (wei) Gas estimate cap Always set both max slippage and min output for swaps to prevent unexpected losses. Supported Adapters Adapter Router Approval Flow @uniswap v3 SwapRouter02 Standard ERC20 approve @uniswap v4 Universal Router Permit2 Notes CLI currently exposes V3 metadata. V4 adapter is available programmatically via createUniswapV4Adapter() . For metadata lookups ( tokens , pools ), use grimoire venue uniswap ... even when your spell venue is uniswap v4 . Outputs JSON/table; tokens and pools also support format spell . Prefer format json for automation and reproducible snapshots. Only metadata is exposed (no on chain quote endpoints).