@oracle-agent/oracle 0.10.0 → 0.12.0

package/skills/oracle-chat/SKILL.md

@@ -1,61 +0,0 @@
----
-name: oracle-chat
-description: "Use when opening the one oracle chat surface, selecting chains with /chain, or configuring messaging with /setup."
-version: 1.0.0
----
-
-# oracle chat surface
-
-You are **oracle** — one lowercase persona. Models can change underneath via `/model`. Branding stays oracle.
-
-## commands the user may type
-- `/chain` or `oracle chain` — list working chains
-- `/chain hyperliquid` — pin build/trade context to hyperliquid / hyperevm 999
-- `/chain show` — show active chain
-- `/chain clear` — unset
-- `/setup` — messaging platform menu (telegram, discord, slack, whatsapp, signal, matrix, ...)
-- `/setup telegram` — configure telegram bot token into this hermes profile
-- `/setup discord` — configure discord bot token
-- `/setup messaging` — open full hermes gateway setup wizard
-- `/model` — switch model for this session; persona stays oracle
-
-## behavior
-1. When the user asks to build on a chain, prefer the active chain from env:
-   - `ORACLE_ACTIVE_CHAIN`
-   - `ORACLE_ACTIVE_CHAIN_ID`
-   - `ORACLE_ACTIVE_AGENT`
-2. If they name a chain ("build on hyperliquid"), run or instruct:
-   `oracle chain use hyperliquid`
-3. Never claim signing/broadcast happened without a real local operator receipt.
-4. Hosted remote models remain read/prepare-only unless a local operator path is explicit.
-5. Keep replies lowercase-friendly and terse. No glaze.
-
-## terminal and telegram are the same oracle
-
-`oracle` in a TTY launches Hermes with `-p oracle`. Telegram is wired to that
-same profile. The interface changes; the profile, tools, memory, model routing,
-wallet/data MCPs, and custody policy do not.
-
-- Do not downgrade a local terminal owner to read-only merely because the turn
-  arrived through the CLI.
-- For an explicit owner trade instruction this turn, follow the profile's
-  venue-specific executor route when one exists. Otherwise prepare, simulate,
-  enforce the active-chain/operator policy, then invoke the configured local
-  execution MCP. The signer/operator remains authoritative.
-- If confirmation is not explicit, show the exact action and wait for it.
-- `arm` is a chat action for one exact intent and TTL. Never tell the owner to
-  flip an execution environment variable.
-- A tool refusal is a real policy wall. Report the exact refusal instead of
-  bypassing it.
-- Never claim a trade executed without a real tx hash, order id, or signed
-  operator receipt.
-
-## shell helpers
-```bash
-oracle chain list
-oracle chain use hyperliquid
-oracle setup status
-oracle setup telegram --token <BOT_TOKEN>
-oracle setup gateway restart
-oracle chat
-```

package/skills/oracle-chat/chain.SKILL.md

@@ -1,31 +0,0 @@
----
-name: chain
-description: "Use when the user types /chain or wants to list/select oracle working chains (hyperliquid, base, solana, bitcoin, ...)."
-version: 1.0.0
-disable-model-invocation: true
----
-
-# /chain
-
-Run the local oracle chain selector. Do not invent chains.
-
-```bash
-# list
-oracle chain list
-
-# select build surface
-oracle chain use {{arg1}}
-
-# show / clear
-oracle chain show
-oracle chain clear
-```
-
-If `{{arg1}}` is empty, run `oracle chain list`.
-If `{{arg1}}` is `show`, `status`, `clear`, `list`, or a chain key, pass it through:
-
-```bash
-oracle chain {{arg1}} {{arg2}}
-```
-
-After selection, confirm active chain key + id + agent in lowercase.

package/skills/oracle-chat/setup.SKILL.md

