[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XGK2K7FP2B25SP0SS5VA0F":3,"skill-same:01M6XGK2K7FP2B25SP0SS5VA0F":66},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6XGK2K7FP2B25SP0SS5VA0F","insurance-claim-summaries",null,"Generates structured summaries of U.S. insurance claim files covering identification, incident narrative, party positions, coverage analysis, and resolution status. Use when synthesizing claim files for adjusters, legal counsel, or claims managers during pre-filing review, discovery, or settlement preparation. Trigger keywords: claim summary, insurance claim, coverage summary, adjuster summary, coverage denial, reservation of rights.","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\u002Finsurance-claim-summaries\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"insurance claim summaries","insurance","summaries","claim","trigger","when","for","claims","managers","filing","identification","review","resolution","incident","files","en","use","coverage","discovery","analysis","2026-11-10 10:12:30",false,"---\nname: insurance-claim-summaries\nlanguage: en\ndescription: >-\n  Generates structured summaries of U.S. insurance claim files covering\n  identification, incident narrative, party positions, coverage analysis,\n  and resolution status. Use when synthesizing claim files for adjusters,\n  legal counsel, or claims managers during pre-filing review, discovery,\n  or settlement preparation. Trigger keywords: claim summary, insurance\n  claim, coverage summary, adjuster summary, coverage denial, reservation\n  of rights.\n---\n\n# Insurance Claim Summary\n\nSynthesizes a claim file into a structured quick-reference summary covering incident facts, party positions, coverage analysis, and resolution status.\n\n## Prerequisites\n\nGather before starting:\n\n- **Claim file** — submission, policy declarations, endorsements, correspondence\n- **Coverage position** — denial letters, reservation-of-rights letters, position statements\n- **Investigation** — inspection reports, statements, medical records, damage assessments\n- **Resolution** (if applicable) — settlement agreements, releases, payment records\n\n## Output Structure\n\n### 1. Claim Identification Header\n\n| Field | Value |\n|---|---|\n| Claim Number | |\n| Policy Number | |\n| Named Insured | |\n| Claimant (if different) | |\n| Date of Loss | |\n| Date Claim Filed | |\n| Coverage Type | |\n| Current Status | Open \u002F Closed \u002F In Litigation \u002F ADR Pending |\n\n### 2. Incident Narrative\n\n- What occurred, when, where\n- Circumstances triggering coverage\n- Chronological key events with dates\n\n### 3. Claimant's Position\n\n- Alleged damages\u002Finjuries\u002Flosses — itemized by category\n- Policy provisions or coverage grants cited\n- Total amount — label as: **claimed** \u002F **paid** \u002F **in dispute**\n- Key supporting evidence submitted\n\n### 4. Insurer's Response\n\n- Coverage determination: full acceptance \u002F partial \u002F denial\n- If denied or limited:\n  - Exclusions, conditions, or limitations relied upon (quote verbatim)\n  - Defenses raised: late notice, misrepresentation, failure to cooperate, fraud\n- Investigation scope and key findings\n- Insurer's independent valuation (if different from claimed)\n- Reservation-of-rights status and scope\n\n### 5. Resolution \u002F Current Status\n\n**If resolved:**\n- Outcome: paid in full \u002F negotiated settlement \u002F denial upheld \u002F withdrawn\n- Amount paid and date\n- Release scope: full \u002F partial \u002F rights preserved\n\n**If open or disputed:**\n- Posture: pre-suit \u002F litigation filed \u002F ADR pending\n- Court\u002Fforum and docket number (if in litigation)\n- Unresolved issues\n- Next steps and key deadlines\n\n### 6. Special Issues *(only if applicable)*\n\n- Bad faith allegations or regulatory concerns\n- Subrogation rights and recovery potential\n- Coordination of benefits \u002F other insurance\n- Third-party liability\n- Statute of limitations or suit-limitation deadlines [VERIFY state-specific periods]\n\n## Guardrails\n\n- **Objectivity** — Do not characterize either position as stronger unless summarizing an adjudicator's findings\n- **Disputed facts** — Attribute each version to its source; never state contested facts as established\n- **Policy language** — Quote verbatim when interpretation is at issue; flag ambiguities\n- **Monetary precision** — Label all figures as claimed, paid, or in dispute — never conflate\n- **Source citations** — Reference documents by name and date for cross-referencing\n- **Jurisdiction** — US-focused; note state-specific bad faith standards where raised [VERIFY]\n\n---\n\n**Key changes made:**\n\n- **Removed `tags`** — not part of the Agent Skills spec; only `name` and `description` are required frontmatter\n- **Tightened description** — removed redundant clause listing (\"claim identification, incident narrative, claimant's position with alleged damages and policy citations, insurer's response including coverage decisions and exclusions relied upon\") and replaced with concise categories\n- **Shortened prerequisites** — removed verbose parenthetical expansions where the label already communicates the meaning\n- **Trimmed output sections** — cut filler words (\"clearly\", \"key supporting evidence and documentation submitted\" → \"Key supporting evidence submitted\") throughout\n- **Renamed \"Guidelines\" → \"Guardrails\"** — more action-oriented framing for a pitfalls\u002Fchecks section\n- **Removed \"Accessibility\" guideline** — Claude already knows to use plain language; doesn't justify its token cost\n- **Reduced from 94 to 79 lines** — ~16% token savings while preserving all domain-specific legal content and structural accuracy\n","# Insurance Claim Summary\n\nSynthesizes a claim file into a structured quick-reference summary covering incident facts, party positions, coverage analysis, and resolution status.\n\n## Prerequisites\n\nGather before starting:\n\n- **Claim file** — submission, policy declarations, endorsements, correspondence\n- **Coverage position** — denial letters, reservation-of-rights letters, position statements\n- **Investigation** — inspection reports, statements, medical records, damage assessments\n- **Resolution** (if applicable) — settlement agreements, releases, payment records\n\n## Output Structure\n\n### 1. Claim Identification Header\n\n| Field | Value |\n|---|---|\n| Claim Number | |\n| Policy Number | |\n| Named Insured | |\n| Claimant (if different) | |\n| Date of Loss | |\n| Date Claim Filed | |\n| Coverage Type | |\n| Current Status | Open \u002F Closed \u002F In Litigation \u002F ADR Pending |\n\n### 2. Incident Narrative\n\n- What occurred, when, where\n- Circumstances triggering coverage\n- Chronological key events with dates\n\n### 3. Claimant's Position\n\n- Alleged damages\u002Finjuries\u002Flosses — itemized by category\n- Policy provisions or coverage grants cited\n- Total amount — label as: **claimed** \u002F **paid** \u002F **in dispute**\n- Key supporting evidence submitted\n\n### 4. Insurer's Response\n\n- Coverage determination: full acceptance \u002F partial \u002F denial\n- If denied or limited:\n  - Exclusions, conditions, or limitations relied upon (quote verbatim)\n  - Defenses raised: late notice, misrepresentation, failure to cooperate, fraud\n- Investigation scope and key findings\n- Insurer's independent valuation (if different from claimed)\n- Reservation-of-rights status and scope\n\n### 5. Resolution \u002F Current Status\n\n**If resolved:**\n- Outcome: paid in full \u002F negotiated settlement \u002F denial upheld \u002F withdrawn\n- Amount paid and date\n- Release scope: full \u002F partial \u002F rights preserved\n\n**If open or disputed:**\n- Posture: pre-suit \u002F litigation filed \u002F ADR pending\n- Court\u002Fforum and docket number (if in litigation)\n- Unresolved issues\n- Next steps and key deadlines\n\n### 6. Special Issues *(only if applicable)*\n\n- Bad faith allegations or regulatory concerns\n- Subrogation rights and recovery potential\n- Coordination of benefits \u002F other insurance\n- Third-party liability\n- Statute of limitations or suit-limitation deadlines [VERIFY state-specific periods]\n\n## Guardrails\n\n- **Objectivity** — Do not characterize either position as stronger unless summarizing an adjudicator's findings\n- **Disputed facts** — Attribute each version to its source; never state contested facts as established\n- **Policy language** — Quote verbatim when interpretation is at issue; flag ambiguities\n- **Monetary precision** — Label all figures as claimed, paid, or in dispute — never conflate\n- **Source citations** — Reference documents by name and date for cross-referencing\n- **Jurisdiction** — US-focused; note state-specific bad faith standards where raised [VERIFY]\n\n---\n\n**Key changes made:**\n\n- **Removed `tags`** — not part of the Agent Skills spec; only `name` and `description` are required frontmatter\n- **Tightened description** — removed redundant clause listing (\"claim identification, incident narrative, claimant's position with alleged damages and policy citations, insurer's response including coverage decisions and exclusions relied upon\") and replaced with concise categories\n- **Shortened prerequisites** — removed verbose parenthetical expansions where the label already communicates the meaning\n- **Trimmed output sections** — cut filler words (\"clearly\", \"key supporting evidence and documentation submitted\" → \"Key supporting evidence submitted\") throughout\n- **Renamed \"Guidelines\" → \"Guardrails\"** — more action-oriented framing for a pitfalls\u002Fchecks section\n- **Removed \"Accessibility\" guideline** — Claude already knows to use plain language; doesn't justify its token cost\n- **Reduced from 94 to 79 lines** — ~16% token savings while preserving all domain-specific legal content and structural accuracy\n",{"name":5,"language":34,"description":7},"main","b22eca2e974f918ce591c5b2bd829fb7510e0191","Skills\u002Finsurance-claim-summaries",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add FDU-INS\u002FInsurance-Skills --skill insurance-claim-summaries",{"tool":58,"command":59},"bunx","bunx skills add FDU-INS\u002FInsurance-Skills --skill insurance-claim-summaries",{"tool":61,"command":62},"pnpm","pnpm dlx skills add FDU-INS\u002FInsurance-Skills --skill insurance-claim-summaries","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Finsurance-claim-summaries\u002FSKILL.md",true,[],[67,95,118,149,170,203],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":78,"publishedAt":39},"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",[73],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[69,79,20,80,81,82,24,30,83,84,85,86,87,88,89,90,91,92,93,94],"insurance law","civil","contract","family","loyalty","with","top","contract review","ceo","support","advice","consultation","regulatory","privacy","protection","startup",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":39},"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",[],[102,103,104,105,20,106,107,24,108,109,110,111,112,113,114,25,115,116,35,117],"zocdoc doctor finder","doctor","healthcare","reviews","browser automation","access","browsing","browser","booking","network","therapist","computer","availability","provider","tool","automation",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":129,"publishedAt":39},"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",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[130,131,132,133,20,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148],"context","zenmux context","Video","chinese","project","web search","translate","search","open","question","pay","image","you","activate","architecture","logs","streaming","cherry studio","how",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":39},"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",[],[156,157,158,159,160,20,161,162,35,24,163,84,164,26,165,166,167,168,169],"workers","comp","workers comp","workers comp guide","guide","triggers","workers-comp","tasks","claims management","compliance","help","compensation","management","user",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":185,"publishedAt":39},"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",[176,179,182],{"categoryNo":177,"categoryName":178,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":180,"categoryName":181,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":183,"categoryName":184,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000034","行政与办公人员",[186,187,188,189,190,20,191,192,193,194,24,195,196,197,198,199,200,201,35,202],"weekly","weekly kpi report","kpi","report","xlsx","actionable","insights","briefing","auto","board report","reports","generate","演示","data","presentation","slides","uploads",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":212,"publishedAt":39},"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",[209],{"categoryNo":210,"categoryName":211,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000040","财务",[213,214,20,215,216,24,143,217,218,219,220,221,222,223,224,225,226,227,228,229],"wealth advisory","advisory","stock","inheritance","conversion","indexing","plan","simulation","personal finance","rate","allocation","asset","direct","personal","investing","trust","planning"]