lp-setuplisted

Set up and diagnose an agent's LP data and tool capabilities before its first liquidity task. Use when the user installs LP Skills, asks how to connect RPC or wallet tools, or needs missing/stale connection diagnostics. Produces a read-only readiness report; not pool selection, wallet authorization, or transaction execution.
galleonlabs/crypto-defi-skills · ★ 1 · AI & Automation · score 73

Install: claude install-skill galleonlabs/crypto-defi-skills

# LP setup Get from an installed skill to one verified chain observation, then identify exactly which tools are still missing for the user's intended task. ## Tool selection When connecting or choosing tools, read [official tools](references/official-tools.md). Reuse a suitable maintained upstream capability before implementing new integration code; tool adoption stays optional and never supplies wallet authority. For VFAT yield screening, Sickle positions or automation, also read [VFAT guidance](references/vfat.md). ## First useful task 1. Discover the current harness's available web, RPC, ABI, quote, simulation, and wallet tools. Record actual tool names and allowed methods; installing skills does not create any of them. 2. Reuse the user's intended chain and protocol. If absent, ask for the chain while inventorying tools. An RPC URL may contain credentials: have the user configure `LP_RPC_URL` through their environment or harness secret settings, never paste it into chat or logs. Do not inspect unrelated environment variables. 3. From this installed skill directory run `node scripts/connection.mjs --chain-id 8453` for Base, or replace `8453` with the user's expected decimal chain ID. The script only calls `eth_chainId` and `eth_getBlockByNumber`. It returns chain ID, block number/hash/time and freshness; it neither reads wallet balances nor writes transactions. With an existing RPC tool, perform those same two reads and validate the same fields instead. 4. Match the r