Update to OloLand DD

{
  "description": "Use when the user asks to run the OloLand ololand-dd-compliance-analysis workflow. Run deal-scoped compliance analysis for OFAC screening, HSR threshold review, and CFIUS risk. Uses OloLand's context-aware compliance workbench.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 444
    }
  ],
  "name": "ololand-dd-compliance-analysis",
  "skill_md_contents": "---\nname: ololand-dd-compliance-analysis\ndescription: Use when the user asks to run the OloLand ololand-dd-compliance-analysis\n  workflow. Run deal-scoped compliance analysis for OFAC screening, HSR threshold\n  review, and CFIUS risk. Uses OloLand's context-aware compliance workbench.\n---\n\n\n# Workflow for ololand-dd-compliance-analysis\n\nFollow the OloLand command instructions below when the user asks for `ololand-dd-compliance-analysis` or the equivalent workflow.\n\n# Compliance Analysis\n\nRun OloLand's compliance workbench for sanctions, antitrust threshold, and national-security risk checks.\n\n## Usage\n\n```\nololand-dd-compliance-analysis <deal_id> [ofac|hsr|cfius|all]\n```\n\n## Arguments\n\n- `deal_id` (required) - The deal to analyze.\n- `scope` (optional) - `ofac`, `hsr`, `cfius`, or `all`. Default: `all`.\n\n## Execution\n\n1. For `ofac` or `all`, call `run_ofac_screen(deal_id)`. Pass explicit `entities` or `sdn_entries` only if the user supplied them.\n2. For `hsr` or `all`, call `run_hsr_analysis(deal_id)`. If the user supplies transaction value, buyer size, target size, or exemptions, pass those inputs through. Dollar inputs are in millions.\n3. For `cfius` or `all`, call `run_cfius_risk(deal_id, ...)`. Ask for missing acquirer country, target industry, government ownership, critical technology, critical infrastructure, sensitive data, and government-contract flags when they materially affect the result.\n4. Use returned `view_url` values for web app handoff.\n\n## Output\n\nRender:\n\n- **OFAC** - match status, matched entities, confidence, required remediation.\n- **HSR** - reportability status, thresholds crossed, exemptions, timing risk.\n- **CFIUS** - risk tier, drivers, mitigation path, filing recommendation.\n- **Open diligence asks** - missing identities, jurisdictions, NAICS/product categories, ownership, sensitive-data facts.\n\n## Guardrails\n\n- This is workflow support, not legal advice. Tell the user to involve counsel for filings, sanctions escalations, or CFIUS mitigation.\n- Do not treat missing acquirer/target details as clean results. Classify missing data as a gap.\n\n## Output URL Conventions\n\nUse the tool-returned `view_url`. Canonical surface:\n\n- Compliance workbench: `https://app.ololand.ai/deals/{deal_id}/analysis/compliance`\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"
}