[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XFP9JV3ERT4Q8M4K147E73":3,"skill-same:01M6XFP9JV3ERT4Q8M4K147E73":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},"01M6XFP9JV3ERT4Q8M4K147E73","compliance",null,"Regulatory compliance guidelines for life insurance policy administration transactions. Use when processing address changes (state-change impacts), beneficiary changes (community property, ERISA, minors), or any transaction that may trigger compliance review. Covers NAIC model regulations, state-specific rules, OFAC screening, and suitability requirements.","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\u002Fcompliance\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"community","insurance","when","for","administration","compliance review","processing","trigger","requirements","transaction","review","use","Rules","model","transactions","state","guidelines","change","policy","2026-11-10 10:12:30",false,"---\nname: compliance\ndescription: Regulatory compliance guidelines for life insurance policy administration transactions. Use when processing address changes (state-change impacts), beneficiary changes (community property, ERISA, minors), or any transaction that may trigger compliance review. Covers NAIC model regulations, state-specific rules, OFAC screening, and suitability requirements.\n---\n\n# Compliance Skill\n\nYou are an expert in life insurance regulatory compliance. You ensure that every policy administration transaction is processed in accordance with federal and state regulations, company policy, and industry best practices.\n\n> **Disclaimer:** This skill provides general compliance guidance for demonstration purposes. Always consult your company's compliance department and legal counsel for binding regulatory advice.\n\n## Address Change Compliance\n\n### State Change Impact Assessment\n\nWhen a policyholder moves to a new state, assess the following:\n\n| Impact Area | What to Check | Action Required |\n|-------------|---------------|-----------------|\n| **Premium tax** | Each state imposes different premium tax rates (typically 1.5%–4%) | Recalculate premium tax allocation; notify tax\u002Faccounting |\n| **Policy form approval** | Product must be approved in the new state of residence | Verify product filing in new state; if not approved, flag for review |\n| **Agent licensing** | Servicing agent must be licensed in the new state | Verify agent license; if not licensed, may need to reassign |\n| **Free look period** | Some states may trigger a new free look period on certain transactions | Check state-specific free look rules |\n| **Replacement regulations** | Moving states does not trigger replacement, but note for any future transactions | Document for future reference |\n| **State guaranty association** | Coverage limits and associations differ by state | Note new state's guaranty association coverage limits |\n\n### States Requiring Special Attention\n\n| State | Special Considerations |\n|-------|----------------------|\n| **New York** | Strictest insurance regulation — many products not available; additional disclosure requirements |\n| **California** | Community property state — spousal consent requirements for certain transactions |\n| **Texas** | Community property state; unique annuity and life insurance exemptions from creditors |\n| **Florida** | No state income tax — impacts tax planning advice; strong creditor protections for life insurance |\n| **Connecticut** | State-mandated benefit requirements may differ from original issue state |\n\n### Community Property States\n\nThe following states have community property laws that may affect beneficiary changes and policy ownership:\n\nArizona, California, Idaho, Louisiana, Nevada, New Mexico, Texas, Washington, Wisconsin\n\n**Impact:** If the policy was purchased with community funds, the non-owner spouse may have a legal interest in the policy. Removing the spouse as beneficiary or changing ownership may require spousal consent.\n\n### OFAC Screening\n\nAll address changes must be screened against:\n- OFAC Specially Designated Nationals (SDN) list\n- Sanctioned countries and regions\n- State Department embargo lists\n\n**Process:**\n1. Screen new address against sanctioned locations\n2. Re-screen customer name against current SDN list\n3. Flag any partial matches for compliance review\n4. Do not process the transaction until screening is clear\n\n### Suspicious Activity Indicators\n\nFlag the following for compliance review:\n- Address changed more than 2 times in 12 months\n- Address changed to a PO Box after previously having a residence address (without explanation)\n- Address changed to a foreign country\n- Address changed immediately before or after a large transaction (loan, surrender, beneficiary change)\n- Address does not match any known property records\n\n## Beneficiary Change Compliance\n\n### Minors as Beneficiaries\n\nIf a named beneficiary is under age 18:\n\n- **State requirement** that a custodial arrangement under UTMA\u002FUGMA or a trust is typically required\n- **Advise** that insurance companies generally cannot pay death benefits directly to a minor\n- **Note** that courts may appoint a guardian to manage the funds, which can be costly and time-consuming\n- **Suggest** language like: \"To [Custodian Name], as custodian for [Minor Name] under the [State] Uniform Transfers to Minors Act\"\n\n### Estate as Beneficiary\n\nIf \"my estate\" or \"estate of the insured\" is named:\n\n- **Advise** that this subjects life insurance proceeds to:\n  - Probate (delays, costs, public record)\n  - Potential creditor claims against the estate\n  - Possible estate tax inclusion beyond the death benefit\n- **Confirm** this is intentional and document the acknowledgment\n- **Recommend** naming a trust or specific individuals instead\n\n### ERISA Considerations\n\nIf the policy is employer-owned or part of an employee benefit plan:\n\n- ERISA preempts state law for beneficiary designations\n- Spousal consent requirements differ (ERISA plans require spousal waiver for non-spouse beneficiaries)\n- Plan document governs over beneficiary form in case of conflict\n- Check with plan administrator before processing changes\n\n### Irrevocable Beneficiary Rules\n\nIf the current designation is **irrevocable**:\n\n- All currently named irrevocable beneficiaries must consent to any change\n- May require notarized consent forms\n- Court order may be needed if a beneficiary is deceased, incapacitated, or cannot be located\n- Company legal department should review before processing\n- Check if the policy is owned by an ILIT — the trustee's authority is defined by the trust document\n\n### Divorce and Beneficiary Changes\n\n- An ex-spouse's rights depend on the **state** and the **divorce decree**\n- Some states have automatic revocation of ex-spouse as beneficiary upon divorce\n- Other states require an affirmative change\n- Always recommend the client review beneficiary designations after any divorce\n- Document whether the current designation was made before or after the divorce\n\n## Transaction Compliance — General\n\n### Suitability Requirements\n\nFor any transaction that changes the nature of coverage:\n\n| Transaction | Suitability Check Required |\n|------------|---------------------------|\n| Policy replacement | Yes — full replacement form per state |\n| Conversion (term to permanent) | Yes — new product suitability |\n| Rider addition\u002Fremoval | Case by case — may affect total coverage |\n| Face amount increase | Yes — new underwriting and suitability |\n| Face amount decrease | Minimal — confirm understanding of reduced benefit |\n| Surrender | Yes — confirm alternatives explored, tax implications understood |\n| Policy loan | Minimal — confirm understanding of loan terms |\n\n### Record Retention\n\nAll transaction documentation must be retained:\n- **Policy changes**: 7 years from transaction date or life of policy, whichever is longer\n- **Correspondence**: 7 years from date of correspondence\n- **Compliance reviews**: Permanent\n\n### Anti-Money Laundering (AML)\n\nFlag transactions for AML review when:\n- Single premium exceeds $10,000 in cash\n- Structured payments that appear designed to avoid reporting thresholds\n- Frequent changes to ownership or beneficiary without clear reason\n- Customer from high-risk jurisdiction\n- Third-party payor with no insurable interest\n\n## Using This Skill\n\nWhen processing any policy administration transaction:\n\n1. **Before processing**: Check this skill for applicable compliance requirements\n2. **Flag any issues**: Note compliance concerns in the transaction output\n3. **State required actions**: List required forms, disclosures, or reviews\n4. **Document**: Include compliance notes in every confirmation\n5. **When in doubt**: Recommend the transaction be reviewed by compliance before processing\n","# Compliance Skill\n\nYou are an expert in life insurance regulatory compliance. You ensure that every policy administration transaction is processed in accordance with federal and state regulations, company policy, and industry best practices.\n\n> **Disclaimer:** This skill provides general compliance guidance for demonstration purposes. Always consult your company's compliance department and legal counsel for binding regulatory advice.\n\n## Address Change Compliance\n\n### State Change Impact Assessment\n\nWhen a policyholder moves to a new state, assess the following:\n\n| Impact Area | What to Check | Action Required |\n|-------------|---------------|-----------------|\n| **Premium tax** | Each state imposes different premium tax rates (typically 1.5%–4%) | Recalculate premium tax allocation; notify tax\u002Faccounting |\n| **Policy form approval** | Product must be approved in the new state of residence | Verify product filing in new state; if not approved, flag for review |\n| **Agent licensing** | Servicing agent must be licensed in the new state | Verify agent license; if not licensed, may need to reassign |\n| **Free look period** | Some states may trigger a new free look period on certain transactions | Check state-specific free look rules |\n| **Replacement regulations** | Moving states does not trigger replacement, but note for any future transactions | Document for future reference |\n| **State guaranty association** | Coverage limits and associations differ by state | Note new state's guaranty association coverage limits |\n\n### States Requiring Special Attention\n\n| State | Special Considerations |\n|-------|----------------------|\n| **New York** | Strictest insurance regulation — many products not available; additional disclosure requirements |\n| **California** | Community property state — spousal consent requirements for certain transactions |\n| **Texas** | Community property state; unique annuity and life insurance exemptions from creditors |\n| **Florida** | No state income tax — impacts tax planning advice; strong creditor protections for life insurance |\n| **Connecticut** | State-mandated benefit requirements may differ from original issue state |\n\n### Community Property States\n\nThe following states have community property laws that may affect beneficiary changes and policy ownership:\n\nArizona, California, Idaho, Louisiana, Nevada, New Mexico, Texas, Washington, Wisconsin\n\n**Impact:** If the policy was purchased with community funds, the non-owner spouse may have a legal interest in the policy. Removing the spouse as beneficiary or changing ownership may require spousal consent.\n\n### OFAC Screening\n\nAll address changes must be screened against:\n- OFAC Specially Designated Nationals (SDN) list\n- Sanctioned countries and regions\n- State Department embargo lists\n\n**Process:**\n1. Screen new address against sanctioned locations\n2. Re-screen customer name against current SDN list\n3. Flag any partial matches for compliance review\n4. Do not process the transaction until screening is clear\n\n### Suspicious Activity Indicators\n\nFlag the following for compliance review:\n- Address changed more than 2 times in 12 months\n- Address changed to a PO Box after previously having a residence address (without explanation)\n- Address changed to a foreign country\n- Address changed immediately before or after a large transaction (loan, surrender, beneficiary change)\n- Address does not match any known property records\n\n## Beneficiary Change Compliance\n\n### Minors as Beneficiaries\n\nIf a named beneficiary is under age 18:\n\n- **State requirement** that a custodial arrangement under UTMA\u002FUGMA or a trust is typically required\n- **Advise** that insurance companies generally cannot pay death benefits directly to a minor\n- **Note** that courts may appoint a guardian to manage the funds, which can be costly and time-consuming\n- **Suggest** language like: \"To [Custodian Name], as custodian for [Minor Name] under the [State] Uniform Transfers to Minors Act\"\n\n### Estate as Beneficiary\n\nIf \"my estate\" or \"estate of the insured\" is named:\n\n- **Advise** that this subjects life insurance proceeds to:\n  - Probate (delays, costs, public record)\n  - Potential creditor claims against the estate\n  - Possible estate tax inclusion beyond the death benefit\n- **Confirm** this is intentional and document the acknowledgment\n- **Recommend** naming a trust or specific individuals instead\n\n### ERISA Considerations\n\nIf the policy is employer-owned or part of an employee benefit plan:\n\n- ERISA preempts state law for beneficiary designations\n- Spousal consent requirements differ (ERISA plans require spousal waiver for non-spouse beneficiaries)\n- Plan document governs over beneficiary form in case of conflict\n- Check with plan administrator before processing changes\n\n### Irrevocable Beneficiary Rules\n\nIf the current designation is **irrevocable**:\n\n- All currently named irrevocable beneficiaries must consent to any change\n- May require notarized consent forms\n- Court order may be needed if a beneficiary is deceased, incapacitated, or cannot be located\n- Company legal department should review before processing\n- Check if the policy is owned by an ILIT — the trustee's authority is defined by the trust document\n\n### Divorce and Beneficiary Changes\n\n- An ex-spouse's rights depend on the **state** and the **divorce decree**\n- Some states have automatic revocation of ex-spouse as beneficiary upon divorce\n- Other states require an affirmative change\n- Always recommend the client review beneficiary designations after any divorce\n- Document whether the current designation was made before or after the divorce\n\n## Transaction Compliance — General\n\n### Suitability Requirements\n\nFor any transaction that changes the nature of coverage:\n\n| Transaction | Suitability Check Required |\n|------------|---------------------------|\n| Policy replacement | Yes — full replacement form per state |\n| Conversion (term to permanent) | Yes — new product suitability |\n| Rider addition\u002Fremoval | Case by case — may affect total coverage |\n| Face amount increase | Yes — new underwriting and suitability |\n| Face amount decrease | Minimal — confirm understanding of reduced benefit |\n| Surrender | Yes — confirm alternatives explored, tax implications understood |\n| Policy loan | Minimal — confirm understanding of loan terms |\n\n### Record Retention\n\nAll transaction documentation must be retained:\n- **Policy changes**: 7 years from transaction date or life of policy, whichever is longer\n- **Correspondence**: 7 years from date of correspondence\n- **Compliance reviews**: Permanent\n\n### Anti-Money Laundering (AML)\n\nFlag transactions for AML review when:\n- Single premium exceeds $10,000 in cash\n- Structured payments that appear designed to avoid reporting thresholds\n- Frequent changes to ownership or beneficiary without clear reason\n- Customer from high-risk jurisdiction\n- Third-party payor with no insurable interest\n\n## Using This Skill\n\nWhen processing any policy administration transaction:\n\n1. **Before processing**: Check this skill for applicable compliance requirements\n2. **Flag any issues**: Note compliance concerns in the transaction output\n3. **State required actions**: List required forms, disclosures, or reviews\n4. **Document**: Include compliance notes in every confirmation\n5. **When in doubt**: Recommend the transaction be reviewed by compliance before processing\n",{"name":5,"description":7},"main","b22eca2e974f918ce591c5b2bd829fb7510e0191","Skills\u002Fcompliance",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 compliance",{"tool":62,"command":63},"bunx","bunx skills add FDU-INS\u002FInsurance-Skills --skill compliance",{"tool":65,"command":66},"pnpm","pnpm dlx skills add FDU-INS\u002FInsurance-Skills --skill compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fcompliance\u002FSKILL.md",true,[],[71,95,118,149,170,203],{"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,25,80,81,82,26,34,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":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",[],[102,103,104,105,25,106,107,26,108,109,110,111,112,113,114,27,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":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",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[130,131,132,133,25,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":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",[],[156,157,158,159,160,25,161,162,35,26,163,84,164,165,5,166,167,168,169],"workers","comp","workers comp","workers comp guide","guide","triggers","workers-comp","tasks","claims management","claims","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":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",[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":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员",[186,187,188,189,190,25,191,192,193,194,26,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":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",[209],{"categoryNo":210,"categoryName":211,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000040","财务",[213,214,25,215,216,26,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"]