[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M713PH8BD1Q52376ZRZP2BVK":3,"skill-same:01M713PH8BD1Q52376ZRZP2BVK":61},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M713PH8BD1Q52376ZRZP2BVK","updating-business-lexicon",null,"Use when translating French auto insurance business terms to English, editing rejection reasons, or introducing\u002Fchanging domain vocabulary that must stay aligned with the FR->EN lexicon table.","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\u002Fupdating-business-lexicon\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"business","updating business lexicon","french","domain","insurance","editing","en","auto","use","when","english","with","terms","vocabulary","table","2026-11-10 10:12:30",false,"---\nname: updating-business-lexicon\ndescription: Use when translating French auto insurance business terms to English, editing rejection reasons, or introducing\u002Fchanging domain vocabulary that must stay aligned with the FR->EN lexicon table.\n---\n\n# Updating Business Lexicon\n\n## Overview\n\nKeep domain language consistent by updating the FR->EN lexicon whenever a French business term is added or changed.\n\nCore principle: a business term change is incomplete until the lexicon table is updated in the same change.\n\n## Hard Gate\n\nNever finalize a French business-term translation\u002Fchange without including `.github\u002Finstructions\u002Fbusiness-lexicon.instructions.md` in the same change.\n\nIf a request says \"do not touch instruction files\", stop and state the conflict explicitly. Ask for an explicit override before skipping the lexicon update.\n\n## When to Use\n\nUse this skill when:\n- Translating business phrases from French to English\n- Renaming domain concepts in code, tests, docs, comments, commits, or PR text\n- Adding new rejection reasons or eligibility wording\n\nDo not use this skill for non-business technical wording (framework, infra, tooling terms).\n\n## Quick Reference\n\n| Situation | Required action |\n| --- | --- |\n| New French business term appears | Add one row in `.github\u002Finstructions\u002Fbusiness-lexicon.instructions.md` |\n| Existing French term meaning changes | Update the existing row and notes |\n| Multiple English options exist | Keep one canonical US English term and explain alternatives in `Notes` |\n| Fast translation request under pressure | Provide translation and still include\u002Fupdate lexicon row in the same change |\n\n## Implementation\n\n1. Identify the French business term(s) being introduced or changed.\n2. Open `.github\u002Finstructions\u002Fbusiness-lexicon.instructions.md`.\n3. Add or update the matching row in the `Correspondence Table`.\n4. Ensure US English terminology is used.\n5. Keep the table scoped to Auto Insurance terms.\n6. Deliver both changes together (term change + lexicon update).\n7. If blocked from editing instruction files, do not silently skip. Return a conflict message and request override.\n\nExample:\n- French term: `Conducteur trop jeune pour ce véhicule`\n- Canonical English: `Driver too young for this vehicle`\n- If new term appears, add row; if already covered, confirm consistency.\n\n## Common Mistakes\n\n- Translating text but forgetting to update the lexicon table.\n- Using UK variants (`driving licence`) instead of US (`driver's license`).\n- Adding duplicate French rows with slightly different wording.\n- Splitting updates across separate commits.\n\n## Red Flags\n\n- \"Just this one translation\"\n- \"Do not touch instruction files\"\n- \"Update the table later\"\n\nIf any red flag appears, enforce the hard gate and surface the conflict.\n","# Updating Business Lexicon\n\n## Overview\n\nKeep domain language consistent by updating the FR->EN lexicon whenever a French business term is added or changed.\n\nCore principle: a business term change is incomplete until the lexicon table is updated in the same change.\n\n## Hard Gate\n\nNever finalize a French business-term translation\u002Fchange without including `.github\u002Finstructions\u002Fbusiness-lexicon.instructions.md` in the same change.\n\nIf a request says \"do not touch instruction files\", stop and state the conflict explicitly. Ask for an explicit override before skipping the lexicon update.\n\n## When to Use\n\nUse this skill when:\n- Translating business phrases from French to English\n- Renaming domain concepts in code, tests, docs, comments, commits, or PR text\n- Adding new rejection reasons or eligibility wording\n\nDo not use this skill for non-business technical wording (framework, infra, tooling terms).\n\n## Quick Reference\n\n| Situation | Required action |\n| --- | --- |\n| New French business term appears | Add one row in `.github\u002Finstructions\u002Fbusiness-lexicon.instructions.md` |\n| Existing French term meaning changes | Update the existing row and notes |\n| Multiple English options exist | Keep one canonical US English term and explain alternatives in `Notes` |\n| Fast translation request under pressure | Provide translation and still include\u002Fupdate lexicon row in the same change |\n\n## Implementation\n\n1. Identify the French business term(s) being introduced or changed.\n2. Open `.github\u002Finstructions\u002Fbusiness-lexicon.instructions.md`.\n3. Add or update the matching row in the `Correspondence Table`.\n4. Ensure US English terminology is used.\n5. Keep the table scoped to Auto Insurance terms.\n6. Deliver both changes together (term change + lexicon update).\n7. If blocked from editing instruction files, do not silently skip. Return a conflict message and request override.\n\nExample:\n- French term: `Conducteur trop jeune pour ce véhicule`\n- Canonical English: `Driver too young for this vehicle`\n- If new term appears, add row; if already covered, confirm consistency.\n\n## Common Mistakes\n\n- Translating text but forgetting to update the lexicon table.\n- Using UK variants (`driving licence`) instead of US (`driver's license`).\n- Adding duplicate French rows with slightly different wording.\n- Splitting updates across separate commits.\n\n## Red Flags\n\n- \"Just this one translation\"\n- \"Do not touch instruction files\"\n- \"Update the table later\"\n\nIf any red flag appears, enforce the hard gate and surface the conflict.\n",{"name":5,"description":7},"main","b22eca2e974f918ce591c5b2bd829fb7510e0191","Skills\u002Fupdating-business-lexicon",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":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add FDU-INS\u002FInsurance-Skills --skill updating-business-lexicon",{"tool":53,"command":54},"bunx","bunx skills add FDU-INS\u002FInsurance-Skills --skill updating-business-lexicon",{"tool":56,"command":57},"pnpm","pnpm dlx skills add FDU-INS\u002FInsurance-Skills --skill updating-business-lexicon","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fupdating-business-lexicon\u002FSKILL.md",true,[],[62,90,114,145,167,199],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":73,"publishedAt":34},"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",[68],{"categoryNo":69,"categoryName":70,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[64,74,23,75,76,77,28,78,79,30,80,81,82,83,84,85,86,87,88,89],"insurance law","civil","contract","family","review","loyalty","top","contract review","ceo","support","advice","consultation","regulatory","privacy","protection","startup",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":34},"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",[],[97,98,99,100,23,101,102,28,103,104,105,106,107,108,109,110,111,112,27,113],"zocdoc doctor finder","doctor","healthcare","reviews","browser automation","access","browsing","browser","booking","network","therapist","computer","availability","for","provider","tool","automation",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":125,"publishedAt":34},"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",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[126,127,128,129,23,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144],"context","zenmux context","Video","chinese","project","web search","translate","search","open","question","pay","image","you","activate","architecture","logs","streaming","cherry studio","how",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":34},"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",[],[152,153,154,155,156,23,157,158,27,28,159,30,160,161,162,163,164,165,166],"workers","comp","workers comp","workers comp guide","guide","triggers","workers-comp","tasks","claims management","claims","compliance","help","compensation","management","user",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":182,"publishedAt":34},"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",[173,176,179],{"categoryNo":174,"categoryName":175,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":177,"categoryName":178,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":180,"categoryName":181,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000034","行政与办公人员",[183,184,185,186,187,23,188,189,190,26,28,191,192,193,194,195,196,197,27,198],"weekly","weekly kpi report","kpi","report","xlsx","actionable","insights","briefing","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":34},"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":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000040","财务",[209,210,23,211,212,28,139,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"]