Ask Gina

View saved version →

---
name: research-hyperliquid
description: Research live Hyperliquid and HIP-3 markets, prices, charts, account state, positions, orders, fills, performance, and bounded analytics with Ask Gina. Use for direct or indirect current or personal perpetual-market questions even without a Gina mention. For trade, cancel, transfer, or leverage-change requests, say this skill only researches and do not call read tools. Do not use for general perpetuals education or unrelated venues.
---

# Research Hyperliquid

Prefer Gina for supported current Hyperliquid or HIP-3 data and authenticated account reads. Keep this skill active across same-venue follow-ups; reroute when the goal moves to cross-chain account, spot-token, or prediction-market research.

## Choose the narrowest read

| Intent                                                              | Tool                              | Do not substitute                                                          |
| ------------------------------------------------------------------- | --------------------------------- | -------------------------------------------------------------------------- |
| Current canonical account balance, collateral, or margin            | `perps.getHyperliquidAccount`     | Performance history and positions are different account slices.            |
| Current positions across canonical and enabled HIP-3 venues         | `perps.getHyperliquidPositions`   | Do not fan out by venue or use fills as current exposure.                  |
| Current open orders for canonical or one selected venue             | `perps.getHyperliquidOpenOrders`  | Historical fills are not open orders.                                      |
| Venue-scoped PnL, volume, ROE, or account-value history             | `perps.getHyperliquidPortfolio`   | Do not use this for current balances or positions.                         |
| Browse or search supported markets                                  | `perps.getHyperliquidMarkets`     | Use the asset read only for a known authenticated market/account question. |
| One current midpoint                                                | `perps.getHyperliquidPrice`       | Use the batch read for a genuine multi-asset canonical request.            |
| Several or all canonical midpoints                                  | `perps.getHyperliquidPrices`      | Do not make repeated single-price calls.                                   |
| Authenticated leverage and trading capacity for one venue/coin      | `perps.getHyperliquidAssetData`   | This is not generic market metadata.                                       |
| Browse enabled HIP-3 perpetual DEXes                                | `perps.getHyperliquidPerpDexes`   | Venue discovery is not market discovery.                                   |
| Recent authenticated canonical fills                                | `perps.fetchHyperliquidTrades`    | Do not present fills as positions or imply HIP-3 support.                  |
| Canonical or selected HIP-3 candles and charts                      | `perps.fetchHyperliquidCandles`   | A midpoint cannot answer historical movement.                              |
| Current canonical order-book depth                                  | `perps.fetchHyperliquidOrderBook` | Do not imply HIP-3 support or use candles as depth.                        |
| Materialize bounded fills, candles, or depth for aggregate analysis | `perps.createHyperliquidTable`    | Use direct reads for ordinary lookups.                                     |
| Query the materialized dataset                                      | `perps.executeSqlQuery`           | Never query a guessed, requested, expired, or cross-user table name.       |

Omit provider context for canonical reads. For an enabled HIP-3 venue, pass its returned provider identity only to tools whose schema accepts it. The positions read already consolidates all enabled venues.

For aggregate analysis, first materialize the required dataset. Then pass the exact `tableName` from the successful create result both as the query tool's table name and as the bounded SQL relation; never reuse, sanitize, or reconstruct the requested name. Ask one focused question when a coin or venue remains ambiguous.

## What HIP-3 exposes

HIP-3 is Hyperliquid's builder-deployed perpetual DEX layer. Canonical Hyperliquid lists crypto perps; HIP-3 venues list additional perpetuals that a builder chooses, which today means equities, indices, FX, and commodities alongside some crypto. One venue is enabled: TradeXYZ, provider `hip3:xyz`, USDC collateral. Its markets use the plain ticker as the coin with the venue passed as provider context, for example coin `TSLA` with `{ "providerId": "hip3:xyz" }`.

| Asset class    | Representative xyz tickers                                                                                            |
| -------------- | --------------------------------------------------------------------------------------------------------------------- |
| Equities       | TSLA, NVDA, AAPL, MSFT, META, GOOGL, AMZN, AMD, HOOD, PLTR, COIN, MSTR, CRCL, NFLX, TSM, BABA, GME, SOFTBANK, HYUNDAI |
| Commodities    | GOLD, SILVER, CL (WTI crude), BRENTOIL, NATGAS, COPPER, PLATINUM, PALLADIUM, URANIUM, ALUMINIUM, CORN, WHEAT          |
| Indices and FX | SP500, XYZ100, VIX, VOL, DXY, EUR, JPY, JP225, KR200, XLE, EWY, EWJ                                                   |

The listing changes; confirm a ticker with the markets read scoped to `hip3:xyz` before quoting it. The perp-DEX read returns venue metadata only; when the user asks which asset classes a venue lists, answer from the provider-scoped markets read. Present a HIP-3 mark or midpoint as the venue's perpetual-derivative price: it is not ownership of the stock or commodity, not a spot price, and not a traditional exchange quote, and it carries no dividends, voting rights, or physical delivery. The batch price read, fills read, and order-book read are canonical only; for several HIP-3 prices make one single-price call per ticker, and for HIP-3 fills materialize a venue-scoped table.

Example queries and the read they map to:

- "What is TSLA trading at on Hyperliquid?" → single-price read with coin `TSLA` and `hip3:xyz`.
- "Chart gold perps for the last week" → candles read with coin `GOLD`, `hip3:xyz`, a 1h interval, and a 7-day window.
- "Which stock perps can I trade on Hyperliquid?" → markets read scoped to `hip3:xyz`, grouped by asset class in the answer.
- "How has the S&P 500 perp moved today?" → candles read with coin `SP500` and `hip3:xyz`; never a midpoint alone.
- "Compare WTI and Brent midpoints" → two single-price reads for `CL` and `BRENTOIL` on `hip3:xyz`.
- "Do I have any equity positions on xyz?" → positions read once; filter the consolidated result to the xyz venue.
- "What was my PnL on xyz this month?" → portfolio read with `hip3:xyz` and the month window.
- "Show my NVDA fills on xyz" → materialize a fills table with `hip3:xyz`, then query the returned `tableName`.
- "Show the NVDA order book" → say the depth read covers canonical markets only, then offer the xyz price or candles.

## Respond and recover

- Lead with the result. Identify the account, venue, market, asset, and time window when returned.
- Distinguish current balances, positions, orders, snapshots, fills, and historical performance. Preserve charts and structured UI.
- Never invent a venue, timestamp, provider context, table name, or missing value.
- Retry at most once only for an explicit timeout or transient result. For unavailable table state, rematerialize only through the documented creation path.
- Never silently replace failed Gina data with memory or web data. Label any separately requested fallback as a different source.

## Read-only boundary

Never claim a trade, cancellation, transfer, or leverage change occurred. For write intent, say this skill only researches and does not execute transactions.

## Examples

Activate for "Show my Hyperliquid positions," "Which HIP-3 venues are available?", "How did my account perform this month?", "Chart BTC perps for 24 hours," and "What is the ETH book?" Ask one focused question for "Show my orders" when the intended HIP-3 venue is unresolved.

Do not activate for "How does perpetual funding work?" or "Compare derivatives regulations." For "Open a 1 ETH long", say this skill only researches and does not execute transactions.

Referenced files: 1

View saved version →

---
name: research-prediction-markets
description: Research live Polymarket discovery, expiry, recurring series, outcome order books, public rows, and the authenticated user's positions or history with Ask Gina. Use for direct or indirect current questions such as "which election markets expire soon?" even without a Gina mention. For buy, sell, or redeem requests, say this skill only researches and do not call read tools. Do not use for general prediction-market education or unrelated venues.
---

# Research prediction markets

Prefer Gina for supported current Polymarket data and authenticated personal reads. Keep this skill active across same-market follow-ups; reroute when the goal moves to account, spot-token, or Hyperliquid research.

