← OloLand DDCONTENT HISTORY

Update to OloLand DD

Snapshot Nov 2, 2026 · 18:12 UTC · version 1.26.7

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save OloLand DD and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when the user asks to run the OloLand ololand-dd-risk-matrix workflow. Render the 67-category risk matrix (311 tracked risk factors) as an interactive inline tile.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 403
    }
  ],
  "name": "ololand-dd-risk-matrix",
  "skill_md_contents": "---\nname: ololand-dd-risk-matrix\ndescription: Use when the user asks to run the OloLand ololand-dd-risk-matrix workflow.\n  Render the 67-category risk matrix (311 tracked risk factors) as an interactive\n  inline tile.\n---\n\n\n# Workflow for ololand-dd-risk-matrix\n\nFollow the OloLand command instructions below when the user asks for `ololand-dd-risk-matrix` or the equivalent workflow.\n\nYou have access to the `render_risk_matrix_tile` MCP tool from the OloLand server.\n\nIf the user has a deal loaded (check conversation context or call `list_deals`), invoke `render_risk_matrix_tile` with that `deal_id`. The tool's response is an MCP App — show the interactive view only if the client supports it. Otherwise explain that display limitation and summarize only data actually returned by the tool.\n\nIf no deal is loaded, ask the user which deal they want to analyze, or offer to run `ololand-dd-dd-analyze` first.\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"
}

SHA-256 of public snapshot: 7f9be90d7a290957678c670eb3704c6f6aaa3b27842c32c3cda14e1f347cea58