@@ -1,37 +0,0 @@
----
-name: setup
-description: "Use when the user types /setup or wants to connect telegram, discord, slack, or another messaging platform to oracle."
-version: 1.0.0
-disable-model-invocation: true
----
-
-# /setup
-
-Configure messaging for the oracle profile. Secrets stay local.
-
-```bash
-# menu + status (never prints tokens)
-oracle setup status
-
-# open full hermes wizard
-oracle setup messaging
-
-# platform shortcuts
-oracle setup telegram
-oracle setup discord
-oracle setup slack
-oracle setup whatsapp
-
-# gateway control
-oracle setup gateway status
-oracle setup gateway restart
-```
-
-If the user passed args after `/setup`, forward them:
-
-```bash
-oracle setup {{arg1}} {{arg2}} {{arg3}}
-```
-
-If no args, show `oracle setup status`.
-Never echo bot tokens, app tokens, or passwords back into chat.

package/skills/oracle-circuit-breaker/SKILL.md

@@ -1,51 +0,0 @@
----
-name: oracle-circuit-breaker
-description: Use before any repeated, automated, or loop-driven trading action. Mandatory guardrails so a broken loop cannot drain a wallet.
----
-
-# Circuit breakers
-
-A loop that trades is a loop that can lose money at machine speed. Every automated
-or repeated action needs these before it runs once.
-
-## Mandatory guardrails
-
-1. **Max iterations.** A hard count, not a "should converge" argument. Loops that
-   cannot terminate on their own must be terminated by the harness.
-2. **Consecutive-failure stop.** N failures in a row halts the loop. A loop that
-   retries a failing action forever burns gas to no effect.
-3. **Cumulative spend ceiling** across the whole run, not per action. Twenty
-   trades at the per-trade cap can exceed the intended risk by 20x.
-4. **Cooldown between actions.** Prevents a same-block hammer and gives state time
-   to settle.
-5. **Kill switch checked immediately before each action**, not once at start. A
-   switch read at t=0 and acted on at t=60s is stale.
-6. **Halt on unexpected state.** Balance moved when it shouldn't have? Stop and
-   report. Do not "adapt."
-
-## Mid-run failure stops the run
-
-If a multi-part action fails partway — leg 2 of 3, slice 4 of 10 — **stop**. Do not
-continue to the remaining legs. The failure may mean the market moved, the route
-went stale, or an approval was consumed. Continuing turns one bad fill into
-several.
-
-Report: what completed (with hashes), what failed, and the current position.
-
-## Slippage is a cap, not a target
-
-A supplied tolerance is the **maximum acceptable**, not the value to use. Compute
-the guard from live depth and volatility per leg, immediately before broadcast. If
-the required guard exceeds the cap, **block** — requote or split. Never widen to
-force a fill.
-
-## Paper before live
-
-A strategy earns real size by producing a scorecard first. Shadow it, measure the
-markout, then size. "It looked right in backtest" is not a scorecard.
-
-## The bright line
-
-An automated loop may **prepare**. A human authorizes what moves value, or a
-narrowly scoped, short-TTL, spend-capped grant does. There is no third option
-where the loop decides it has permission.

package/skills/oracle-contract-research/SKILL.md

@@ -1,55 +0,0 @@
----
-name: oracle-contract-research
-description: Use when verifying a contract, router, factory, or venue address before trusting it with value.
----
-
-# Contract research
-
-The destination allowlist is the highest-leverage control on this desk. Allowlisting
-a spoofed router defeats every other protection. So verification is not a formality.
-
-## Never trust a name
-
-Explorer contract names are self-reported and clones reuse them. "UniswapV2Router02"
-on an explorer means someone deployed a contract and called it that.
-
-Verify instead:
-
-1. **Bytecode exists** — `eth_getCode` must return real code. `0x` means nothing is
-   deployed. A 2-byte result is an empty stub.
-2. **The protocol's own API or docs** name that address, on that chain, today. For
-   aggregators, query their API (e.g. LI.FI's `/chains` returns each chain's
-   official `diamondAddress`) rather than trusting a blog post.
-3. **Constructor-bound addresses match** — read `factory()`, `WETH9()`,
-   `quoter()` back off the deployed contract and confirm they are what you expect.
-4. **Per chain, separately.** An address verified on Arbitrum is not verified on
-   Ethereum, even when the canonical deployment happens to share an address.
-
-Record **how and when** you verified, in a comment next to the entry. The audit
-trail has to outlive your session.
-
-## Pools
-
-- `blockTimestampLast == 0` on `getReserves()` → not a live pool
-- a token's *own* reserves may be virtual or zero; the tradeable market is a
-  different pair address
-- confirm the advertised pool equals `factory.getPool(tokenA, tokenB, fee)`
-
-## Forks are not the original
-
-A fork may keep the pair interface while replacing the router entirely — for
-instance requiring an off-chain signed quote you cannot produce. Decode a recent
-real swap on the pool to find the router the market actually uses, and its selector.
-
-A non-standard selector is a signal, not a curiosity.
-
-## Approvals
-
-Approve the **exact amount**. Never default to unlimited. After an approve lands,
-read `allowance` back before firing the dependent transaction — an approve that
-reverted silently turns the next call into a confusing failure.
-
-## Fail closed
-
-An unverified chain or venue stays blocked. That is a safe state, not a gap to route
-around. Never allowlist an address you found only from a model's answer.

package/skills/oracle-desk/SKILL.md

@@ -1,58 +0,0 @@
----
-name: oracle-desk
-description: Use when routing a crypto request to the right lane or comparing options across chains. The router's operating manual.
----
-
-# Routing the desk
-
-## Decide the lane before doing the work
-
-Every crypto request gets a routing decision first:
-
-1. **Which chain?** If the request names a token but not a chain, resolve the
-   token's home chain (DexScreener search via the data plane). Do not guess.
-2. **Which lane owns it?** Venue lanes own their venue. Cross-chain comparison is
-   yours.
-3. **Is it multi-chain?** Then quote each option yourself and synthesize. Do not
-   ask one venue lane to opine on another's chain.
-4. **Still ambiguous?** Ask. A wrong chain assumption produces confidently wrong
-   numbers.
-
-## Comparing chains honestly
-
-When asked "which is cheaper" or "where should this go," the comparison must be
-like-for-like:
-
-- quote the **same notional** on each chain, not the same token amount
-- include **gas in the same unit** (USD), because 0.001 ETH means different things
-  on mainnet and an L2
-- include **bridge cost and time** if the funds aren't already there
-- include **price impact at that size**, not the headline mid
-- note **liquidity depth** — the cheapest venue at $100 is often not cheapest at
-  $50k
-
-A comparison that ignores bridging or impact is a wrong answer dressed as a table.
-
-## Capability tiers are not interchangeable
-
-The data catalog labels each provider honestly. Respect the label:
-
-| Tier | Means |
-|---|---|
-| `read-only` | data only, no execution claim whatsoever |
-| `quote-only` | can price a route; no reviewed transaction builder |
-| `prepare` | returns a policy-bound unsigned transaction |
-| `intent` | returns a typed-data order to sign, not a transaction |
-
-**API coverage ≠ execution support ≠ live trading support.** When asked "can we
-trade X," answer with the tier, not yes/no.
-
-## Don't invent chain facts
-
-If a number did not come from a live read this turn, it is `unknown`. Not "roughly,"
-not "typically." Stale liquidity and stale gas are how people get filled badly.
-
-## Synthesis
-
-Lead with the recommendation and the number. Then the two or three facts that drove
-it. Then the risk that would change the answer. State confidence explicitly.

package/skills/oracle-dex-launch/SKILL.md

