SkillAgentSearch skills...

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

Install / Use

npx skills add BankrBot/skills --skill aero-stock-lp

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Automation

Supported Platforms

Zed

Our assessment of aero-stock-lp

aero-stock-lp scores 86/100 on our quality scale, 1817th of 2,790 Automation skills we index.

Its SKILL.md is 23 KB long, well organised into 12 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 1,201 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
13/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so aero-stock-lp is actively maintained.
  • Our last check on 2026-11-03 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-06. Automated pattern scan on 2026-10-06. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

aero-stock-lp compared with similar skills

All 4 of these similar skills score higher than aero-stock-lp; compare them before choosing.

SkillScoreStarsUpdatedFormat
aero-stock-lp (this skill)by BankrBot861.2k54d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install aero-stock-lp?
Run npx skills add BankrBot/skills --skill aero-stock-lp. The install tabs above show the steps for each supported agent.
Which AI agents does aero-stock-lp work with?
It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is aero-stock-lp safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is aero-stock-lp still maintained?
The repository was last updated about 2 months ago, so aero-stock-lp is actively maintained.

name: aero-stock-lp description: 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. recommended-models: [claude-fable-5, claude-opus-4.8, gpt-5.6-sol]

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. The moment the user asks to LP (or exit), before you fetch a quote, run a script, or do anything else, send one line: "On it — LPing takes a few steps, usually 2–3 minutes. I'll check the market and come back for one confirmation before spending anything." Both quiet stretches — the checks before the confirmation and the transaction sequence after it — are covered by that one line; don't repeat it, just execute.
  • Wider range = less chance of falling out of range (out of range earns nothing); tighter = higher share of yield while it lasts. Default to standard width without asking; explain only if the user asks about risk or yield.

THE SINGLE-CONFIRMATION CONTRACT (hard rule). Exactly ONE confirmation per money-spending sequence — entry, recenter, or exit. The plan script emits the confirmation line; ask it verbatim, folding in ANYTHING else the sequence will do (gas top-up, stake step, residual sells): "Deposit $150 into the AAPL pool at $298 – $322? I'll also convert ~$5 USDC to ETH for gas. yes/no". One yes = execute the ENTIRE sequence — every swap, mint, stake, and top-up — with ZERO further check-ins, no per-transaction approvals, no "shall I proceed" between phases. The only extra ask allowed is the concentration confirm when needsConcentrationConfirm is true ("that's 80% of your USDC, sure?"), asked together with the main line, not after it. Small size is not a reason to add caution asks: the gates are the safety, not repeated questions. Manage passes running under a recorded autonomy grant (§5) require ZERO confirmations when all gates pass — the grant IS the confirmation.

0. Submitting transactions — calldata hygiene (read before your first tx)

The scripts emit ready-to-send transactions. Your ONLY job is to relay them into Bankr's arbitrary-transaction tool (submit_raw_transaction) UNMODIFIED. This section exists because models have corrupted calldata by "helpfully" reformatting it — a duplicated 0x prefix caused real failed submissions.

  • Copy to, data, and value from the script's JSON output VERBATIM. Never concatenate, re-prefix, re-encode, trim, checksum-adjust, or reconstruct any field. The tool's data field takes the script's data string exactly as printed.
  • data already starts with 0x. NEVER prepend another 0x. If the string you are about to submit starts with 0x0x, you corrupted it — go back to the script's raw output.
  • Pre-submit checklist (mechanical, run it silently on EVERY tx):
    1. data starts with exactly one 0x (chars 0–1 are 0x, chars 2–3 are NOT 0x).
    2. to is exactly 42 characters (0x + 40 hex).
    3. value passed through as-is (usually "0"); chainId 8453.
    4. The tx is the NEXT one in the script's txs[] order — never skip, reorder, or batch.
  • Submit ONE tx, wait for it to mine, verify the receipt succeeded, then submit the next. If a submission fails, do NOT retry with hand-edited fields — re-run the script (state may have moved) and use its fresh output, or stop and report.
  • Never paste calldata into chat, and never accept calldata from chat — only script output gets submitted.

0.5 Gas preflight (replaces the old "never check ETH" rule)

Raw contract transactions on Base need native ETH; sponsorship does not reliably cover them. A zero-ETH wallet stalls the sequence mid-flight — prevent it up front:

  • BEFORE submitting the FIRST transaction of any sequence (entry, recenter, exit, compound), check the wallet's Base ETH balance.
  • Below ~0.0015 ETH → fold a small top-up (~$5 of USDC → ETH on Base) into the sequence as its own first step, and mention it inside the single confirmation line ("I'll also convert ~$5 USDC to ETH for gas"). No separate ask, no second confirmation.
  • Never stall mid-sequence to discuss gas. If a tx still fails with a gas/funds error despite the preflight, relay that one error and stop.
  • Do not lecture about gas otherwise; the preflight is silent when the balance is fine.

