{"id":76379,"plugin_id":"plugin_asdk_app_6ad3a430b30481919b3d089dabbc9b93","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-02T18:12:10.758Z","digest":"dccffe296f93499de006762887badbff2c538b568b518cd18bd603cd0e10ca30","against":null,"payload":{"description":"Use when the user asks to run the OloLand ololand-dd-okf-export workflow. Export an OloLand deal dossier as an OKF bundle for downstream system handoff.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":387}],"name":"ololand-dd-okf-export","skill_md_contents":"---\nname: ololand-dd-okf-export\ndescription: Use when the user asks to run the OloLand ololand-dd-okf-export workflow.\n  Export an OloLand deal dossier as an OKF bundle for downstream system handoff.\n---\n\n\n# Workflow for ololand-dd-okf-export\n\nFollow the OloLand command instructions below when the user asks for `ololand-dd-okf-export` or the equivalent workflow.\n\n# OKF Export\n\nUse this command when the user asks for an OKF bundle, portable deal dossier, or machine-readable export of a deal's OloLand record.\n\n## Usage\n\n```\nololand-dd-okf-export <deal_id>\n```\n\n## Execution\n\n1. Confirm the deal id.\n2. Call `export_deal_okf_bundle(deal_id)`.\n3. If the response includes artifact or download metadata, render it exactly and preserve provenance fields.\n4. If the user wants a regulator/compliance package instead, route to `ololand-dd-regulator-export`; OKF is a deal-record handoff, not the compliance-framework export.\n\n## Output\n\n- Bundle id/path or artifact id.\n- Included sections/data classes.\n- Any warnings about missing deal data.\n- Returned URL or retrieval instructions.\n\n## Guardrails\n\n- Do not describe OKF as a signed IC artifact.\n- Do not strip provenance, source ids, or methodology fields from the exported bundle summary.\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":{}}