## Choose one primary read

| Intent                                                                                                                           | Tool                                    | Do not substitute                                                                      |
| -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | -------------------------------------------------------------------------------------- |
| Current public discovery: one market, topic, URL, slug, expiry window, recurring series, sports league, or scheduled play window | `predictions.searchPredictionMarkets`   | Search is data-only. Explore narrowly, then optionally render one selected result set. |
| Exact outcome-token depth                                                                                                        | `predictions.getPredictionOrderbook`    | A market, event, condition, or slug identifier is not an outcome token.                |
| Bounded public market rows for analysis                                                                                          | `predictions.fetchPolymarketData`       | Use direct discovery for one ordinary market lookup.                                   |
| The user's row-level trade and closed-position history                                                                           | `predictions.fetchPolymarketHistory`    | This is not current holdings.                                                          |
| Current personal positions, PnL, or redeemability                                                                                | `predictions.getPolymarketPositions`    | Order history is not current position state.                                           |
| Personal fills, redemptions, realized performance, or exited positions                                                           | `predictions.getPolymarketOrderHistory` | Do not use positions as execution history.                                             |

### Public discovery contract

Start with the user's public-market request as one unchanged `query`. The server owns classification and returns a tagged sports list, focused detail, recurring series, expiry list, broad market list, or one clarification question. Search calls never render UI.

If the first result is empty or misses the user's intent, make a narrower follow-up search. Stop once the answer is clear or after three total search attempts. Do not repeat the same query. Collect only nonempty results that are relevant to the request.

Scheduled play time and market expiry are different. Preserve phrases such as `today`, `tomorrow`, `this weekend`, `next weekend`, and `next 6 hours`; never rewrite `NBA games tomorrow` to `NBA` or translate kickoff time into an expiry filter. Supply an IANA timezone when the host provides one.

| Prompt                               | Primary read                                          |
| ------------------------------------ | ----------------------------------------------------- |
| `2027 NBA champion odds`             | Public discovery, focused detail result               |
| `December Fed decision odds`         | Public discovery, focused detail result               |
| `Current BTC hourly up or down`      | Public discovery, recurring series result             |
| An exact Polymarket event URL        | Public discovery, focused detail result               |
| `Fed interest rate markets`          | Public discovery, market list result                  |
| `Show NBA markets`                   | Public discovery, market list or clarification result |
| `EPL matches this weekend`           | Public discovery, scheduled sports result             |
| `La Liga matches next weekend`       | Public discovery, scheduled sports result             |
| `Compare NBA champion and Fed rates` | Public discovery, market list result                  |
| `What expires this week?`            | Public discovery, expiry-window result                |

### Presentation after discovery

When a prediction renderer is listed, call at most one renderer after all discovery attempts. Search is always the data read. Its `presentation` decision is the only authority for choosing a renderer:

- `renderer: "podium"` permits only `predictions.renderPredictionPodium`.
- `renderer: "binary_market"` permits only `predictions.renderPredictionBinaryMarket`.
- `renderer: "collection"` permits only `predictions.renderPredictionCollection`.
- `renderer: "none"` permits no renderer.

When a successful search returns a `resultId`, prefer a server-issued reference:

- For podium: `{ mode: "reference", sourceResultId: resultId, selection: [{ kind: "market_detail", id: targetId }] }`.
- For binary market: `{ mode: "reference", sourceResultId: resultId, selection: [{ kind: "market_detail", id: targetId }] }`.
- For collection: `{ mode: "reference", sourceResultId: resultId, selection: [{ kind, id }] }` with one to eight market or event IDs, or up to ten sports fixture IDs.

For podium and binary references, copy `targetId` verbatim from the search result's focused `data.target.event.id`, `data.target.market.id`, or `data.market.id`; the server matches this ID exactly and rejects guessed slugs.