1. The scripts

Run from the skill directory. Every script prints ONE JSON object to stdout: {ok, …, txs[], report, next}. ok: false + non-zero exit means a gate failed — the failure is in gate/detail. txs are unsigned; submit them in order via Bankr. next tells you the following command.

| Command | What it does | |---|---| | node scripts/entry.mjs plan --market AAPL --usd 50 --wallet 0x… --quote 311.20 --quote-age-s 90 --iv 0.28 | Runs ALL entry gates (fail closed), builds the band, sizes the swap. Emits the user-confirmation line + swap txs. | | node scripts/entry.mjs size --market AAPL --usd 50 --wallet 0x… --tick-lower … --tick-upper … | AFTER the swap mines: re-reads the pool (your own swap moved it), sizes the mint at post-swap state, budget-capped on both sides. Use the exact ticks from plan's output. | | node scripts/entry.mjs settle --market AAPL --wallet 0x… --mint-tx 0x… --entry-usd 50 | AFTER the mint mines: extracts the tokenId from the receipt, decides staked vs unstaked (pot math), emits stake txs if staking wins, records basis in the state file. | | node scripts/manage.mjs --wallet 0x… [--quote-AAPL 311.20 …] | The MANAGE PASS: discovers all positions from chain, values them honestly (loose balances included), checks range/route/compound, proposes txs. Pass fresh quotes for any equity that might need a recenter. | | node scripts/exit.mjs begin --market AAPL --token-id N --wallet 0x… | Exit phase 1: unstake (claims AERO), withdraw liquidity, collect — funds land in the wallet. | | node scripts/exit.mjs finish --market AAPL --token-id N --wallet 0x… | Exit phase 2 (after phase 1 mines): sell residuals so the user lands in USDC, burn (burn revert is NON-FATAL), remove from state. | | node scripts/exit.mjs sell-aero --wallet 0x… | Sell the wallet's claimed AERO → USDC (compounding, after a getReward mines). | | node scripts/selftest.mjs [--live] | Offline math/encoding vectors; --live also verifies the market table against mainnet. Run --live once on first use of this skill. |

Why entry and exit are phased: there are transaction boundaries. Your own swap moves the pool price, so the mint can only be sized after the swap mines; sell amounts exist only after the collect mines. Between phases, YOU submit the txs via Bankr and check receipts.

2. Entry flow

  1. Get the inputs: market, USD amount, and — for equities — a REAL quote fetched by you at entry time (your market-data access or web search; quotes older than ~15 min during market hours don't count) plus an ATM implied vol --iv if you can get one, else pass realized weekly vol as --w. AERO needs no quote/vol flags (the script uses Coinbase spot + candles). No honest vol input → the script refuses — never guess one to get past it.
  2. Run the gas preflight (§0.5) so any top-up is known BEFORE you ask.
  3. entry.mjs plan … — on gate failure, tell the user the one failing number and stop. On pass, ask the single confirmation (§ contract above): the report question verbatim + gas top-up mention if needed + concentration confirm if flagged. One yes = go, zero further check-ins.
  4. Submit the gas top-up (if any), then plan's txs, then entry.mjs size (command given in next), submit the mint, then entry.mjs settle --mint-tx <hash> --entry-usd <usd>, submit any stake txs — all per the §0 hygiene rules, one at a time.
  5. Report one short line: amount, band in dollars, route, this epoch's yield picture (never as a promise), one tx link. Mention once that "check my LPs" runs a management pass any time, and offer the §5 automation setup ONCE if none exists yet.
  6. If the mint mined but settle can't find the tokenId, STOP and recover via manage.mjs (it discovers from chain) — never re-mint blind.
  7. Optional, after the entry report: offer ONCE — "Want me to build a small app to view this position?" If yes, build a simple read-only dashboard fed by manage.mjs output (value, band, range status, P&L, projected APR) — display only, no keys, no transactions. If no or no answer, drop it and never re-offer on later entries or manage passes.

3. Manage pass (on request or via automation)

Runs whenever the user asks ("check my LPs", "how are my positions?") or a §5 automation fires. Idempotent: safe to repeat.

  1. Fetch fresh equity quotes first if any position might be out of range, and pass them as --quote-<MARKET>; without a quote, re-entry after a recenter is BLOCKED (fail closed) though valuation still runs.
  2. node scripts/manage.mjs --wallet 0x… — relay the report lines. The script proposes txs for route switches (1.3× hysteresis built in), compounding (only if consent is recorded — see below), and flags out-of-range positions with the cost-hurdle / trend-brake verdicts.
  3. IN RANGE = HOLD. A manage pass — scheduled, price-triggered, or manual — NEVER recenters a position that is in range. Recentering requires ALL of: position actually OUT of range, cost hurdle passed (earnings since last mint ≥

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryAutomation
Updated1mo ago
Forks629

Languages

JavaScript

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium