Update to Option Desk (hosted)

{
  "description": "Validate, normalize, import, or delete an option-chain snapshot that the user is permitted to send. Use when a user attaches CSV or JSON data, asks how to format it, wants errors repaired, wants a private dashboard, or asks to delete that dashboard.",
  "included_files": [],
  "name": "option-data-import",
  "skill_md_contents": "---\nname: option-data-import\ndescription: \"Validate, normalize, import, or delete an option-chain snapshot that the user is permitted to send. Use when a user attaches CSV or JSON data, asks how to format it, wants errors repaired, wants a private dashboard, or asks to delete that dashboard.\"\n---\n\n# Option data import\n\nUse the hosted Option Desk MCP. Do not run a local command.\n\n## Safety boundary\n\n- Never fetch market data.\n- Never ask for credentials, API keys, account numbers, positions, or names.\n- Do not process an upload until the user confirms that they may send it.\n- A user confirmation does not override the source provider's terms.\n- The hosted service blocks Yahoo, yfinance, and personal Alpha Vantage data.\n- Never invent a strike, quote, volatility, open-interest value, expiry, source, or rights statement.\n\n## Workflow\n\n1. If the format is unclear, call `option_snapshot_schema`.\n2. Ask for the data source and rights confirmation if either is missing.\n3. Call `option_validate_snapshot` before analysis.\n4. Report each validation problem and the permitted repair. Ask for corrected data when a required value is missing.\n5. Call `option_import_snapshot` only after the user also accepts storage for up to one hour.\n6. Tell the user that the private dashboard URL is a bearer secret.\n7. Use `option_delete_snapshot` when the user asks for early deletion.\n\nFor analysis that does not need a dashboard, use a plot or strategy tool. Those tools remove their temporary files before they respond.\n\n## What a zero in a quote column means\n\nDo not treat a zero bid and zero ask as an executable price of zero.\nRead the validation result for the accepted price, volatility and repairs.\nA row can also carry an explicit mid or user-supplied volatility.\nDo not infer that the service skipped it from the bid and ask alone.\n\nA zero bid with a positive ask differs from two zero quotes.\nReport how the service handled the row without substituting your own price.\n\nBefore reporting analysis, read its degraded reason and skip counts.\nState which figures are unavailable and which remain supported by accepted inputs.\nDo not infer market hours or provider staleness from zero quotes alone.\n"
}