Update to OloLand DD

{
  "description": "Use when the user asks to run the OloLand ololand-dd-watchlist workflow. Create, inspect, and promote OloLand watchlists for continuous company and signal monitoring.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 400
    }
  ],
  "name": "ololand-dd-watchlist",
  "skill_md_contents": "---\nname: ololand-dd-watchlist\ndescription: Use when the user asks to run the OloLand ololand-dd-watchlist workflow.\n  Create, inspect, and promote OloLand watchlists for continuous company and signal\n  monitoring.\n---\n\n\n# Workflow for ololand-dd-watchlist\n\nFollow the OloLand command instructions below when the user asks for `ololand-dd-watchlist` or the equivalent workflow.\n\n# Watchlist\n\nUse this command when the user wants ongoing monitoring for a sourcing thesis, signal-driven target tracking, or promotion of a watchlist match into a deal.\n\n## Usage\n\n```\nololand-dd-watchlist list\nololand-dd-watchlist create \"Healthcare IT carveouts\" criteria='{\"query\":\"healthcare IT carveouts\",\"company_scope\":\"both\"}'\nololand-dd-watchlist matches <watchlist_id>\nololand-dd-watchlist promote <watchlist_id> <match_id>\n```\n\n## Execution\n\n1. `list` — call `list_watchlists`.\n2. `create` — ask for a name and criteria if absent, then call `create_watchlist`.\n3. `matches` — call `list_watchlist_matches`, defaulting to active/non-dismissed matches.\n4. `promote` — confirm the user wants to create a deal, then call `promote_watchlist_match`.\n5. If the user starts from prose instead of a watchlist id, run `ololand-dd-company-discovery` first and use its filters as watchlist criteria.\n\n## Output\n\n- For lists: watchlist name, matched count, threshold, last matched time, and criteria.\n- For matches: company, match score, match reason, signal count, promoted deal id if present.\n- For promote: created deal id, canonical company name, and returned `view_url`.\n\n## Guardrails\n\n- Promotion creates a real deal row. Confirm before calling `promote_watchlist_match`.\n- Dismissal/pinning remains a UI workflow unless the user explicitly asks for match state updates.\n- Watchlists are monitoring infrastructure, not diligence conclusions.\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"
}