galleonlabs/crypto-defi-skills / packages/lp/skills/lp-setup
lp-setup
VerifiedSet 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.
| File | Kind | Size |
|---|---|---|
| ATTRIBUTION.md | markdown | 921 B |
| LICENSE | other | 1.0 KB |
| SKILL.md | skill md | 4.5 KB |
| agents/openai.yaml | config | 221 B |
| references/connections.md | markdown | 3.1 KB |
| references/official-tools.md | markdown | 3.9 KB |
| references/vfat.md | markdown | 2.9 KB |
| scripts/connection.mjs | script | 4.0 KB |
references/vfat.md
View on GitHub# VFAT access and readiness
Use VFAT as an optional public discovery interface or a user-selected position-management route. Reviewed 2026-09-05.
## Start without a wallet
Open [VFAT Yield](https://vfat.io/yield) with a public browser and wait for the table to finish loading. Record the selected Farms/Pools view, active filters, sort order, observation time and exact chain/protocol/pool. A loading shell or filtered empty table is not evidence of an empty market. The public page was verified to render farms without connecting a wallet; this does not verify its quotes or writes.
Use public address/ENS viewing only for an account the user selected. The [portfolio guide](https://docs.vfat.io/portfolio/) describes this read path. Do not connect a wallet, create a Sickle, or enable automation merely to inspect opportunities. A user address entered into a hosted service is visible to that provider.
## Choose a supported access path
- Public browser: inspect yield candidates and source links, then verify identity and economics with chain reads or a suitable existing protocol tool.
- Sickle contract reads: use current official ABIs with an existing RPC/ABI tool. Resolve the factory, Sickle, registry and deployed implementation for the intended chain; source constants are not a deployment registry.
- Integration source: [sickle-public](https://github.com/vfat-io/sickle-public) and [sickle-wrapper](https://github.com/vfat-io/sickle-wrapper) are official sources. The latter documents a wrapper SDK, but its reviewed manifest depends on a sibling local SDK. On 2026-10-19 only `@vfat-io/sickle-sdk` 0.1.0 was published, with no repository field; the wrapper SDK still returned 404. Treat ready-to-install SDK access as unavailable until upstream publishes or supplies a verified distribution.
No supported public VFAT MCP or general quoting API contract was verified. Do not invent a server, authentication token, CLI command or endpoint from browser network traffic. Use a documented upstream interface when one becomes available; record the version and access terms before integration. For Aerodrome capabilities already served by the maintained Sugar SDK, retain that path rather than adopting VFAT's fork by default.
## Readiness result
Return `provider`, `accessPath`, `observedAt`, `viewAndFilters`, `chainAndPool`, `readEvidence`, `supportedOperations`, `missing`, and `nextAction`. Keep browser discovery, RPC verification, quote construction, wallet authority and automation permissions as separate capabilities. An official repository or an enabled button proves none of the others.
A VFAT route can use a user-owned Sickle smart contract account, or a separately chosen ownership wrapper. Establish the actual owner and approved operators from chain state before describing custody. [Sickle documentation](https://docs.vfat.io/sickle/) explains the basic account model; the live implementation remains authoritative.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |