agentsclimarketplace
Sign in

Ito trade planner

Skill S3YED/appie-kit/skills/ecc/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.From its SKILL.md

Install
npx -y skills add S3YED/appie-kit --skill ito-trade-planner

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 379 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most plan spec skills give in 379 tokens

Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06

  • Ask one question at a timein 73 of 1360
  • Write the spec using the templatein 22 of 1360
  • Ask clarifying questions if neededin 19 of 1360, across 18 files
  • Wait for user confirmation before proceedingin 19 of 1360
  • Save plans to the plans directoryin 17 of 1360, across 13 files
  • Check for product marketing context firstin 16 of 1360, across 5 files
  • Read the plan file completelyin 16 of 1360
  • Order tasks by dependencyin 16 of 1360
  • Gather context from the conversationin 15 of 1360, across 9 files
  • Explore the codebase instead of askingin 15 of 1360, across 13 files
  • Wait for explicit user approvalin 14 of 1360, across 13 files
  • Quiz the user on the breakdownin 13 of 1360, across 7 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.