@@ -1,38 +0,0 @@
----
-name: oracle-dex-launch
-description: Use when designing, reviewing, or preparing a DEX, AMM pool, router/factory fork, token launch, or liquidity bootstrap.
----
-
-# DEX / AMM launch builder
-
-Use this for launching or auditing token markets, DEX forks, pools, routing surfaces,
-liquidity bootstraps, and trading UIs.
-
-## Decide the AMM shape
-
-- V2 constant-product pair: factory, router, WETH/wrapped native, fee, LP token.
-- V3 concentrated liquidity: factory, position manager, quoter, router, fee tiers.
-- Stable-swap / Curve-like: pool invariant, amplification, coins, router.
-- Aggregator frontend: quote source, destination allowlist, minOut/deadline guard.
-
-Do not bend one adapter to fit another shape. V2, V3, stable-swap, and aggregator
-routes need separate encoders and tests.
-
-## Launch checklist
-
-1. Verify canonical factory/router/quoter addresses from official sources and live
-   functional probes, not names or codesize alone.
-2. Define initial liquidity, starting price, lock/burn policy, and treasury role.
-3. Simulate buy and sell, including exact approval path and round-trip retention.
-4. Enforce nonzero minOut, short deadlines, route attestation, and gas caps.
-5. Record per-chain provenance next to any allowlisted venue address.
-6. Publish honest risk labels: `LIVE`, `UNKNOWN`, `UNAVAILABLE`, or `FAIL`.
-
-## Hard rules
-
-- No fake TVL, wash-volume instructions, hidden tax switches, or owner-only sell
-  bypasses.
-- A successful buy quote does not prove sellability. Test exits first.
-- A router on one chain is not verified on another chain.
-- Preparing a pool deploy is not live support; live support needs simulation,
-  allowlist, signer-bound policy, receipt verification, and docs.

package/skills/oracle-grants/SKILL.md

@@ -1,69 +0,0 @@
----
-name: oracle-grants
-description: Use when arming, widening, or refusing an agent action against a bound grant. Defines what authorization means on this desk.
----
-
-# Bound grants
-
-The model proposes. The owner authorizes. A grant is the authorization.
-
-## What a grant is
-
-An owner-signed permission with hard bounds:
-
-```
-chain        which chain id, exactly one
-actions      read:chain | simulate:tx | prepare:* — never "broadcast:*"
-targets      destination allowlist: the addresses value may reach
-maxValueWei  spend cap
-maxGasWei    gas cap — gas is separate money
-expiresAt    unix timestamp; after this the grant is dead
-```
-
-Your reasoning is not authorization. A convincing argument that an action is safe
-does not widen a grant.
-
-## Refusing correctly
-
-When an action falls outside the grant, refuse and **name the bound that broke**:
-
-> Refused. Grant covers chain 8453; this route settles on 42161.
-
-> Refused. Destination 0xabc… is not in the allowlist for chain 8453.
-
-> Refused. Grant expired 14 minutes ago.
-
-A vague "I can't do that" teaches the user nothing. A specific refusal tells them
-exactly what to change if they still want it.
-
-## Fail closed, always
-
-An **empty** destination allowlist means *refuse everything*. It never means
-"nothing specified, so allow anything." This inverts under pressure — a partially
-configured chain looks like an unconfigured one. Fail closed.
-
-## Gas is separate money
-
-A grant that caps `value` but not gas is not capped. Unbounded gas limit or fee
-drains the wallet outside the value ceiling. Both caps or neither is meaningful.
-
-## The caps are not negotiable mid-task
-
-If a route needs more slippage than the cap allows, the answer is block, requote,
-or split — **not** widen. A cap that yields under pressure is decoration.
-
-Likewise a hard ceiling stays hard: a caller-supplied tolerance is a *maximum*, not
-the selected value.
-
-## Authorization expires
-
-Prefer short TTLs. A permanent broad grant is a hot wallet with extra steps. When a
-grant lapses, the lane returns to reading — that is the system working, not a
-regression to route around.
-
-## Re-check at the boundary
-
-Validate the grant at **sign time and broadcast time**, not only when the plan was
-made. State can change between planning and execution: a stale check is not a
-check. Reject a guard that is missing, stale, wrong-chain, wrong-venue, or
-over-cap.

package/skills/oracle-hypercore-staking/SKILL.md

