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.
- License 许可
- MIT
- 最近更新
- 2026-07-30
- Stars
- ★ 2
- Forks
- 1
01 前言 Front Matter
- name
- ito-data-atlas-agent
- metadata
- { "origin": "HCP" }
- description
- 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.
03 SKILL.md 正文
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
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-智械工程
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code