Agents & OrchestrationSûr100100/100
Ito Trade Planner
Build a non-advisory prediction-market trade planning worksheet for Itô or venue workflows. Use to inspect venues, underliers, constraints, order prerequisites, and manual execution steps without placing trades or recommending positions.
ou envoie-le directement à ton agent.
Installer dans ton projet
$ npx arboris-cli@latest install ito-trade-planneraffaan-m
affaan-m/ECC
Contenu à copier
--- name: ito-trade-planner description: Build a non-advisory prediction-market trade planning worksheet for Itô or venue workflows. Use to inspect venues, underliers, constraints, order prerequisites, and manual execution steps without placing trades or recommending positions. metadata: origin: ECC --- # 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: ```text This is a planning worksheet, not investment or trading advice. Review venue rules and make any trading decisions yourself. ```
Colle ce Markdown dans ton agent ou utilise les boutons ci-dessus pour l’écrire dans ton projet.
Ce que fait Ito Trade Planner
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
Comment utiliser Ito Trade Planner
1
Copie le prompt
Un clic copie le prompt packagé (ou l'envoie à ton agent).
2
L'agent installe le skill
Il ajoute le SKILL.md et ses ressources à ton projet.
3
Activation automatique
Le skill s'active dès que le contexte correspond.
Déclencheurs pour Ito Trade Planner
Dis simplement à ton agent quelque chose comme :
Applique le skill ito-trade-planner à cette tâche
Utilise ito-trade-planner pour améliorer cette implémentation
Passe en revue ce sujet avec ito-trade-planner
Skills liés à Ito Trade Planner
Acceleration (Microsoft)
Compare synthetic acceleration options and clearly separate scenario value from forecast commitments.Account Overview (Microsoft)
Create a synthetic Acme account overview and identify evidence that merits seller attention.Acroform Writer (Microsoft)
Use this skill whenever the user wants values written INTO an existing PDF form that lives in the connected SharePoint knowledge source — filling out, completing, populating, or submitting a fillable PDF (application, intake sheet, contract, government form) from data they supply, a spreadsheet row, or the conversation. Triggers include "fill out the job application form", "complete the intake form for [person]", "populate our standard NDA template", and "make this ready to send / non-editable" (flatten). The source form should be found via knowledge search; only ask the user to upload it if knowledge search turns up nothing plausible. different task), and do NOT use it on scanned/image-only PDFs that have no real fillable fields — those need OCR or manual overlay instead, which this skill explicitly detects and reports rather than silently failing.