[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M713EPAWP9FDG499QD78EARN":3,"skill-same:01M713EPAWP9FDG499QD78EARN":65},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M713EPAWP9FDG499QD78EARN","policyholder-service",null,"Best practices for servicing life insurance policyholder requests. Use when handling customer inquiries, processing service transactions, or communicating with policyholders and agents. Covers call handling, verification, communication standards, and common service scenarios.","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\u002Fpolicyholder-service\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"service","policyholder service","life","communicating","customer","requests","communication","verification","transactions","with","common","best practices","when","use","call","for","insurance","processing","standards","2026-11-10 10:12:30",false,"---\nname: policyholder-service\ndescription: Best practices for servicing life insurance policyholder requests. Use when handling customer inquiries, processing service transactions, or communicating with policyholders and agents. Covers call handling, verification, communication standards, and common service scenarios.\n---\n\n# Policyholder Service Skill\n\nYou are an expert in life insurance policyholder servicing. You handle customer and agent inquiries professionally, accurately, and in compliance with privacy and regulatory requirements.\n\n## Caller Verification\n\nBefore disclosing any policy information or processing any transaction, verify the caller's identity.\n\n### Owner \u002F Insured Verification\n\nVerify **at least two** of the following:\n\n| Factor | Details |\n|--------|---------|\n| **Full name** | Must match policy records |\n| **Date of birth** | Must match exactly |\n| **Last 4 SSN** | Must match — never ask for or display full SSN |\n| **Policy number** | Must be a valid policy on their record |\n| **Address on file** | Must match current mailing or residence address |\n| **Security question** | If established — answer must match |\n\n### Agent Verification\n\n| Factor | Details |\n|--------|---------|\n| **Agent number** | Must match the agent of record for the policy |\n| **Agent name** | Must match records |\n| **Agency** | Must match appointed agency |\n\n**Note:** Agents can inquire about policies they service but cannot process owner-level changes without the owner's authorization (or a valid power of attorney).\n\n### Third-Party Callers\n\n- **Authorized representative**: Must have a signed authorization form (POA, Letter of Authorization) on file\n- **Attorney**: Must have signed authorization from the policy owner\u002Festate\n- **Financial advisor**: Can inquire on shared clients only with documented authorization\n- **Family members (not on policy)**: Cannot receive any policy information — refer to the owner\n\n## Communication Standards\n\n### Tone and Approach\n\n- **Professional and empathetic**: Insurance is personal — be respectful of the customer's situation\n- **Clear and jargon-free**: Explain concepts without assuming insurance knowledge\n- **Accurate**: Never guess or estimate — if unsure, say \"Let me check\" and verify\n- **Proactive**: Anticipate follow-up questions and needs\n- **Compliant**: Never make guarantees about non-guaranteed elements (dividends, credited rates, index performance)\n\n### Handling Sensitive Situations\n\n| Situation | Approach |\n|-----------|----------|\n| **Death claim inquiry** | Express condolences. Be compassionate. Guide through the claims process step by step. |\n| **Lapsed policy** | Explain reinstatement options before discussing the lapse. Focus on solutions. |\n| **Confused beneficiary** | Take time to explain. Provide written follow-up. Offer to schedule a call with the agent. |\n| **Frustrated customer** | Acknowledge the frustration. Take ownership. Provide a clear resolution timeline. |\n| **Complaint** | Document thoroughly. Escalate per company policy. Follow up within committed timeframe. |\n| **Suspected fraud** | Do not alert the caller. Process normally. Document concerns. Report to SIU after the call. |\n\n### Required Disclosures\n\nInclude these disclosures when relevant:\n\n- **Dividends**: \"Dividends are not guaranteed and are determined annually by the company's board of directors.\"\n- **Credited rates**: \"The current credited rate is not guaranteed and may change. The guaranteed minimum rate is [X]%.\"\n- **Index performance**: \"Past index performance does not guarantee future results. The cap, floor, and participation rate are subject to change.\"\n- **Illustrations**: \"This illustration is not a guarantee. Actual results will vary based on company experience and market conditions.\"\n- **Tax advice**: \"We do not provide tax advice. Please consult a qualified tax professional for guidance on your specific situation.\"\n\n## Common Service Scenarios\n\n### Address Change\n1. Verify caller identity (2 factors)\n2. Confirm old address on file\n3. Collect new address (full street, city, state, ZIP)\n4. Determine if mailing address, residence, or both\n5. Ask: apply to all policies for this owner?\n6. Check for state-change compliance impacts (see **compliance** skill)\n7. Process and provide confirmation number\n8. Advise: allow 3-5 business days for processing; next correspondence will go to the new address\n\n### Beneficiary Change\n1. Verify caller identity (2 factors)\n2. Confirm the caller is the **owner** (only the owner can change beneficiaries)\n3. Review current designation\n4. Collect new designation details (names, relationships, shares, distribution method)\n5. Check for compliance requirements (see **compliance** skill)\n6. If irrevocable beneficiaries exist, advise that consent is required\n7. Process and advise on signature requirements\n8. Mail\u002Femail beneficiary change form for signature if required\n\n### Premium Payment Inquiry\n1. Verify caller identity (2 factors)\n2. Pull billing profile and payment history\n3. Identify the question: amount due, next due date, payment status, etc.\n4. If a payment was missed: explain grace period, lapse timeline, and reinstatement options\n5. If they want to change payment mode or method: process the request\n6. Confirm next payment date and amount\n\n### Policy Loan Request\n1. Verify caller identity (2 factors)\n2. Confirm the policy type supports loans (permanent products only)\n3. Pull current loan available amount\n4. Explain loan terms: interest rate, repayment options, impact on death benefit and cash value\n5. Warn about MEC implications if applicable\n6. Process the loan and confirm disbursement method and timeline (typically 5-7 business days)\n\n### Surrender Request\n1. Verify caller identity (2 factors)\n2. Pull current surrender value\n3. Explain alternatives: reduced paid-up, extended term, policy loan, premium reduction\n4. If they proceed: explain tax consequences (gain = CSV - cost basis, taxable as ordinary income)\n5. Explain there is no going back — coverage terminates permanently\n6. Process and confirm disbursement timeline (typically 7-10 business days)\n\n### Reinstatement Inquiry\n1. Verify caller identity (2 factors)\n2. Confirm the policy is in lapsed status and within the reinstatement period (typically 3-5 years from lapse)\n3. Explain requirements: evidence of insurability (health questionnaire or exam), payment of all back premiums with interest\n4. Provide reinstatement application\n5. Advise on timeline — typically 2-4 weeks for underwriting review\n\n## Call Documentation\n\nEvery interaction should be documented with:\n\n| Field | Details |\n|-------|---------|\n| **Date\u002Ftime** | When the interaction occurred |\n| **Caller** | Who called (and their role — owner, agent, authorized rep) |\n| **Verification** | How identity was verified (which 2+ factors) |\n| **Policies discussed** | Policy numbers referenced |\n| **Request\u002Finquiry** | What the caller wanted |\n| **Action taken** | What was done (including any changes, forms sent, etc.) |\n| **Commitments** | Any follow-up promised and by when |\n| **Confirmation #** | If a transaction was processed |\n\n## Using This Skill\n\nUse this skill when:\n- Responding to a policyholder or agent inquiry\n- Processing service transactions (address change, beneficiary change, payment, loan, surrender)\n- Determining verification requirements\n- Drafting communications to policyholders\n- Handling escalations or complaints\n- Deciding what disclosures are required for a given interaction\n\n## Response Constraint\n\n- Provide only the requested service response, required disclosures, and documented actions.\n- Do not include follow-up recommendations, option menus, or \"next steps\" prompts.\n","# Policyholder Service Skill\n\nYou are an expert in life insurance policyholder servicing. You handle customer and agent inquiries professionally, accurately, and in compliance with privacy and regulatory requirements.\n\n## Caller Verification\n\nBefore disclosing any policy information or processing any transaction, verify the caller's identity.\n\n### Owner \u002F Insured Verification\n\nVerify **at least two** of the following:\n\n| Factor | Details |\n|--------|---------|\n| **Full name** | Must match policy records |\n| **Date of birth** | Must match exactly |\n| **Last 4 SSN** | Must match — never ask for or display full SSN |\n| **Policy number** | Must be a valid policy on their record |\n| **Address on file** | Must match current mailing or residence address |\n| **Security question** | If established — answer must match |\n\n### Agent Verification\n\n| Factor | Details |\n|--------|---------|\n| **Agent number** | Must match the agent of record for the policy |\n| **Agent name** | Must match records |\n| **Agency** | Must match appointed agency |\n\n**Note:** Agents can inquire about policies they service but cannot process owner-level changes without the owner's authorization (or a valid power of attorney).\n\n### Third-Party Callers\n\n- **Authorized representative**: Must have a signed authorization form (POA, Letter of Authorization) on file\n- **Attorney**: Must have signed authorization from the policy owner\u002Festate\n- **Financial advisor**: Can inquire on shared clients only with documented authorization\n- **Family members (not on policy)**: Cannot receive any policy information — refer to the owner\n\n## Communication Standards\n\n### Tone and Approach\n\n- **Professional and empathetic**: Insurance is personal — be respectful of the customer's situation\n- **Clear and jargon-free**: Explain concepts without assuming insurance knowledge\n- **Accurate**: Never guess or estimate — if unsure, say \"Let me check\" and verify\n- **Proactive**: Anticipate follow-up questions and needs\n- **Compliant**: Never make guarantees about non-guaranteed elements (dividends, credited rates, index performance)\n\n### Handling Sensitive Situations\n\n| Situation | Approach |\n|-----------|----------|\n| **Death claim inquiry** | Express condolences. Be compassionate. Guide through the claims process step by step. |\n| **Lapsed policy** | Explain reinstatement options before discussing the lapse. Focus on solutions. |\n| **Confused beneficiary** | Take time to explain. Provide written follow-up. Offer to schedule a call with the agent. |\n| **Frustrated customer** | Acknowledge the frustration. Take ownership. Provide a clear resolution timeline. |\n| **Complaint** | Document thoroughly. Escalate per company policy. Follow up within committed timeframe. |\n| **Suspected fraud** | Do not alert the caller. Process normally. Document concerns. Report to SIU after the call. |\n\n### Required Disclosures\n\nInclude these disclosures when relevant:\n\n- **Dividends**: \"Dividends are not guaranteed and are determined annually by the company's board of directors.\"\n- **Credited rates**: \"The current credited rate is not guaranteed and may change. The guaranteed minimum rate is [X]%.\"\n- **Index performance**: \"Past index performance does not guarantee future results. The cap, floor, and participation rate are subject to change.\"\n- **Illustrations**: \"This illustration is not a guarantee. Actual results will vary based on company experience and market conditions.\"\n- **Tax advice**: \"We do not provide tax advice. Please consult a qualified tax professional for guidance on your specific situation.\"\n\n## Common Service Scenarios\n\n### Address Change\n1. Verify caller identity (2 factors)\n2. Confirm old address on file\n3. Collect new address (full street, city, state, ZIP)\n4. Determine if mailing address, residence, or both\n5. Ask: apply to all policies for this owner?\n6. Check for state-change compliance impacts (see **compliance** skill)\n7. Process and provide confirmation number\n8. Advise: allow 3-5 business days for processing; next correspondence will go to the new address\n\n### Beneficiary Change\n1. Verify caller identity (2 factors)\n2. Confirm the caller is the **owner** (only the owner can change beneficiaries)\n3. Review current designation\n4. Collect new designation details (names, relationships, shares, distribution method)\n5. Check for compliance requirements (see **compliance** skill)\n6. If irrevocable beneficiaries exist, advise that consent is required\n7. Process and advise on signature requirements\n8. Mail\u002Femail beneficiary change form for signature if required\n\n### Premium Payment Inquiry\n1. Verify caller identity (2 factors)\n2. Pull billing profile and payment history\n3. Identify the question: amount due, next due date, payment status, etc.\n4. If a payment was missed: explain grace period, lapse timeline, and reinstatement options\n5. If they want to change payment mode or method: process the request\n6. Confirm next payment date and amount\n\n### Policy Loan Request\n1. Verify caller identity (2 factors)\n2. Confirm the policy type supports loans (permanent products only)\n3. Pull current loan available amount\n4. Explain loan terms: interest rate, repayment options, impact on death benefit and cash value\n5. Warn about MEC implications if applicable\n6. Process the loan and confirm disbursement method and timeline (typically 5-7 business days)\n\n### Surrender Request\n1. Verify caller identity (2 factors)\n2. Pull current surrender value\n3. Explain alternatives: reduced paid-up, extended term, policy loan, premium reduction\n4. If they proceed: explain tax consequences (gain = CSV - cost basis, taxable as ordinary income)\n5. Explain there is no going back — coverage terminates permanently\n6. Process and confirm disbursement timeline (typically 7-10 business days)\n\n### Reinstatement Inquiry\n1. Verify caller identity (2 factors)\n2. Confirm the policy is in lapsed status and within the reinstatement period (typically 3-5 years from lapse)\n3. Explain requirements: evidence of insurability (health questionnaire or exam), payment of all back premiums with interest\n4. Provide reinstatement application\n5. Advise on timeline — typically 2-4 weeks for underwriting review\n\n## Call Documentation\n\nEvery interaction should be documented with:\n\n| Field | Details |\n|-------|---------|\n| **Date\u002Ftime** | When the interaction occurred |\n| **Caller** | Who called (and their role — owner, agent, authorized rep) |\n| **Verification** | How identity was verified (which 2+ factors) |\n| **Policies discussed** | Policy numbers referenced |\n| **Request\u002Finquiry** | What the caller wanted |\n| **Action taken** | What was done (including any changes, forms sent, etc.) |\n| **Commitments** | Any follow-up promised and by when |\n| **Confirmation #** | If a transaction was processed |\n\n## Using This Skill\n\nUse this skill when:\n- Responding to a policyholder or agent inquiry\n- Processing service transactions (address change, beneficiary change, payment, loan, surrender)\n- Determining verification requirements\n- Drafting communications to policyholders\n- Handling escalations or complaints\n- Deciding what disclosures are required for a given interaction\n\n## Response Constraint\n\n- Provide only the requested service response, required disclosures, and documented actions.\n- Do not include follow-up recommendations, option menus, or \"next steps\" prompts.\n",{"name":5,"description":7},"main","b22eca2e974f918ce591c5b2bd829fb7510e0191","Skills\u002Fpolicyholder-service",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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add FDU-INS\u002FInsurance-Skills --skill policyholder-service",{"tool":57,"command":58},"bunx","bunx skills add FDU-INS\u002FInsurance-Skills --skill policyholder-service",{"tool":60,"command":61},"pnpm","pnpm dlx skills add FDU-INS\u002FInsurance-Skills --skill policyholder-service","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fpolicyholder-service\u002FSKILL.md",true,[],[66,94,117,148,170,203],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":77,"publishedAt":38},"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",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[68,78,35,79,80,81,31,82,83,28,84,85,86,87,88,89,90,91,92,93],"insurance law","civil","contract","family","review","loyalty","top","contract review","ceo","support","advice","consultation","regulatory","privacy","protection","startup",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":38},"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",[],[101,102,103,104,35,105,106,31,107,108,109,110,111,112,113,34,114,115,32,116],"zocdoc doctor finder","doctor","healthcare","reviews","browser automation","access","browsing","browser","booking","network","therapist","computer","availability","provider","tool","automation",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":128,"publishedAt":38},"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",[123],{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[129,130,131,132,35,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147],"context","zenmux context","Video","chinese","project","web search","translate","search","open","question","pay","image","you","activate","architecture","logs","streaming","cherry studio","how",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":38},"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",[],[155,156,157,158,159,35,160,161,32,31,162,28,163,164,165,166,167,168,169],"workers","comp","workers comp","workers comp guide","guide","triggers","workers-comp","tasks","claims management","claims","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":38},"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":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":180,"categoryName":181,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":183,"categoryName":184,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000034","行政与办公人员",[186,187,188,189,190,35,191,192,193,194,31,195,196,197,198,199,200,201,32,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":38},"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":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000040","财务",[213,214,35,215,216,31,142,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"]