Ito trading

---

Market Intelligence

Itô Market Intelligence

Use this skill when a user wants prediction-market context, event discovery, venue comparison, basket theme exploration, or an Itô API-backed market brief.

This is a public teaser skill. It can work with public sources by default. Any Itô-backed data call requires explicit API access through ITO_API_KEY.

Guardrails

• Do not provide investment, legal, tax, or trading advice.
• Do not place, cancel, route, or simulate live orders.
• Do not infer the user's financial situation unless they provide it.
• Treat Polymarket, Kalshi, Itô, X, Exa, GitHub, and web data as source inputs, not as truth by themselves.
• Separate facts, market-implied signals, and your interpretation.

Workflow

1. Clarify the market theme, venue, geography, and time horizon.
2. Gather public market data from venue docs/APIs or source-grounded research.
3. If ITO_API_KEY is present and the user explicitly asks for Itô data, call only read endpoints and state that access is gated.
4. Normalize event, underlier, liquidity, fee, resolution, and data-latency differences across venues.
5. Produce a decision brief:
   • market/event summary
   • available venues and underliers
   • liquidity and data-quality caveats
   • relevant news/source context
   • open questions before any user action

Useful Skill Chains

• Use deep-research or exa-search for source discovery.
• Use x-api for public social signal discovery when X access is configured.
• Use market-research for market sizing, competitors, or business use cases.
• Use prediction-market-risk-review before any workflow touches user capital, portfolio data, or execution-capable credentials.

Output Contract

Default to a compact brief with source links and a clear caveat:

This is market intelligence, not investment or trading advice.

If access is missing, say:

Itô live basket/API data requires gated access. Request an ITO_API_KEY before
using Itô-backed reads.

---

Trade Planner

Itô Trade Planner

Use this skill when a user wants a structured worksheet for a prediction-market idea, basket adjustment, venue comparison, or manual execution plan.

The skill is intentionally non-executing. It produces checklists and parameter tables the user can review manually.

Guardrails

• Do not say a trade is good, bad, optimal, or recommended.
• Do not provide investment advice or position sizing advice.
• Do not place, cancel, route, or sign orders.
• Do not request private keys, seed phrases, exchange passwords, or wallet credentials.
• Require explicit user approval before any workflow moves from research to execution-capable tooling.

Planning Workflow

1. Restate the user's idea as a neutral hypothesis.
2. Identify markets, venues, underliers, resolution rules, fees, and data freshness constraints.
3. If ITO_API_KEY is configured and requested, read Itô basket metadata.
4. Build a manual worksheet:
   • market/underlier
   • venue
   • data source
   • current observable price or status
   • resolution rule
   • liquidity caveat
   • open questions
   • manual action link or next review step
5. Run prediction-market-risk-review before discussing automation, keys, venue auth, or capital constraints.

Allowed Language

Use:

• "manual planning worksheet"
• "questions to answer before acting"
• "observable venue data"
• "risk and constraint review"

Avoid:

• "you should buy/sell"
• "best trade"
• "guaranteed"
• "risk-free"
• "optimal size"

Output Contract

End every plan with:

This is a planning worksheet, not investment or trading advice. Review venue
rules and make any trading decisions yourself.

---

Basket Compare

Itô Basket Compare

Use this skill to compare a basket, theme, or market set against a user's knowledge base, portfolio notes, research memo, CRM context, or stated thesis.

This skill is read-only. It does not recommend trades. It helps a user inspect fit, exposure, assumptions, and missing context before they decide what to do.

Guardrails

• Do not provide investment advice or tell the user to buy, sell, hold, hedge, lever, or size a trade.
• Do not execute, prepare, or submit orders.
• Do not use private documents unless the user explicitly points to them.
• Use ITO_API_KEY only for read-only Itô basket/market data after explicit user request.
• If comparing against financials, preserve privacy and summarize only the fields needed for the comparison.

Comparison Modes

Basket vs Knowledge Base

1. Identify the basket theme and underliers.
2. Retrieve the user's relevant notes, docs, or memory snippets.
3. Map each underlier to claims, sources, uncertainties, and stale assumptions.
4. Return aligned signals, conflicting signals, and missing research.

Basket vs Portfolio Notes

1. Parse the user's watchlist, holdings summary, or exposure notes.
2. Compare themes, geographies, time horizons, and event outcomes.
3. Flag concentration, correlation, and duplicated narrative exposure.
4. Avoid recommendations; phrase output as inspection and questions.

Basket vs Financial Context

1. Accept only user-provided or explicitly selected financial context.
2. Identify liquidity, drawdown, time-horizon, and constraint mismatches.
3. Ask for missing constraints instead of guessing.

Output Contract

Use this structure:

1. Basket summary
2. Comparison target
3. Matches
4. Conflicts or stale assumptions
5. Missing context
6. User-action checklist

End with:

This comparison is informational and not investment or trading advice.

---

Data Atlas Agent

Itô Data Atlas Agent

Use this skill to design an agent that watches data sources, builds candidate prediction-market baskets, drafts parameter changes, and hands the result to a human for review.

This skill describes architecture and workflow. It does not run live trading.

Guardrails

• Keep all execution behind explicit human approval.
• Require ITO_API_KEY only for read-only Itô data access unless a separate private implementation explicitly adds execution controls.
• Do not persist private user data unless the target repo already has a storage contract and the user asks for it.
• Do not expose private strategy logic, venue credentials, or local paths in public docs.

Architecture Pattern

Use four lanes:

1. Research collector: public web, X, GitHub, venue docs, API metadata, and Itô read endpoints when gated access exists.
2. Basket drafter: turns sources into candidate underliers, weights, rules, and questions.
3. Risk reviewer: checks data freshness, venue limits, resolution ambiguity, compliance notes, and prompt-injection exposure.
4. Human editor: opens a chat or UI state where the user can approve, reject, adjust, or ask for more research.

Workflow

1. Define the user objective and excluded actions.
2. List data sources and access requirements.
3. Draft a basket spec with provenance for every underlier.
4. Produce editable parameters rather than executable orders.
5. Store an audit trail: inputs, model output, sources, and human decision.

Useful Skill Chains

• deep-research for source collection.
• x-api for current social/event signal.
• ito-market-intelligence for venue and underlier context.
• ito-basket-compare for user knowledge-base matching.
• prediction-market-risk-review before any execution-capable integration.

Output Contract

Return an implementation-ready workflow spec with:

• data sources
• access gates
• agent roles
• human approval points
• storage/audit boundary
• non-goals