Update to OloLand DD

{
  "description": "Use when the user asks to run the OloLand ololand-dd-value-impact workflow. Review or preview OloLand's value-impact ledger for a deal or firm. Shows hours saved, labor/advisor cost avoided, platform cost completeness, and methodology snapshots.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 440
    }
  ],
  "name": "ololand-dd-value-impact",
  "skill_md_contents": "---\nname: ololand-dd-value-impact\ndescription: Use when the user asks to run the OloLand ololand-dd-value-impact workflow.\n  Review or preview OloLand's value-impact ledger for a deal or firm. Shows hours\n  saved, labor/advisor cost avoided, platform cost completeness, and methodology snapshots.\n---\n\n\n# Workflow for ololand-dd-value-impact\n\nFollow the OloLand command instructions below when the user asks for `ololand-dd-value-impact` or the equivalent workflow.\n\n# Value Impact\n\nUse this command when the user asks for ROI, hours saved, avoided QoE/advisor cost, value multiple, or the evidence behind OloLand's value-impact claims.\n\n## Usage\n\n```\nololand-dd-value-impact <deal_id>\nololand-dd-value-impact company [start=YYYY-MM-DD] [end=YYYY-MM-DD] [workflow=<workflow_key>]\nololand-dd-value-impact preview workflows=pre_loi_screen,full_qoe deals=12 cost=238800\n```\n\n## Execution\n\n1. If the first argument is a deal id, call `get_deal_value_impact(deal_id)`.\n2. If the first argument is `company` or the user asks for firm-wide ROI, call `get_company_value_impact` with any date/workflow filters.\n3. If the user asks \"what would this be worth if...\" call `preview_value_impact` with `workflows`, `workflow_counts`, `deals_per_year`, and optional `annual_platform_cost_cents`.\n4. If the user asks what assumptions drive the ledger, call `get_value_impact_assumptions`.\n5. Only call `update_value_impact_assumptions` when the user explicitly asks to change company ROI assumptions and confirms the values. That tool is company-admin gated.\n\n## Output\n\nRender:\n\n- **Value summary**: hours saved, labor cost avoided, advisor cost avoided, gross value, net value if platform cost is complete.\n- **Cost completeness**: `ololand_cost_is_complete`, missing-cost count, and whether `value_multiple` is known or intentionally withheld.\n- **Top events**: workflow, source, completed time, confidence, and methodology note.\n- **Assumptions**: hourly rates, display mode, external QoE baseline when relevant.\n- **Next action**: open the returned `view_url`, adjust assumptions, or run the workflow that would create missing events.\n\n## Guardrails\n\n- Never convert unknown OloLand cost to zero. If `net_value_cents` or `value_multiple` is null because cost is incomplete, say that directly.\n- Treat the ledger as substantiated estimate, not a guarantee of actual savings.\n- Preserve confidence and methodology notes when presenting dollar figures.\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"
}