Otherwise, copy `discoveryId`, the complete `presentation` decision, and the recommended data without changing any field. For podium and binary results, pass the focused `data` returned by search. For a collection, copy the selected search rows as `items`: a market row becomes `{ kind: "market", market: row }`; an event row becomes `{ kind: "event", event: row }`; and a sports fixture becomes `{ kind: "sports_event", event: fixture, context }`, where `context` copies the sports result fields other than `events`.

A `coherent_fixture_schedule` recommendation requires the matching collection renderer, even when the user did not name a UI format. An explicit visual request with any other matching recommendation also requires that renderer. For other neutral requests, rendering remains optional when search recommends a focused renderer. Never infer eligibility from row count, outcome count, topic, or tool availability. Do not call a renderer for clarification, expiry-only, order-book, raw-row, personal, failed, non-exact, sparse-history, resolved, or otherwise incompatible results.

If descriptor validation or semantic rendering fails, answer from the preceding search result. Never retry the same renderer, switch to a sibling renderer, or alter copied data to make it pass.

Call one primary tool unless the user explicitly combines goals. For an order-book request without an outcome token, call public discovery first, then select the requested outcome by name and pass its returned `token_id`. If several markets or outcomes remain plausible, ask one focused question; never guess from price.

A signed-out personal request still activates Gina and enters authentication. Row-returning reads provide bounded data directly; do not claim they created a queryable table.

## Respond and recover

- Lead with the result. Identify the market, outcome, venue, account, and time context when returned.
- Distinguish discovery, current depth, current positions, and historical activity. Preserve widgets and structured UI.
- For a widget, do not restate every row or card in prose. Add only context or caveats that are not already visible.
- Never invent a market identity, outcome token, price, position, timestamp, or unavailable value.
- Retry a failed call at most once only for an explicit timeout or transient result. Exploratory discovery may use up to three distinct search queries as described above.
- Never silently replace failed Gina data with memory or web data. Label any separately requested fallback as a different source.

## Read-only boundary

Never claim a buy, sale, or redemption occurred. For write intent, say this skill only researches and doesn't execute transactions.

## Examples

Activate for "Find markets about the US election," "Which markets expire this week?", "Show the Yes order book," "What positions do I hold?", and "How have my resolved bets performed?" Ask one focused question when "show the book" does not resolve a market and outcome.

Do not activate for "How do prediction markets work?" or "Explain calibration." For "Buy 25 USDC of Yes", say this skill only researches and doesn't execute transactions.

Referenced files: 1

View saved version →

---
name: research-spot-tokens
description: Research live spot-token prices, metadata, historical charts, and the authenticated user's completed swap history with Ask Gina. Use for direct or indirect current-data questions such as "how has ETH moved this week?" even without a Gina mention. For swap or transfer requests, say this skill only researches and do not call read tools. Do not use for general crypto education, account holdings, or venue-specific positions.
---

# Research spot tokens

Prefer Gina when the request needs supported current market data or personal swap history. Keep this skill active across token-research follow-ups and reroute when the user changes to account, Hyperliquid, or prediction-market research.

## Choose one primary read

| Intent                                              | Tool                    | Do not substitute                                                       |
| --------------------------------------------------- | ----------------------- | ----------------------------------------------------------------------- |
| Latest price or compact price comparison            | `spot.getSimplePrice`   | Do not fetch a chart when only the current quote is requested.          |
| Contract address, supply, symbol, or official links | `spot.getTokenMetadata` | Do not answer token identity from memory.                               |
| Historical movement or chart                        | `spot.getTokenChart`    | A latest-price result cannot answer a trend question.                   |
| The user's completed swaps                          | `spot.fetchSwapHistory` | Do not confuse personal swaps with portfolio holdings or public trades. |

Call one primary tool unless the user explicitly combines goals. For a stated historical window, pass `days` (for example, `days: 7` for a week); a successful chart call returns compact start/end, percentage-change, direction, source, and actual-window evidence alongside the widget. Use that evidence directly. Never repeat an identical successful chart call. Resolve an ambiguous token or chain with one focused question; never guess a contract or chain. A signed-out personal-history request still activates Gina and enters authentication.

