Update to Aivana CIO Decision Twin

{
  "name": "vendor-ecosystem-intelligence",
  "description": "Analyze vendor dependencies, lock-in, concentration risk, contract exposure, cost, resilience, exit options and ecosystem health. Use for sourcing, architecture, risk and CIO/CFO reviews. Use when the user needs vendor ecosystem intelligence for CIO decision support.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 145
    }
  ],
  "skill_md_contents": "---\nname: vendor-ecosystem-intelligence\ndescription: Analyze vendor dependencies, lock-in, concentration risk, contract exposure, cost, resilience, exit options and ecosystem health. Use for sourcing, architecture, risk and CIO/CFO reviews. Use when the user needs vendor ecosystem intelligence for CIO decision support.\n---\n\n# Vendor Ecosystem Intelligence\n\n## Mission\n\nReveal enterprise exposure created by vendors, platforms, contracts, integrations and external service dependencies.\n\n## Inputs\n\nAccept vendor lists, contracts summaries, spend data, service performance, SLA notes, architecture dependencies, incident history, renewal dates and sourcing concerns.\n\n## Workflow\n\n1. Map vendors to business capabilities, systems, processes, data and risks.\n2. Detect concentration risk, lock-in, weak exit options, SLA gaps, cost escalation and hidden dependencies.\n3. Assess strategic fit, resilience, financial exposure and switching feasibility.\n4. Prioritize renegotiation, mitigation, dual-sourcing, architecture decoupling or exit planning.\n5. Produce executive sourcing and risk recommendations.\n\n## Output Format\n\n- Executive Summary\n- Vendor Dependency Map\n- Lock-in and Concentration Risks\n- Cost / Contract Exposure\n- Resilience and SLA Risks\n- Exit Options\n- Recommended Actions\n- Evidence & Assumptions\n- Missing Data\n\n## Guardrails\n\nDo not infer contract terms not provided. Mark commercial assumptions clearly.\n"
}