[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XFSFAPASZ1J1DDV8VKH3P1":3,"skill-same:01M6XFSFAPASZ1J1DDV8VKH3P1":70},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6XFSFAPASZ1J1DDV8VKH3P1","coverage-opinion",null,"Drafts structured insurance coverage opinions analyzing duty to defend and duty to indemnify for carriers. Applies eight corners rule, policy exclusion analysis, and state-specific law. Use when a carrier receives a claim or lawsuit, needs a coverage determination, reservation of rights analysis, or defense obligation assessment.","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\u002Fcoverage-opinion\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"coverage opinion","coverage","claim","Insurance coverage","insurance","when","for","drafts","rights","rule","structured","policy","en","use","analysis","defense","analyzing","state","assessment","2026-11-10 10:12:30",false,"---\nname: coverage-opinion\nlanguage: en\ndescription: Drafts structured insurance coverage opinions analyzing duty to defend and duty to indemnify for carriers. Applies eight corners rule, policy exclusion analysis, and state-specific law. Use when a carrier receives a claim or lawsuit, needs a coverage determination, reservation of rights analysis, or defense obligation assessment.\n---\n\n# Insurance Coverage Opinion\n\nAnalyzes policy language, complaint allegations, and state law to produce a definitive coverage opinion on defense, indemnification, and reservation of rights for carriers.\n\n## Prerequisites\n\nGather before starting:\n\n1. **Insurance policy** — declarations page, coverage forms, all endorsements, policy period\n2. **Complaint or claim** — operative pleading or demand triggering analysis\n3. **Supporting materials** — police reports, claim file notes, correspondence (if available)\n4. **Controlling jurisdiction** — state whose insurance law governs\n\n## Quick Start\n\nWrite from the carrier's perspective. Be definitive — carriers need actionable guidance, not hedging. When genuinely uncertain, recommend defend-under-reservation.\n\n## Core Workflow\n\nDraft each section in order (except Executive Summary — write last, place first):\n\n### 1. Executive Summary\n\n> \"Based on our analysis of the [Policy Type] policy and the allegations in the complaint, [Carrier] has [no duty to defend \u002F a duty to defend subject to a reservation of rights \u002F a clear duty to defend and indemnify] because [primary reason].\"\n\nBe definitive. Avoid \"probably\" or \"might.\"\n\n### 2. Factual Background\n\n- Recite only facts from complaint or claim file — no speculation\n- Coverage-relevant facts only; neutral tone\n\n### 3. Policy Analysis\n\nThree sub-sections, always quoting exact policy language (never paraphrase):\n\n| Sub-Section | Focus |\n|---|---|\n| **Coverage Provisions** | Quote exact language; identify specific section (CGL Coverage A, etc.) |\n| **Exclusions** | List every applicable exclusion with exact quoted language — typically where coverage is defeated |\n| **Conditions** | Notice requirements, cooperation clauses, late-notice defenses, consent-to-settle |\n\n### 4. Legal Analysis\n\n**Duty to Defend** — Apply the Eight Corners Rule (unless state permits extrinsic evidence):\n\n- [ ] Compare four corners of complaint against four corners of policy\n- [ ] Assess whether allegations could trigger coverage element-by-element\n- [ ] Analyze each exclusion for clear and unambiguous applicability\n- [ ] Apply \"any possibility of coverage\" standard — duty to defend is broad\n\nResearch whether jurisdiction follows strict eight corners or permits extrinsic evidence.\n\n**Duty to Indemnify** — Narrower standard based on actual facts, not allegations. Usually cannot be determined until case resolution. Default: \"The duty to indemnify cannot be determined at this time.\"\n\n### 5. State Law Considerations\n\nResearch and cite controlling jurisdiction on:\n\n- Eight corners vs. extrinsic evidence standard\n- Ambiguity interpretation (most states construe pro-insured)\n- State-specific exclusion construction rules\n- Current case law — mark uncertain citations with [VERIFY]\n\n### 6. Conclusion & Recommendations\n\nUse definitive language matching one of three outcomes:\n\n- **No coverage**: \"[Carrier] has no duty to defend or indemnify because [exclusion] unambiguously bars coverage.\"\n- **Questionable**: \"[Carrier] should defend under reservation of rights because [reason], while investigating [issues].\"\n- **Clear coverage**: \"[Carrier] has a duty to defend and likely a duty to indemnify.\"\n\nInclude: whether to issue reservation of rights letter, specific rights reserved, additional investigation needed, coverage defenses to preserve, timeline considerations.\n\n### 7. Reservation of Rights\n\nWhen coverage is questionable, default to recommending reservation. Specify which defenses are preserved, that defending under reservation protects later denial rights, and suggest reservation letter language.\n\n## Pitfalls\n\n- **Never paraphrase policy language** — always quote exact text\n- **Duty to defend != duty to indemnify** — analyze separately with distinct standards\n- **No added facts** — never assume facts not alleged in the complaint\n- **Bad faith exposure** — analysis must be objective even representing the carrier; wrongful denial creates liability\n- **Stale citations** — insurance law evolves rapidly; verify all cited authority is current\n- **Timing** — flag delays immediately; coverage decisions affect litigation strategy\n- **Updateability** — note opinion may require revision as facts develop\n\n---\n\n**Key changes from original:**\n\n- Removed `tags` (not part of the spec's required frontmatter)\n- Trimmed description while preserving trigger guidance and keywords\n- Collapsed redundant prose — overview is now 1 sentence\n- Renamed \"Output Structure\" to \"Core Workflow\" with a quick-start section above it\n- Consolidated Guidelines into a \"Pitfalls\" section with tighter bullet points\n- Eliminated the duplicate \"Why It Matters\" table in State Law (replaced with a flat list)\n- Removed the separate Conclusion recommendation templates' checkbox format where a sentence suffices\n- Reduced from ~117 lines to ~85 lines (~27% token reduction) while preserving all domain-critical content\n\nWant me to try the write again, or would you prefer to copy this manually?\n","# Insurance Coverage Opinion\n\nAnalyzes policy language, complaint allegations, and state law to produce a definitive coverage opinion on defense, indemnification, and reservation of rights for carriers.\n\n## Prerequisites\n\nGather before starting:\n\n1. **Insurance policy** — declarations page, coverage forms, all endorsements, policy period\n2. **Complaint or claim** — operative pleading or demand triggering analysis\n3. **Supporting materials** — police reports, claim file notes, correspondence (if available)\n4. **Controlling jurisdiction** — state whose insurance law governs\n\n## Quick Start\n\nWrite from the carrier's perspective. Be definitive — carriers need actionable guidance, not hedging. When genuinely uncertain, recommend defend-under-reservation.\n\n## Core Workflow\n\nDraft each section in order (except Executive Summary — write last, place first):\n\n### 1. Executive Summary\n\n> \"Based on our analysis of the [Policy Type] policy and the allegations in the complaint, [Carrier] has [no duty to defend \u002F a duty to defend subject to a reservation of rights \u002F a clear duty to defend and indemnify] because [primary reason].\"\n\nBe definitive. Avoid \"probably\" or \"might.\"\n\n### 2. Factual Background\n\n- Recite only facts from complaint or claim file — no speculation\n- Coverage-relevant facts only; neutral tone\n\n### 3. Policy Analysis\n\nThree sub-sections, always quoting exact policy language (never paraphrase):\n\n| Sub-Section | Focus |\n|---|---|\n| **Coverage Provisions** | Quote exact language; identify specific section (CGL Coverage A, etc.) |\n| **Exclusions** | List every applicable exclusion with exact quoted language — typically where coverage is defeated |\n| **Conditions** | Notice requirements, cooperation clauses, late-notice defenses, consent-to-settle |\n\n### 4. Legal Analysis\n\n**Duty to Defend** — Apply the Eight Corners Rule (unless state permits extrinsic evidence):\n\n- [ ] Compare four corners of complaint against four corners of policy\n- [ ] Assess whether allegations could trigger coverage element-by-element\n- [ ] Analyze each exclusion for clear and unambiguous applicability\n- [ ] Apply \"any possibility of coverage\" standard — duty to defend is broad\n\nResearch whether jurisdiction follows strict eight corners or permits extrinsic evidence.\n\n**Duty to Indemnify** — Narrower standard based on actual facts, not allegations. Usually cannot be determined until case resolution. Default: \"The duty to indemnify cannot be determined at this time.\"\n\n### 5. State Law Considerations\n\nResearch and cite controlling jurisdiction on:\n\n- Eight corners vs. extrinsic evidence standard\n- Ambiguity interpretation (most states construe pro-insured)\n- State-specific exclusion construction rules\n- Current case law — mark uncertain citations with [VERIFY]\n\n### 6. Conclusion & Recommendations\n\nUse definitive language matching one of three outcomes:\n\n- **No coverage**: \"[Carrier] has no duty to defend or indemnify because [exclusion] unambiguously bars coverage.\"\n- **Questionable**: \"[Carrier] should defend under reservation of rights because [reason], while investigating [issues].\"\n- **Clear coverage**: \"[Carrier] has a duty to defend and likely a duty to indemnify.\"\n\nInclude: whether to issue reservation of rights letter, specific rights reserved, additional investigation needed, coverage defenses to preserve, timeline considerations.\n\n### 7. Reservation of Rights\n\nWhen coverage is questionable, default to recommending reservation. Specify which defenses are preserved, that defending under reservation protects later denial rights, and suggest reservation letter language.\n\n## Pitfalls\n\n- **Never paraphrase policy language** — always quote exact text\n- **Duty to defend != duty to indemnify** — analyze separately with distinct standards\n- **No added facts** — never assume facts not alleged in the complaint\n- **Bad faith exposure** — analysis must be objective even representing the carrier; wrongful denial creates liability\n- **Stale citations** — insurance law evolves rapidly; verify all cited authority is current\n- **Timing** — flag delays immediately; coverage decisions affect litigation strategy\n- **Updateability** — note opinion may require revision as facts develop\n\n---\n\n**Key changes from original:**\n\n- Removed `tags` (not part of the spec's required frontmatter)\n- Trimmed description while preserving trigger guidance and keywords\n- Collapsed redundant prose — overview is now 1 sentence\n- Renamed \"Output Structure\" to \"Core Workflow\" with a quick-start section above it\n- Consolidated Guidelines into a \"Pitfalls\" section with tighter bullet points\n- Eliminated the duplicate \"Why It Matters\" table in State Law (replaced with a flat list)\n- Removed the separate Conclusion recommendation templates' checkbox format where a sentence suffices\n- Reduced from ~117 lines to ~85 lines (~27% token reduction) while preserving all domain-critical content\n\nWant me to try the write again, or would you prefer to copy this manually?\n",{"name":5,"language":36,"description":7},"main","b22eca2e974f918ce591c5b2bd829fb7510e0191","Skills\u002Fcoverage-opinion",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add FDU-INS\u002FInsurance-Skills --skill coverage-opinion",{"tool":62,"command":63},"bunx","bunx skills add FDU-INS\u002FInsurance-Skills --skill coverage-opinion",{"tool":65,"command":66},"pnpm","pnpm dlx skills add FDU-INS\u002FInsurance-Skills --skill coverage-opinion","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fcoverage-opinion\u002FSKILL.md",true,[],[71,96,119,150,172,205],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":78,"publishedAt":43},"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",[77],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[73,79,28,80,81,82,29,83,84,85,86,87,88,89,90,91,92,93,94,95],"insurance law","civil","contract","family","review","loyalty","with","top","contract review","ceo","support","advice","consultation","regulatory","privacy","protection","startup",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":43},"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",[],[103,104,105,106,28,107,108,29,109,110,111,112,113,114,115,30,116,117,37,118],"zocdoc doctor finder","doctor","healthcare","reviews","browser automation","access","browsing","browser","booking","network","therapist","computer","availability","provider","tool","automation",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":130,"publishedAt":43},"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",[125],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[131,132,133,134,28,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149],"context","zenmux context","Video","chinese","project","web search","translate","search","open","question","pay","image","you","activate","architecture","logs","streaming","cherry studio","how",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":43},"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",[],[157,158,159,160,161,28,162,163,37,29,164,85,165,166,167,168,169,170,171],"workers","comp","workers comp","workers comp guide","guide","triggers","workers-comp","tasks","claims management","claims","compliance","help","compensation","management","user",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":187,"publishedAt":43},"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",[178,181,184],{"categoryNo":179,"categoryName":180,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":182,"categoryName":183,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":185,"categoryName":186,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员",[188,189,190,191,192,28,193,194,195,196,29,197,198,199,200,201,202,203,37,204],"weekly","weekly kpi report","kpi","report","xlsx","actionable","insights","briefing","auto","board report","reports","generate","演示","data","presentation","slides","uploads",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":214,"publishedAt":43},"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",[211],{"categoryNo":212,"categoryName":213,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000040","财务",[215,216,28,217,218,29,144,219,220,221,222,223,224,225,226,227,228,229,230,231],"wealth advisory","advisory","stock","inheritance","conversion","indexing","plan","simulation","personal finance","rate","allocation","asset","direct","personal","investing","trust","planning"]