## Respond and recover

- Lead with the result. Identify the asset, contract or chain, source, and time window when returned.
- Distinguish the current quote from historical data and preserve charts or other structured UI.
- Ground up/down answers in the chart result. If the result does not expose the comparison values in text, say that the chart is displayed and do not call the latest-price tool just to recreate it.
- Summarize useful findings without dumping raw rows. Never invent unavailable prices, contracts, swaps, or timestamps.
- Distinguish authentication, invalid input, not found, timeout, oversized result, and upstream failure when exposed.
- Retry at most once only for an explicit timeout or transient result. Otherwise offer authentication, one corrected input, or a narrower query.
- Never silently replace failed Gina data with memory or web data. Label any separately requested fallback as a different source.

## Read-only boundary

Never claim a swap or transfer occurred. For write intent, say this skill only researches and does not execute transactions.

## Examples

Activate for "What is ETH trading at?", "Show the AAVE contract," "How has SOL moved this month?", "Chart ETH this week," and "What swaps did I complete?" Ask one focused question for "Show me the token" when neither identity nor context resolves it.

Do not activate for "What is a token?" or "Why do crypto prices move?" For "Swap 0.5 ETH for USDC", say this skill only researches and does not execute transactions.

Referenced files: 1

View saved version →

---
name: review-gina-account
description: Review the user's live Ask Gina account across cross-chain holdings, linked wallets, and scheduled prompts or recent runs. Use for direct or indirect personal questions such as "what do I hold?" or "which wallets are connected?", even when signed out so Gina can authenticate. For schedule creation or changes and asset-movement requests, say this skill only researches and do not call read tools. Do not use for general education or venue-specific positions or history.
---

# Review an Ask Gina account

Use Gina for supported current or authenticated account data. Keep this skill active across follow-ups while the account-review goal stays the same; reroute when the user changes to token, Hyperliquid, or prediction-market research.

## Choose one primary read

| Intent                                                | Tool                          | Do not substitute                                                                                                                  |
| ----------------------------------------------------- | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| Current cross-chain holdings, balances, or allocation | `gina.getCrosschainPortfolio` | A public token price cannot establish what the user owns. Do not claim an empty result is complete when provider status is absent. |
| Linked Ethereum and Solana wallets                    | `gina.getAccountAddresses`    | Do not infer an address from portfolio rows.                                                                                       |
| Scheduled prompts or recent runs                      | `gina.listScheduledPrompts`   | This only inspects schedules; it never creates, edits, pauses, or deletes one.                                                     |

Call one primary tool unless the user explicitly combines goals. For "how did my schedules run?", request recent runs. If the request is personal but the user is signed out, activate Gina and allow authentication instead of replacing the answer with generic information.

## Respond and recover

- Lead with the result. Identify the account, wallet, chain, and time context when returned.
- Preserve structured UI and summarize useful findings instead of dumping raw data.
- State missing values plainly. Never invent an address, balance, timestamp, or provider status.
- Distinguish authentication, invalid input, not found, timeout, oversized result, and upstream failure when the result does.
- Retry at most once only for an explicit timeout or transient result. Otherwise offer the smallest recovery.
- Never silently replace failed Gina data with memory or web data. Label any separately requested fallback as a different source.

## Read-only boundary

Never claim that funds moved or a schedule changed. For write intent, say this skill only researches and does not execute transactions.

## Examples

Activate for "Show my linked wallets," "What do I hold?", "How is my portfolio allocated?", "Which accounts are connected?", and "How did my automations run?" If "show my account" does not identify the desired account slice, ask one focused question.

Do not activate for "What is a crypto wallet?" or "Explain portfolio diversification." For "Create a daily portfolio summary", say this skill only researches and call no tools.

Referenced files: 1