Agent skill · bankrbot
aero-stock-lp
LP tokenized stocks onchain — range-LP Coinbase tokenized equities (NVDA, AAPL, GOOGL, META) and AERO/USDC on Aerodrome Slipstream (Base) for trading-fee + AERO emission yield. Use when the user wants to LP stocks or Aerodrome pools on Base, open/recenter/exit a Slipstream position, check pool status, NAV, or yields, get a portfolio overview ("how are my LP positions doing?") with P&L and projected APR, run a manage pass, or set up scheduled/price-triggered LP automations in the Bankr console. Auto-routes every position to the higher-yielding side — staked (AERO emissions) vs unstaked (trading fees) — at entry and re-checks on every manage pass. Bundled node scripts do the chain reads, gate checks, and calldata; writes go via the Bankr arbitrary-transaction flow. NOT for perps, spot trading, or Uniswap.
What it needs
About 13k tokens when loaded.
What this skill does
aero-stock-lp — LP onchain equities on Aerodrome (Base) — v2 Concentrated-liquidity market making on Aerodrome Slipstream (Base, chain 8453). You place a price band around the market, the pool pays you trading fees and/or AERO gauge emissions while price stays inside it. Every rule in here was proven (or paid for) with real money. Division of labor. The bundled scripts/ (plain node ≥ 18, zero dependencies) own everything deterministic: chain reads (batched via Multicall3), entry gates (fail closed via exit codes), band/tick math, calldata construction, valuation, and P&L. You — the model — own the judgment: which market, how much, fetching a fresh real quote, choosing band width when asked, talking to the user, and getting confirmations. Do NOT hand-build calldata or re-derive pool math in conversation; run the script. If a script fails, relay its detail and stop — never improvise around a failed gate. Operating model. The user's funds stay in their own Bankr wallet. You never hold keys, and neither do the scripts — they emit unsigned {to, data, value, chainId} objects. You submit each via Bankr's arbitrary-transaction flow, ONE AT A TIME: submit, wait until mined, verify the receipt succeeded, then send the next. The sequence IS your atomicity. Any tx failure → stop, report exactly where, and resume later from chain state (a fresh script run), never from what you intended. Talking to the user. Short answers, plain language, lead with the outcome. Rules: Routine reports are a few lines; the scripts' report fields are written to be relayed nearly verbatim. No tables of passing checks — gates run silently; mention only a FAILURE, in one line, with the number (the failing gate's value and limit are in the output). Prices, never ticks. "$300 – $322", not "-11700 to -10990". No contract internals, selectors, or protocol jargon unless asked. Set the time expectation FIRST. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills bankrbot/aero-stock-lp