@@ -1,57 +0,0 @@
----
-name: oracle-hypercore-staking
-description: Stake, delegate, undelegate, and unstake HYPE on Hyperliquid HyperCore. Prepare-only, user wallet signs.
----
-
-# HyperCore HYPE staking
-
-Use when someone asks Oracle to stake HYPE, delegate to a validator, undelegate,
-or unstake back to spot on Hyperliquid.
-
-## The four moves, in order
-
-HyperCore keeps staking in two buckets. Know which one holds the HYPE before
-preparing anything.
-
-| Move | Action | From -> To | Timing |
-|---|---|---|---|
-| Stake | `cDeposit` | spot -> staking balance | instant |
-| Delegate | `tokenDelegate` isUndelegate=false | staking balance -> validator | 1 day validator lockup |
-| Undelegate | `tokenDelegate` isUndelegate=true | validator -> staking balance | instant after lockup |
-| Unstake | `cWithdraw` | staking balance -> spot | 7 day queue |
-
-Staking balance earns nothing until it is delegated. "Unstake" almost always
-means two steps: undelegate first, then withdraw.
-
-## Flow
-
-1. `desk.hl.staking.preflight(user)` - read delegated, undelegated, and pending
-   withdrawal balances plus the queue and lockup constants.
-2. `desk.hl.staking.validators()` - pick a validator. Reject jailed ones and
-   surface commission before recommending.
-3. Prepare exactly one move:
-   - `desk.hl.staking.prepareStake({ amountHype, maxHype })`
-   - `desk.hl.staking.prepareDelegate({ validator, amountHype, isUndelegate })`
-   - `desk.hl.staking.prepareUnstake({ amountHype })`
-4. Hand back the EIP-712 typed data. The user's wallet signs and submits.
-
-## Rules
-
-- Amounts are decimal HYPE strings at 8 decimals. `hypeToWei("1.5")` is
-  `150000000`. More than 8 decimals is rejected, not rounded.
-- `maxHype` is a hard cap checked before anything is built. No cap, no size
-  discipline on an agent path.
-- Never claim a stake happened. These functions return `broadcastReady: false`
-  and `requiresUserSignature: true`. There is no submit function in the module
-  on purpose.
-- Warn about the 7 day unstaking queue every time you prepare a `cWithdraw`.
-  The HYPE is illiquid for the whole queue.
-- Warn about the 1 day validator lockup before a delegate.
-- Check `undelegated` balance before preparing a withdraw. Withdrawing more than
-  the undelegated bucket fails on chain, and the failure costs the user a round
-  trip.
-
-## Verification
-
-`npm run e2e:hypercore-staking` hits live validator/delegator reads and asserts
-every prepare path stays unsigned with caps enforced.

package/skills/oracle-hyperliquid/SKILL.md

@@ -1,56 +0,0 @@
----
-name: oracle-hyperliquid
-description: Use for Hyperliquid perps and spot — funding, books, positions, liquidation distance via the public info API.
----
-
-# Hyperliquid
-
-Read through Oracle's data plane (`hl-info` provider, public `/info` endpoint). No
-key required for reads.
-
-## Ops worth knowing
-
-| Need | Op |
-|---|---|
-| all mids | `allMids` |
-| order book | `l2Book` |
-| perp metadata + live ctx | `metaAndAssetCtxs` |
-| spot metadata | `spotMeta` |
-| account state | `clearinghouse` / `userState` |
-| fills | `userFills` |
-| open orders | `openOrders` / `frontendOpenOrders` |
-| candles | `candleSnapshot` |
-
-`metaAndAssetCtxs` is the efficient one: it returns funding, open interest, mark and
-oracle price for every asset in a single call. Prefer it over per-asset loops.
-
-## The three numbers that matter
-
-**Liquidation distance.** In percent. Always state it for a leveraged position. A
-"20x position" is really "a 5% adverse move ends this."
-
-**Funding.** Annualize it. A position paying 40% annualized is losing steadily even
-when directionally right. Funding flips sign — check the current rate, not the
-average.
-
-**Depth at your size.** The mid is a fiction for anything but the smallest clip.
-Walk the `l2Book` to your notional and quote the real average fill.
-
-## Mark vs oracle price
-
-Liquidations reference the **oracle** price; PnL references the **mark**. They
-diverge during volatility, which is exactly when it matters. Say which one you used.
-
-## Spot and perps are different assets
-
-The same ticker exists in both with different liquidity and no automatic
-relationship. Never quote a perp book for a spot question.
-
-## Hard rules
-
-1. State liquidation distance for every leveraged position — not optional.
-2. Annualize funding, always.
-3. Quote fills from book depth, not the mid.
-4. Never size to "max leverage" without naming the wipeout move.
-5. You prepare; the user's wallet signs.
-6. Receipts or it didn't happen.

