Ito data atlas agent
Design background Data Atlas style agents for Itô basket research, market discovery, parameter drafting, and human-in-the-loop editing. Use for architecture and workflow planning, not live order execution.From its SKILL.md
npx -y skills add S3YED/appie-kit --skill ito-data-atlas-agentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 12 stars12 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
2.2 KB, 425 tokens by cl100k_base, as published. Nobody here has run it
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_KEYonly 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:
- Research collector: public web, X, GitHub, venue docs, API metadata, and Itô read endpoints when gated access exists.
- Basket drafter: turns sources into candidate underliers, weights, rules, and questions.
- Risk reviewer: checks data freshness, venue limits, resolution ambiguity, compliance notes, and prompt-injection exposure.
- Human editor: opens a chat or UI state where the user can approve, reject, adjust, or ask for more research.
Workflow
- Define the user objective and excluded actions.
- List data sources and access requirements.
- Draft a basket spec with provenance for every underlier.
- Produce editable parameters rather than executable orders.
- Store an audit trail: inputs, model output, sources, and human decision.
Useful Skill Chains
deep-researchfor source collection.x-apifor current social/event signal.ito-market-intelligencefor venue and underlier context.ito-basket-comparefor user knowledge-base matching.prediction-market-risk-reviewbefore 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
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most context ai engineering skills give in 425 tokens
Counted across 1,328 of the 2,349 authors here whose files we hold, read 2026-09-06
- Dispatch a fresh subagent for each taskin 76 of 1328, across 59 files
- Perform spec compliance review before code quality reviewin 44 of 1328, across 34 files
- Dispatch a final code reviewer after all tasksin 38 of 1328, across 26 files
- Answer subagent questions before allowing implementationin 36 of 1328, across 26 files
- Use the least powerful model capable of the taskin 33 of 1328, across 26 files
- Create a TodoWrite list for all tasksin 32 of 1328, across 22 files
- Perform a task review after each implementationin 31 of 1328, across 24 files
- Extract all tasks and context from the planin 29 of 1328, across 20 files
- Provide full task text to subagentsin 28 of 1328, across 20 files
- Use git worktrees for isolated workspacesin 25 of 1328, across 20 files
- Specify the model explicitly when dispatching a subagentin 23 of 1328, across 18 files
- Execute all tasks from the plan without stoppingin 21 of 1328, across 16 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.