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

65 lines
2.1 KiB
Markdown

---
name: ito-basket-compare
description: Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.
metadata:
origin: ECC
---
# Itô Basket Compare
Use this skill to compare a basket, theme, or market set against a user's
knowledge base, portfolio notes, research memo, CRM context, or stated thesis.
This skill is read-only. It does not recommend trades. It helps a user inspect
fit, exposure, assumptions, and missing context before they decide what to do.
## Guardrails
- Do not provide investment advice or tell the user to buy, sell, hold, hedge,
lever, or size a trade.
- Do not execute, prepare, or submit orders.
- Do not use private documents unless the user explicitly points to them.
- Use `ITO_API_KEY` only for read-only Itô basket/market data after explicit
user request.
- If comparing against financials, preserve privacy and summarize only the
fields needed for the comparison.
## Comparison Modes
### Basket vs Knowledge Base
1. Identify the basket theme and underliers.
2. Retrieve the user's relevant notes, docs, or memory snippets.
3. Map each underlier to claims, sources, uncertainties, and stale assumptions.
4. Return aligned signals, conflicting signals, and missing research.
### Basket vs Portfolio Notes
1. Parse the user's watchlist, holdings summary, or exposure notes.
2. Compare themes, geographies, time horizons, and event outcomes.
3. Flag concentration, correlation, and duplicated narrative exposure.
4. Avoid recommendations; phrase output as inspection and questions.
### Basket vs Financial Context
1. Accept only user-provided or explicitly selected financial context.
2. Identify liquidity, drawdown, time-horizon, and constraint mismatches.
3. Ask for missing constraints instead of guessing.
## Output Contract
Use this structure:
1. Basket summary
2. Comparison target
3. Matches
4. Conflicts or stale assumptions
5. Missing context
6. User-action checklist
End with:
```text
This comparison is informational and not investment or trading advice.
```