[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XG16CBYHY0N5FSMP76E308":3,"skill-same:01M6XG16CBYHY0N5FSMP76E308":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M6XG16CBYHY0N5FSMP76E308","extraction-policy-lookup-ar",null,"Consulta sistemas internos de Libra para obtener el documento de póliza a partir de datos del asegurado o del vehículo","FDU-INS\u002FInsurance-Skills","FDU-INS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F167067594?v=4","01M6XEYMRS4CVJMZ834YWE66BV","FDU-Insurance","01M6XEYMXPDA34HFM0ZE6AY78G",82,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fextraction-policy-lookup-ar\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27],"policy","extraction","lookup","ar","policy lookup","extraction policy lookup ar","para","de","stub","2026-11-10 10:12:30",false,"---\nname: extraction-policy-lookup-ar\ndescription: Consulta sistemas internos de Libra para obtener el documento de póliza a partir de datos del asegurado o del vehículo\nstatus: stub — integración técnica pendiente de definición con Juan Mazzochi\n---\n\n# Consulta de Póliza en Sistemas Internos (Policy Lookup AR)\n\nRecupera el documento de póliza desde los sistemas internos de Libra Seguros usando los datos identificatorios disponibles: número de póliza, dominio del vehículo, datos del asegurado o tomador.\n\nEste skill es una capa de integración — no analiza la póliza. El análisis lo hace `extraction-policy-summary-ar` sobre el documento que este skill devuelve.\n\n## Contexto\n\n- **Agente:** Mike (Extraction Agent)\n- **Se activa cuando:** `poliza_path = null` y hay datos identificatorios disponibles en el output de `extraction-claim-summary-ar`\n- **Output:** path al documento de póliza recuperado (para pasar a `extraction-policy-summary-ar`), o `null` con motivo si no se encuentra\n\n## Campos de búsqueda (orden de prioridad)\n\n1. `numero_poliza` — el más directo; extraído de la demanda por `extraction-claim-summary-ar`\n2. `vehiculo.dominio` — dominio del vehículo asegurado (ej: AQX769)\n3. `asegurado.dni` o `asegurado.cuit` — datos del tomador\u002Fasegurado\n4. `asegurado.nombre` + `vehiculo.marca_modelo` — búsqueda combinada como fallback\n\n## Input\n\n```json\n{\n  \"numero_poliza\": \"string | null\",\n  \"vehiculo\": {\n    \"dominio\": \"string | null\",\n    \"marca\": \"string | null\",\n    \"modelo\": \"string | null\"\n  },\n  \"asegurado\": {\n    \"nombre\": \"string | null\",\n    \"dni\": \"string | null\",\n    \"cuit\": \"string | null\"\n  },\n  \"fecha_siniestro\": \"ISO date — para verificar vigencia de la póliza a esa fecha\"\n}\n```\n\n## Output\n\n```json\n{\n  \"found\": true | false,\n  \"poliza_path\": \"ruta al documento recuperado | null\",\n  \"numero_poliza\": \"string | null\",\n  \"vigente_a_fecha_siniestro\": true | false | null,\n  \"motivo_no_encontrado\": \"string | null\",\n  \"confidence\": \"high | medium | low\"\n}\n```\n\n## TODO — Integración técnica (pendiente con Juan Mazzochi)\n\nLos siguientes puntos deben definirse antes de implementar este skill:\n\n- [ ] ¿Sistema de origen? (API REST \u002F base de datos directa \u002F sistema de gestión de pólizas)\n- [ ] ¿Endpoint o query? (URL, método, autenticación)\n- [ ] ¿Formato de respuesta del sistema? (JSON \u002F XML \u002F PDF \u002F otro)\n- [ ] ¿Credenciales de acceso? (API key \u002F OAuth \u002F usuario-contraseña)\n- [ ] ¿El sistema devuelve el documento de póliza completo o solo datos estructurados?\n- [ ] ¿Qué hacer si hay múltiples pólizas para el mismo vehículo\u002Fasegurado? (tomar la vigente a la fecha del siniestro)\n- [ ] ¿El sistema tiene entorno de staging para pruebas?\n\nVer: `docs\u002Fpolicy-lookup-integration.md`\n\n## Reglas\n\n- Si `found = false`: no bloquear el pipeline. Continuar con `policy_summary = null` y marcar como pendiente en la entrega al abogado.\n- Si `vigente_a_fecha_siniestro = false`: marcar como señal de atención crítica y escalar a Ali antes de continuar. Posible defensa de falta de cobertura por póliza no vigente al momento del siniestro.\n- Si `found = true` pero `confidence = low` (ej: match solo por nombre sin DNI): registrar ambigüedad y marcar para revisión humana.\n","# Consulta de Póliza en Sistemas Internos (Policy Lookup AR)\n\nRecupera el documento de póliza desde los sistemas internos de Libra Seguros usando los datos identificatorios disponibles: número de póliza, dominio del vehículo, datos del asegurado o tomador.\n\nEste skill es una capa de integración — no analiza la póliza. El análisis lo hace `extraction-policy-summary-ar` sobre el documento que este skill devuelve.\n\n## Contexto\n\n- **Agente:** Mike (Extraction Agent)\n- **Se activa cuando:** `poliza_path = null` y hay datos identificatorios disponibles en el output de `extraction-claim-summary-ar`\n- **Output:** path al documento de póliza recuperado (para pasar a `extraction-policy-summary-ar`), o `null` con motivo si no se encuentra\n\n## Campos de búsqueda (orden de prioridad)\n\n1. `numero_poliza` — el más directo; extraído de la demanda por `extraction-claim-summary-ar`\n2. `vehiculo.dominio` — dominio del vehículo asegurado (ej: AQX769)\n3. `asegurado.dni` o `asegurado.cuit` — datos del tomador\u002Fasegurado\n4. `asegurado.nombre` + `vehiculo.marca_modelo` — búsqueda combinada como fallback\n\n## Input\n\n```json\n{\n  \"numero_poliza\": \"string | null\",\n  \"vehiculo\": {\n    \"dominio\": \"string | null\",\n    \"marca\": \"string | null\",\n    \"modelo\": \"string | null\"\n  },\n  \"asegurado\": {\n    \"nombre\": \"string | null\",\n    \"dni\": \"string | null\",\n    \"cuit\": \"string | null\"\n  },\n  \"fecha_siniestro\": \"ISO date — para verificar vigencia de la póliza a esa fecha\"\n}\n```\n\n## Output\n\n```json\n{\n  \"found\": true | false,\n  \"poliza_path\": \"ruta al documento recuperado | null\",\n  \"numero_poliza\": \"string | null\",\n  \"vigente_a_fecha_siniestro\": true | false | null,\n  \"motivo_no_encontrado\": \"string | null\",\n  \"confidence\": \"high | medium | low\"\n}\n```\n\n## TODO — Integración técnica (pendiente con Juan Mazzochi)\n\nLos siguientes puntos deben definirse antes de implementar este skill:\n\n- [ ] ¿Sistema de origen? (API REST \u002F base de datos directa \u002F sistema de gestión de pólizas)\n- [ ] ¿Endpoint o query? (URL, método, autenticación)\n- [ ] ¿Formato de respuesta del sistema? (JSON \u002F XML \u002F PDF \u002F otro)\n- [ ] ¿Credenciales de acceso? (API key \u002F OAuth \u002F usuario-contraseña)\n- [ ] ¿El sistema devuelve el documento de póliza completo o solo datos estructurados?\n- [ ] ¿Qué hacer si hay múltiples pólizas para el mismo vehículo\u002Fasegurado? (tomar la vigente a la fecha del siniestro)\n- [ ] ¿El sistema tiene entorno de staging para pruebas?\n\nVer: `docs\u002Fpolicy-lookup-integration.md`\n\n## Reglas\n\n- Si `found = false`: no bloquear el pipeline. Continuar con `policy_summary = null` y marcar como pendiente en la entrega al abogado.\n- Si `vigente_a_fecha_siniestro = false`: marcar como señal de atención crítica y escalar a Ali antes de continuar. Posible defensa de falta de cobertura por póliza no vigente al momento del siniestro.\n- Si `found = true` pero `confidence = low` (ej: match solo por nombre sin DNI): registrar ambigüedad y marcar para revisión humana.\n",{"name":5,"status":33,"description":7},"stub — integración técnica pendiente de definición con Juan Mazzochi","main","b22eca2e974f918ce591c5b2bd829fb7510e0191","Skills\u002Fextraction-policy-lookup-ar",18,"https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills","https:\u002F\u002Fgithub.com\u002FFDU-INS","Fudan University Department of Risk Management and Insurance","2026-07-12 12:54:34",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add FDU-INS\u002FInsurance-Skills --skill extraction-policy-lookup-ar",{"tool":48,"command":49},"bunx","bunx skills add FDU-INS\u002FInsurance-Skills --skill extraction-policy-lookup-ar",{"tool":51,"command":52},"pnpm","pnpm dlx skills add FDU-INS\u002FInsurance-Skills --skill extraction-policy-lookup-ar","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fextraction-policy-lookup-ar\u002FSKILL.md",true,[],[57,88,113,144,166,199],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":68,"publishedAt":28},"01M713QW6EGEG0YAD75440GSD0","로인장 (Roinjiang)","Activates when the user needs legal advice, contract review, insurance law consultation, startup legal support, or any legal\u002Fregulatory matter. She is a top-tier in-house lawyer with absolute loyalty to the CEO, specializing in insurance law, financial consumer protection, privacy, contracts, labor law, family law, civil and criminal matters.","https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002F로인장 (Roinjiang)\u002FSKILL.md",[63],{"categoryNo":64,"categoryName":65,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[59,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87],"insurance law","insurance","civil","contract","family","when","review","loyalty","with","top","contract review","ceo","support","advice","consultation","regulatory","privacy","protection","startup",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":28},"01M713QRN8VFMA9VKS6R4DJ2WS","zocdoc-doctor-finder","Use when a user needs to find a doctor, dentist, specialist, therapist, or healthcare provider — especially when they mention insurance, in-network, availability, location, appointments, or booking. Also use for browsing provider reviews, comparing doctors by specialty, or checking if a provider takes their insurance.","https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fzocdoc-doctor-finder\u002FSKILL.md",[],[95,96,97,98,70,99,100,74,101,102,103,104,105,106,107,108,109,110,111,112],"zocdoc doctor finder","doctor","healthcare","reviews","browser automation","access","browsing","browser","booking","network","therapist","computer","availability","for","provider","tool","use","automation",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":124,"publishedAt":28},"01M713QKGV3FTX7EEYWKDM8ENZ","zenmux-context","Answers any question about ZenMux by reading the latest official documentation. Use this skill whenever the user asks about ZenMux product features, API usage, configuration, integration, pricing, models, providers, routing, fallback, streaming, multimodal, structured output, tool calling, reasoning, prompt caching, image generation, video generation, web search, long context, observability, logs, cost tracking, usage analytics, insurance, subscription, pay-as-you-go, invoices, best practices for tools like Claude Code, Cursor, Cline, CodeX, Gemini CLI, opencode, Cherry Studio, Obsidian, Sider, Open-WebUI, Dify, Neovate, GitHub Copilot, OpenClaw, CC-Switch, Immersive Translate, Studio Chat, architecture, benchmarks, FAQ, contact, privacy, terms of service, compliance, or any other ZenMux-related topic. Also trigger when the user writes in Chinese about ZenMux: 文档, 使用指南, 快速开始, API 参考, 最佳实践, 模型路由, 供应商路由, 订阅, 按量计费, 可观测性, 帮助, 常见问题, 接入指南, 配置. Trigger on phrases like \"how to use ZenMux\", \"ZenMux docs\", \"ZenMux API\", \"ZenMux integration\", \"ZenMux 怎么用\", \"ZenMux 接入\", \"ZenMux 配置\". Even if the user doesn't say \"ZenMux\" explicitly but asks about LLM API aggregation, model routing, provider fallback in a context where ZenMux is the project being worked on, this skill should activate.","https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fzenmux-context\u002FSKILL.md",[119],{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[125,126,127,128,70,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143],"context","zenmux context","Video","chinese","project","web search","translate","search","open","question","pay","image","you","activate","architecture","logs","streaming","cherry studio","how",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":28},"01M713QHWTBG634BCBV7NBJME1","workers-comp-guide","Guide workers compensation compliance and claims management.\nTRIGGERS - Use when user needs help with workers-comp-guide related tasks.","https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fworkers-comp-guide\u002FSKILL.md",[],[151,152,153,154,155,70,156,157,111,74,158,77,159,160,161,162,163,164,165],"workers","comp","workers comp","workers comp guide","guide","triggers","workers-comp","tasks","claims management","claims","compliance","help","compensation","management","user",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":181,"publishedAt":28},"01M713QF45VMV1685AFNF1GPMA","weekly-kpi-report","Generate McKinsey-style board presentation PPTs from weekly auto insurance data. Automatically calculates 16+ KPIs, creates executive-level slides with actionable insights, and supports week-over-week comparisons. Use when user uploads insurance cost data (Excel\u002FCSV) and requests board report, weekly presentation, executive briefing, or mentions keywords like 董事会汇报, 周报PPT, 经营分析演示, McKinsey-style reports.","https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fweekly-kpi-report\u002FSKILL.md",[172,175,178],{"categoryNo":173,"categoryName":174,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":176,"categoryName":177,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":179,"categoryName":180,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000034","行政与办公人员",[182,183,184,185,186,70,187,188,189,190,74,191,192,193,194,195,196,197,111,198],"weekly","weekly kpi report","kpi","report","xlsx","actionable","insights","briefing","auto","board report","reports","generate","演示","data","presentation","slides","uploads",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":208,"publishedAt":28},"01M713QA9WJDHMNVTTY1ENRKVB","wealth-advisory","Wealth management and financial planning for HNW and UHNW clients. Activate when the user\nmentions wealth management, financial planning, retirement, estate planning, tax planning,\nGRAT, IDGT, trust, asset allocation, withdrawal rate, Monte Carlo simulation, goals-based\ninvesting, tax-loss harvesting, Roth conversion, insurance, annuity, mortgage strategy,\nconcentrated stock, family office, direct indexing, 529 plan, charitable giving, donor-advised\nfund, private foundation, or asks about personal finance strategy, inheritance, long-term\nfinancial planning, or UHNW advisory.","https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fwealth-advisory\u002FSKILL.md",[205],{"categoryNo":206,"categoryName":207,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000040","财务",[209,210,70,211,212,74,138,213,214,215,216,217,218,219,220,221,222,223,224,225],"wealth advisory","advisory","stock","inheritance","conversion","indexing","plan","simulation","personal finance","rate","allocation","asset","direct","personal","investing","trust","planning"]