lp-plan
LP plan
Turn a chosen pool and capital budget into an unsigned, simulation-backed plan.
If a skill rule blocks progress, cite its file and exact rule, explain the missing input or authority, and continue independent work within this skill's boundary. User instructions govern workflow and style defaults; they do not bypass tool or financial controls.
Tool selection
When connecting or choosing tools, read official tools. 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.
Start here and connected workflow
For a chosen verified pool, first produce a field-complete draft showing known and missing identity, user budget, range and spend limits. Use the local range script only after token orientation and tick spacing are known. Missing quotes or simulation make the plan explicitly non-executable.
Receive analysis evidence or equivalent independently verified identity, risk and exit evidence. Return chain/wallet/pool identity, observation block, exact amounts/ticks, maximum spends, approval terms, targets/calldata/value, expected effects, simulation evidence, deadline and missing fields to lp-execute. Related skills are optional: if analysis is absent, verify identity, token behavior, hook/gauge risk and exit feasibility through trusted reads; if these cannot be established, retain a non-executable draft. If execution is absent, return the unsigned plan without asking for a signature.
Resolve script and reference paths from this installed skill directory, not the agent workspace. Discover related skills by exact name in the harness; do not assume a sibling directory or silently install another skill. For missing RPC, ABI, quote or wallet capabilities, use lp-setup if available, otherwise inventory actual tools and report the missing method. Instructions alone do not supply live data or execution integrations.