{"id":76351,"plugin_id":"plugin_asdk_app_6ad3a430b30481919b3d089dabbc9b93","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-02T18:12:09.970Z","digest":"f6849e54676ce36aca5fd022c183a9a1eb3646c67c10fcdeaa1e422343eafbee","against":null,"payload":{"description":"Use when the user asks to run the OloLand ololand-dd-ai-finserv-moves workflow. Browse recent AI financial-services moves captured by OloNet's competitive scanner — competitor product launches, partner integrations, regulatory signals, pricing changes, personnel moves. Each move includes a source URL, signal strength, and the recommended OloLand response surface.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":454}],"name":"ololand-dd-ai-finserv-moves","skill_md_contents":"---\nname: ololand-dd-ai-finserv-moves\ndescription: \"Use when the user asks to run the OloLand ololand-dd-ai-finserv-moves\\\n  \\ workflow. Browse recent AI financial-services moves captured by OloNet's competitive\\\n  \\ scanner \\u2014 competitor product launches, partner integrations, regulatory signals,\\\n  \\ pricing changes, personnel moves. Each move includes a source URL, signal strength,\\\n  \\ and the recommended OloLand response surface.\"\n---\n\n\n# Workflow for ololand-dd-ai-finserv-moves\n\nFollow the OloLand command instructions below when the user asks for `ololand-dd-ai-finserv-moves` or the equivalent workflow.\n\n# ololand-dd-ai-finserv-moves\n\nYou are reading OloNet's persisted AI financial-services competitive-intel feed. Use this to pull recent context about competitors, partners, or the broader AI-in-finance market into a deal narrative, pitch deck, or strategy review.\n\n## Required inputs\n\nNone — but the feed is large. Default to a filtered query.\n\nOptional filters:\n- **actor** — substring match on the actor name (e.g. `Anthropic`, `BlackRock`, `Sequoia`).\n- **move_type** — `product_launch`, `partnership`, `regulatory`, `pricing`, `personnel`, etc.\n- **workflow_surface** — `dd`, `cim`, `risk`, `valuation`, `pricing`, etc. — surface the move pertains to.\n- **limit** — default 50, cap 200.\n- **offset** — pagination.\n\n## Action\n\nCall `list_ai_finserv_moves` with the chosen filters.\n\n## Output\n\nRender in reverse-chronological order:\n\n```\n<n> AI finserv moves (filters: <filters>)\n\n<collected_at>  <actor_name>\n  Move type:    <move_type>\n  Surface:      <workflow_surface>\n  Signal:       <signal_strength>\n  Source:       <source_url>\n  Summary:      <summary or facts excerpt>\n  Recommended:  <recommended_response>\n...\n```\n\nIf the user asks for a deeper look at one move, surface its full `extracted_facts` JSON and the source-record metadata.\n\n## When to use\n\n- Pre-meeting prep when a competitor or partner is on the agenda.\n- Updating a `/compare` page when a competitor ships something new.\n- Researching market context for a deal in a competitive segment.\n- Adding live competitive color to a CIM, IC memo, or strategy deck.\n\n## When NOT to use\n\n- For *deal-specific* intel — use `research_market` or `deep_market_research`. This feed is firm-wide, not deal-scoped.\n- For *historical* M&A deals — use `search_ma_deals` instead.\n- For *real-time* breaking news — the feed is gateway-ingested with up-to-14-day freshness; for sub-day signal, route to OloNet directly.\n\n## Ingestion is not exposed here\n\nThe matching ingest endpoint (`POST /api/ma/ai-finserv-moves/ingest`) is HMAC-keyed and reserved for the headless OloNet/OpenClaw gateway. There is no MCP write surface for new moves — feed corrections happen at the gateway, not via plugin. If a user sees a wrong move, ask them to flag it and route to the OloNet operator; do not attempt to mutate via MCP.\n\nCompanion skill: `cmd-ai-finserv-moves` (auto-loads).\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":{}}