elias/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-06-16 16:36:53 +08:00
Code Issues Packages Projects Releases Wiki Activity
everything-claude-code/skills/ito-trade-planner/SKILL.md
BERORINPO db7f2a6fd5 fix(skills): move top-level origin frontmatter key under metadata 
The official Agent Skills spec (agentskills.io/specification) whitelists exactly
6 top-level frontmatter keys (name/description/license/compatibility/metadata/
allowed-tools). A top-level `origin` key fails the official validator
(anthropics/skills quick_validate.py ALLOWED_PROPERTIES; skills-ref validate).

This moves `origin: X` -> `metadata.origin: X` across the canonical skills/
tree, preserving each value verbatim. Frontmatter-only, minimal diff.

- 251 SKILL.md updated (242 new metadata block, 9 appended to existing metadata)
- origin values preserved verbatim (verified 251/251)
- YAML validated on all changed files
- scoped to canonical skills/ only (docs/<lang> translations + tool mirrors
  .cursor/.kiro/.agents left untouched; presumably regenerated from canonical)

Addresses #2233
2026-06-11 21:12:21 +09:00

1.9 KiB
Raw Blame History

name, description, metadata
name description metadata
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.
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:

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