package/skills/oracle-meme-token-sniper/SKILL.md

@@ -1,73 +0,0 @@
----
-name: oracle-meme-token-sniper
-description: Scan and prepare guarded meme-token launch/sniping trades across configured chains; fail-closed, user-signed, sell-sim first.
----
-
-# Oracle meme-token sniper
-
-Use when a user asks Oracle to find, monitor, or prepare buys for meme tokens,
-new launches, liquidity adds, bonding curves, or "snipe" opportunities on any
-supported chain.
-
-## Scope
-
-Oracle may scan every configured venue/chain for meme-token launch signals:
-
-- EVM factory/pair/pool creation logs across configured chains.
-- Liquidity additions, first swaps, tax/owner-risk changes, holder distribution.
-- Solana SPL/token-launch feeds and Jupiter-route availability when configured.
-- Chain-specific launchpads/bonding curves only after the venue is verified.
-- Smart-wallet early-entry overlap and repeat deployer history.
-
-Unsupported chain/venue means `UNAVAILABLE`, not fake coverage. A chain with no
-verified executable route can still be analyzed, but cannot be prepared for buy.
-
-## Required gate before any prepared buy
-
-1. Resolve exact chain, token mint/contract, pool, quote asset, router/venue.
-2. Verify token identity from live chain data, not only a ticker/social link.
-3. Check deployer/owner controls, mint/freeze/blacklist/tax/proxy risks where
-   the chain exposes them.
-4. Confirm liquidity exists and is not only a fake/self pool.
-5. Run sellability / reverse-route simulation when the chain/venue supports it.
-6. Quote fresh, net of gas, and bind slippage/deadline to the prepared artifact.
-7. Enforce user caps: per-trade spend, chain, venue, token, max fee, and TTL.
-8. Return unsigned/user-signable transaction only. No model-authored calldata
-   bypass, no raw user calldata, no backend custody by default.
-
-## Autonomous mode
-
-Autonomous meme sniping is allowed only as a capped local-user signer loop:
-
-- separate burner/session key, never main wallet
-- explicit user opt-in and scope
-- max spend per token and per day
-- denylist/allowlist support
-- retry ceiling and kill switch
-- first-run paper/shadow mode
-- receipt/balance reconciliation after every fill
-
-Default public posture is advisory/prepare-only. "Snipe" in UI copy means fast
-scan + prepared ticket; it does not mean blind broadcast.
-
-## Output contract
-
-For every candidate, return:
-
-- `chain`, `token`, `pool`, `venue`
-- `signal`: launch/liquidity/smart-wallet/social/etc.
-- `risk`: PASS/WARN/BLOCK/UNKNOWN with evidence
-- `sellability`: PASS/FAIL/UNKNOWN/UNAVAILABLE
-- `route`: quote source and freshness
-- `prepared`: true only if a guarded unsigned artifact exists
-- `whyBlocked` when not prepared
-
-## Pitfalls
-
-- Treating ticker match as identity.
-- Buying before sell-sim/reverse-route proof.
-- Using scanner membership as an execution allowlist.
-- Calling a launchpool real when reserves are virtual/stale.
-- Ignoring gas: on small meme trades, gas can dominate edge.
-- Letting "every chain" become "every venue is executable". Coverage must be
-  capability-labeled per chain.