[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XFG8BCDANVR2VE73V490M8":3,"skill-same:01M6XFG8BCDANVR2VE73V490M8":72},{"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},"01M6XFG8BCDANVR2VE73V490M8","claim-source-auditor",null,"Verify claims, quotes, timelines, and findings against supplied source files and return a source map with verified, conflicting, not found, and manual-review statuses. Use when the user asks to fact-check a memo, audit, timeline, executive summary, research packet, or project brief against PDFs, XML, HTML, notes, screenshots, exported chat logs, or other supplied files before sending, publishing, or relying on the result.","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\u002Fclaim-source-auditor\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"claim source auditor","source","auditor","claim","map","when","source map","project brief","manual","quotes","project","review","chat","files","publishing","use","check","brief","logs","executive summary","2026-11-10 10:12:30",false,"---\nname: claim-source-auditor\ndescription: >\n  Verify claims, quotes, timelines, and findings against supplied source files and return a source map\n  with verified, conflicting, not found, and manual-review statuses. Use when the user asks to fact-check\n  a memo, audit, timeline, executive summary, research packet, or project brief against PDFs, XML,\n  HTML, notes, screenshots, exported chat logs, or other supplied files before sending, publishing,\n  or relying on the result.\n---\n\n# Claim Source Auditor\n\n## Objective\n\nTurn a draft or claim set into a traceable evidence map. Separate what is proven, what is contradicted,\nwhat is not found in the searched source set, and what still needs manual review.\n\n## Directives\n\n| Parameter | Requirement |\n| --- | --- |\n| Formatting | Table-first; each claim gets a discrete status row |\n| Tone | Factual, restrained, audit-style |\n| Scope | Verification only; do not rewrite the whole narrative unless the verification results require targeted remediation |\n| Grounding | Every `verified` or `conflicting` result must trace to a named file, source location, or quoted passage |\n| Defaults | Use the fixed status taxonomy and keep unsourced claims unresolved rather than downgraded into speculation |\n| Fallback | If search or extraction is partial, return the searched scope, likely matches, and manual-review flags instead of overstating certainty |\n| Triggering | Use for source mapping, quote verification, claim checking, contradiction audits, and pre-release fact review |\n| Restrictions | Do not treat absence as falsity without naming the searched scope; do not paraphrase a quote as verified unless the exact wording or a faithful equivalent is present |\n\n## Workflow\n\n1. Define the audit scope: claims list, searched sources, and whether exact quotes are required.\n2. Break compound paragraphs into individual claims.\n3. Search the provided source set for exact wording first, then faithful supporting context.\n4. Assign one status per claim: `verified`, `verified in broader bundle`, `conflicting`, `not found in searched sources`, or `manual review needed`.\n5. Cite the exact source location when available.\n6. Separate remediation notes from evidence status so unsupported claims are easy to fix or remove.\n\n## Resources\n\n| Resource | Create When | Notes |\n| --- | --- | --- |\n| `scripts\u002F` | A claim-extraction or source-map helper exists | Optional |\n| `references\u002F` | A source hierarchy or record legend is needed | Useful for large evidence sets |\n| `assets\u002F` | A reusable audit table template is needed | Optional |\n| `agents\u002Fopenai.yaml` | The skill should appear cleanly in the UI | Keep the UI prompt focused on verification |\n\nPreferred status meanings:\n\n- `verified`: supported in the exact searched packet\n- `verified in broader bundle`: supported locally, but outside the narrow packet under review\n- `conflicting`: the source materially contradicts the draft claim\n- `not found in searched sources`: not located in the named search scope\n- `manual review needed`: likely present, but extraction, image content, or ambiguity blocks automatic confirmation\n\n## Validation\n\n1. Verify that every claim row names the searched source scope.\n2. Verify that every `verified` or `conflicting` row includes a concrete citation or file reference.\n3. Verify that every `not found` row distinguishes source absence from search limitation.\n4. Remove blended statuses and duplicated claims.\n5. Run `scripts\u002Fquick_validate.py \u003Cpath\u002Fto\u002Fskill-folder>` before delivery.\n","# Claim Source Auditor\n\n## Objective\n\nTurn a draft or claim set into a traceable evidence map. Separate what is proven, what is contradicted,\nwhat is not found in the searched source set, and what still needs manual review.\n\n## Directives\n\n| Parameter | Requirement |\n| --- | --- |\n| Formatting | Table-first; each claim gets a discrete status row |\n| Tone | Factual, restrained, audit-style |\n| Scope | Verification only; do not rewrite the whole narrative unless the verification results require targeted remediation |\n| Grounding | Every `verified` or `conflicting` result must trace to a named file, source location, or quoted passage |\n| Defaults | Use the fixed status taxonomy and keep unsourced claims unresolved rather than downgraded into speculation |\n| Fallback | If search or extraction is partial, return the searched scope, likely matches, and manual-review flags instead of overstating certainty |\n| Triggering | Use for source mapping, quote verification, claim checking, contradiction audits, and pre-release fact review |\n| Restrictions | Do not treat absence as falsity without naming the searched scope; do not paraphrase a quote as verified unless the exact wording or a faithful equivalent is present |\n\n## Workflow\n\n1. Define the audit scope: claims list, searched sources, and whether exact quotes are required.\n2. Break compound paragraphs into individual claims.\n3. Search the provided source set for exact wording first, then faithful supporting context.\n4. Assign one status per claim: `verified`, `verified in broader bundle`, `conflicting`, `not found in searched sources`, or `manual review needed`.\n5. Cite the exact source location when available.\n6. Separate remediation notes from evidence status so unsupported claims are easy to fix or remove.\n\n## Resources\n\n| Resource | Create When | Notes |\n| --- | --- | --- |\n| `scripts\u002F` | A claim-extraction or source-map helper exists | Optional |\n| `references\u002F` | A source hierarchy or record legend is needed | Useful for large evidence sets |\n| `assets\u002F` | A reusable audit table template is needed | Optional |\n| `agents\u002Fopenai.yaml` | The skill should appear cleanly in the UI | Keep the UI prompt focused on verification |\n\nPreferred status meanings:\n\n- `verified`: supported in the exact searched packet\n- `verified in broader bundle`: supported locally, but outside the narrow packet under review\n- `conflicting`: the source materially contradicts the draft claim\n- `not found in searched sources`: not located in the named search scope\n- `manual review needed`: likely present, but extraction, image content, or ambiguity blocks automatic confirmation\n\n## Validation\n\n1. Verify that every claim row names the searched source scope.\n2. Verify that every `verified` or `conflicting` row includes a concrete citation or file reference.\n3. Verify that every `not found` row distinguishes source absence from search limitation.\n4. Remove blended statuses and duplicated claims.\n5. Run `scripts\u002Fquick_validate.py \u003Cpath\u002Fto\u002Fskill-folder>` before delivery.\n",{"name":5,"description":7},"main","b22eca2e974f918ce591c5b2bd829fb7510e0191","Skills\u002Fclaim-source-auditor",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 claim-source-auditor",{"tool":58,"command":59},"bunx","bunx skills add FDU-INS\u002FInsurance-Skills --skill claim-source-auditor",{"tool":61,"command":62},"pnpm","pnpm dlx skills add FDU-INS\u002FInsurance-Skills --skill claim-source-auditor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fclaim-source-auditor\u002FSKILL.md",true,[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"agents\u002Fopenai.yaml","REFERENCE","参考文档",308,"https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fclaim-source-auditor\u002Fagents\u002Fopenai.yaml",[73,102,126,155,177,210],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":84,"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",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[75,85,86,87,88,89,24,30,90,91,92,93,94,95,96,97,98,99,100,101],"insurance law","insurance","civil","contract","family","loyalty","with","top","contract review","ceo","support","advice","consultation","regulatory","privacy","protection","startup",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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",[],[109,110,111,112,86,113,114,24,115,116,117,118,119,120,121,122,123,124,34,125],"zocdoc doctor finder","doctor","healthcare","reviews","browser automation","access","browsing","browser","booking","network","therapist","computer","availability","for","provider","tool","automation",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":137,"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",[132],{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[138,139,140,141,86,29,142,143,144,145,146,147,148,149,150,151,37,152,153,154],"context","zenmux context","Video","chinese","web search","translate","search","open","question","pay","image","you","activate","architecture","streaming","cherry studio","how",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"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",[],[162,163,164,165,166,86,167,168,34,24,169,91,170,171,172,173,174,175,176],"workers","comp","workers comp","workers comp guide","guide","triggers","workers-comp","tasks","claims management","claims","compliance","help","compensation","management","user",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":192,"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",[183,186,189],{"categoryNo":184,"categoryName":185,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":187,"categoryName":188,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":190,"categoryName":191,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000034","行政与办公人员",[193,194,195,196,197,86,198,199,200,201,24,202,203,204,205,206,207,208,34,209],"weekly","weekly kpi report","kpi","report","xlsx","actionable","insights","briefing","auto","board report","reports","generate","演示","data","presentation","slides","uploads",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":219,"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",[216],{"categoryNo":217,"categoryName":218,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000040","财务",[220,221,86,222,223,24,150,224,225,226,227,228,229,230,231,232,233,234,235,236],"wealth advisory","advisory","stock","inheritance","conversion","indexing","plan","simulation","personal finance","rate","allocation","asset","direct","personal","investing","trust","planning"]