{"id":76357,"plugin_id":"plugin_asdk_app_6ad3a430b30481919b3d089dabbc9b93","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-02T18:12:10.131Z","digest":"ebe2d0d270170cd2418fff56cb298a05668fedfdc7ed9248a790bd6cd391787f","against":null,"payload":{"description":"Use when the user asks to run the OloLand ololand-dd-dd-merger-analyze workflow. Run a third-party merger analysis on an announced or rumored acquisition. Use when the user is not a principal in the deal (banker, equity analyst, merger-arb, antitrust counsel, target board, journalist). Runs on Developer as part of the bounded single-deal trial.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":442}],"name":"ololand-dd-dd-merger-analyze","skill_md_contents":"---\nname: ololand-dd-dd-merger-analyze\ndescription: Use when the user asks to run the OloLand ololand-dd-dd-merger-analyze\n  workflow. Run a third-party merger analysis on an announced or rumored acquisition.\n  Use when the user is not a principal in the deal (banker, equity analyst, merger-arb,\n  antitrust counsel, target board, journalist). Runs on Developer as part of the bounded\n  single-deal trial.\n---\n\n\n# Workflow for ololand-dd-dd-merger-analyze\n\nFollow the OloLand command instructions below when the user asks for `ololand-dd-dd-merger-analyze` or the equivalent workflow.\n\n# ololand-dd-dd-merger-analyze\n\nYou are creating a third-party merger-analysis deal for an announced or rumored acquisition. The user is an *outside observer*, not a principal — distinct from `ololand-dd-dd-analyze`, which assumes the user's firm is the acquirer.\n\n## Required inputs\n\nAsk the user for these if any are missing:\n\n1. **target** — the company being acquired (free text, e.g. \"Discover Financial\").\n2. **acquirer** — the buyer (free text, e.g. \"Capital One\").\n\nOptional:\n- **announced_date** — ISO date (YYYY-MM-DD) of the merger announcement. Used by Lane C to anchor the 8-K window.\n- **target_cik** — SEC CIK if known (skips one entity-resolution round-trip).\n- **acquirer_cik** — same for the acquirer.\n\nIf the user gave a natural-language phrasing (\"examine Capital One's acquisition of Discover\", \"is the X-Y merger accretive?\"), parse target + acquirer from it; only ask back if the two companies are not unambiguously identifiable.\n\n## Action\n\n1. Call the OloLand MCP tool `analyze_announced_merger` with `target`, `acquirer`, and optional `announced_date` / CIKs. The tool returns `{deal_id, task_ids, view_url}`.\n\n2. Poll `get_merger_readiness(deal_id=...)` every ~30 seconds until all three sides (target / acquirer / combined) reach at least `medium` tier — or until two minutes pass, whichever is sooner.\n\n3. Surface the deal_id, view_url, and per-side readiness to the user. If any side is still `low` or `missing` after polling, name the missing artifacts and suggest manual uploads (8-K, 10-K, S-4, audited financials, market research).\n\n4. Direct the user to the cockpit (`view_url`) for the five hero tiles — deal terms, premium analysis, accretion/dilution, antitrust HHI, combined-DCF — plus per-side risk and financial tiles.\n\n## Subscription\n\nRuns on Developer as part of the bounded single-deal trial, metered against the monthly credit budget — no longer Pro-gated. Note `analyze_announced_merger` creates a deal, so a user who has already used their one deal will hit the one-deal-limit CTA. If any call returns `tier_gated: true`, surface the upgrade CTA at https://app.ololand.ai/settings/billing in your reply.\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"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}