Update to OloLand DD

{
  "description": "Use when the user asks to run the OloLand ololand-dd-dd-merger-rerun-math workflow. Re-run one or all four merger engines on an existing merger-analysis deal with optional input overrides. Useful for sensitivity analysis (e.g., halved synergies).",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 447
    }
  ],
  "name": "ololand-dd-dd-merger-rerun-math",
  "skill_md_contents": "---\nname: ololand-dd-dd-merger-rerun-math\ndescription: Use when the user asks to run the OloLand ololand-dd-dd-merger-rerun-math\n  workflow. Re-run one or all four merger engines on an existing merger-analysis deal\n  with optional input overrides. Useful for sensitivity analysis (e.g., halved synergies).\n---\n\n\n# Workflow for ololand-dd-dd-merger-rerun-math\n\nFollow the OloLand command instructions below when the user asks for `ololand-dd-dd-merger-rerun-math` or the equivalent workflow.\n\n# ololand-dd-dd-merger-rerun-math\n\nRe-run a deterministic merger engine on a third-party merger-analysis deal. Each engine returns `INSUFFICIENT_DATA` when required inputs are missing — never silently impute.\n\n## Required inputs\n\n- **deal_id** — the merger-analysis deal ID (starts with `merger_`). Ask if missing.\n\nOptional:\n- **engine** — one of `premium`, `accretion`, `dcf`, `hhi`. When omitted, run all four.\n- **overrides** — JSON object of per-input pins. See \"Engine-specific overrides\" below.\n\n## Action\n\nPick the matching MCP tool(s):\n\n- `premium` → `run_premium_analysis(deal_id, overrides=...)`\n- `accretion` → `run_accretion_dilution(deal_id, overrides=...)`\n- `dcf` → `run_combined_dcf(deal_id, synergies=..., integration_costs=..., wacc=..., terminal_growth=...)`\n- `hhi` → `run_antitrust_hhi(deal_id, market_definition=..., rivals=..., target_share_pct=..., acquirer_share_pct=...)`\n\nFor each run, report:\n- `run_id` (for replay / lineage)\n- `status` (`completed` / `insufficient_data` / `error`)\n- Key outputs (numeric headlines)\n- Any `assumptions` payload (with confidence labels)\n\nIf `status == \"insufficient_data\"`, name the missing fields and where they typically come from. Suggest uploads or `ololand-dd-dd-merger-readiness` to confirm coverage.\n\n## Engine-specific overrides\n\n- **premium**: `target_unaffected_price`, `offer_price_per_share`, `target_52wk_high`, `target_30d_vwap`, `sector`, `size_class`.\n- **accretion**: `acquirer_eps_forward`, `target_eps_forward`, `acquirer_shares_million`, `target_shares_million`, `after_tax_synergy_runrate_million`, `synergy_phasing_pct`, `tax_rate`.\n- **dcf**: `synergies` (`{revenue_runrate, cost_runrate, phasing_pct}`), `integration_costs` (`{one_time_million}`), `wacc`, `terminal_growth`. Synergies MUST be attested as incremental to standalone forecasts per the merger-mechanics skill.\n- **hhi**: `market_definition` (`{industry, geography, product_segment}`) MUST be stated explicitly. `rivals` is `[{name, share_pct}, ...]`.\n\n## Subscription\n\nThe four engine tools run on Developer as part of the bounded single-deal trial, metered against the monthly credit budget — no longer Pro-gated. If a call returns `tier_gated: true`, surface the upgrade CTA from the response.\n\n\n## OpenAI execution requirements\n\nUse the connected MCP server's current tool schemas. Do not invent tool arguments, job-status endpoints, inputs, or outputs. If a referenced tool is unavailable, explain the limitation and request the needed connection or data. Invoke writes only when the user has requested the corresponding action. Do not initiate purchases or payments. An unrun, unsupported, or unavailable procedure is a gap, never a passing result.\n\n\nOpenAI cannot execute local lifecycle hooks. Use the packaged explicit setup/review workflow when requested. Server-side MCP auditing remains authoritative; preserve evidence blockers and human-only approval gates.\n\nClaim-correction submission is unsupported in this OpenAI upload because the current handler records surface=cowork. Do not invoke submit_agent_claim_correction from OpenAI. Explain the limitation and retain proposed correction text for human review without claiming submission. See unsupported-workflows.json for the excluded canonical workflow.\n"
}