agentleFS
accolveraccolver/annuity-life-insurance-sales-skill/skills/annuity-life-insurance-sales/SKILL.md

annuity-life-insurance-sales

Skill0 starsChanged 6 months agoMITView on GitHub

Guides licensed insurance agents and financial professionals through compliant annuity and life-insurance sales workflows. Use when creating discovery questions, suitability framing, retirement-income analysis, product-positioning language, objection handling, meeting prep, client follow-up, policy review, or servicing guidance for annuities, life insurance, QLACs, retirement income, guaranteed income, or protection planning.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. accolver/skill-maker★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 12 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not recommend carrier-specific products, rates, riders, replacements, illustrations, underwriting outcomes, or tax/legal strategies as …

    line 20
  2. Distinctive:

    Do not present annuities or life insurance as universally appropriate.

    line 21
  3. Distinctive:

    Document suitability rationale, liquidity needs, fees, surrender charges, limitations, replacement considerations, and required disclosures.

    line 22
  4. Distinctive:

    Use compliant language: say "may help," "can be considered," and "subject to suitability, carrier approval, and required disclosures."

    line 23
  5. Distinctive:

    Use the Paychecks and Playchecks framework when relevant:

    line 28
  6. Distinctive:

    QLAC: consider mentioning for clients with significant qualified assets who want longevity protection and may benefit from deferring a …

    line 38
  7. Distinctive:

    Do not jump to a product recommendation without facts.

    line 47
  8. Distinctive:

    Ask about ages, health, goals, income sources, assets, liabilities, expenses, liquidity, risk tolerance, tax concerns, beneficiaries, …

    line 48
  9. Very specific:

    Use references/fact-finding-questions.md when a full question bank is needed.

    line 49
  10. Distinctive:

    Document client goals, needs, financial profile, liquidity, time horizon, risk tolerance, tax context, and why the proposed strategy fits.

    line 58
  11. Very specific:

    Use references/compliance-checklist.md before producing final recommendations or client-facing language.

    line 59
  12. Very specific:

    Use references/product-positioning.md for a concise category guide.

    line 68
  13. Distinctive:

    Never pressure. Make suitability and client understanding the close.

    line 72
  14. Very specific:

    Use references/objection-handling.md for examples.

    line 73
  15. Distinctive:

    Keep client-facing outputs plain-English, balanced, and disclosure-aware.

    line 76
  16. Distinctive:

    Use this structure unless the user requests another format:

    line 81

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Annuity & Life Insurance Sales Enablement

Purpose

This skill helps licensed insurance agents and financial professionals prepare compliant sales conversations and deliverables for annuities and life insurance. It is an enablement tool for professionals, not consumer-facing financial, tax, legal, fiduciary, investment, or securities advice.

Non-negotiable guardrails

  • Assume the user is a licensed professional unless they state otherwise; if not licensed, provide education only and recommend working with licensed professionals.
  • Do not recommend carrier-specific products, rates, riders, replacements, illustrations, underwriting outcomes, or tax/legal strategies as definitive advice.
  • Do not present annuities or life insurance as universally appropriate.
  • Document suitability rationale, liquidity needs, fees, surrender charges, limitations, replacement considerations, and required disclosures.
  • Use compliant language: say "may help," "can be considered," and "subject to suitability, carrier approval, and required disclosures."
  • Encourage review with the client’s CPA, attorney, investment adviser, or compliance department when tax, legal, securities, fiduciary, or replacement issues arise.

Core retirement-income framing

Use the Paychecks and Playchecks framework when relevant:

  • Paychecks: guaranteed income sources covering essential expenses, such as Social Security, pensions, and suitable lifetime-income annuities.
  • Playchecks: remaining assets for discretionary spending, growth, legacy, inflation flexibility, emergencies, and lifestyle goals.

Reference these concepts only when useful and explain them plainly:

  • Mortality credits: risk-pooling economics that can make lifetime annuity income more efficient than self-managed withdrawals for some retirees.
  • Retirement Alpha: potential portfolio benefit from allocating part of retirement assets to guaranteed income, which can reduce sequence-risk pressure and improve spending confidence.
  • Happy Factor: retirees with dependable income may feel more confident and less anxious.
  • QLAC: consider mentioning for clients with significant qualified assets who want longevity protection and may benefit from deferring a portion of RMD exposure; verify current IRS limits and rules before use.

Workflow

  1. Classify the task
    • Prospecting, discovery, suitability analysis, product-positioning, objection handling, presentation prep, follow-up, policy review, or servicing.
    • Identify whether the deliverable is for agent coaching, internal notes, or client-facing language.
  2. Collect facts before products
    • Do not jump to a product recommendation without facts.
    • Ask about ages, health, goals, income sources, assets, liabilities, expenses, liquidity, risk tolerance, tax concerns, beneficiaries, existing coverage, decision makers, and outside influencers.
    • Use references/fact-finding-questions.md when a full question bank is needed.
  3. Run income-gap logic
    • Essential monthly expenses minus guaranteed income sources equals the paycheck gap.
    • Guaranteed income sources include Social Security, pensions, existing guaranteed annuity income, and other dependable income.
    • Separate assets needed for paychecks from assets left for playchecks.
    • Preserve emergency liquidity and avoid over-concentration in illiquid contracts.
  4. Assess suitability
    • Document client goals, needs, financial profile, liquidity, time horizon, risk tolerance, tax context, and why the proposed strategy fits.
    • Use references/compliance-checklist.md before producing final recommendations or client-facing language.
  5. Map needs to product categories
    • Income now: SPIA may be considered.
    • Income later: DIA, QLAC, or annuity with income features may be considered.
    • Principal protection with upside potential: FIA may be considered.
    • Guaranteed fixed rate: MYGA may be considered.
    • Death benefit protection: term, whole life, universal life, or indexed universal life may be considered depending on need, budget, and suitability.
    • Long-term-care concern: hybrid life/LTC or annuity/LTC features may be considered.
    • Use references/product-positioning.md for a concise category guide.
  6. Handle objections consultatively
    • Validate the concern, clarify the source, answer with facts, disclose tradeoffs, and return to the client’s goals.
    • Never pressure. Make suitability and client understanding the close.
    • Use references/objection-handling.md for examples.
  7. Produce the deliverable
    • Keep client-facing outputs plain-English, balanced, and disclosure-aware.
    • Include assumptions, missing facts, compliance caveats, and next steps.

Output format

Use this structure unless the user requests another format:

  1. Summary — task, scope, and main conclusion.
  2. Decision / Approach — classification, assumptions, and selected path.
  3. Artifacts — scripts, talk tracks, outlines, discovery questions, emails, checklists, or meeting notes.
  4. Validation — suitability/compliance checks, caveats, missing data, and risks.
  5. Next steps — concrete follow-up actions.

Common mistakes to avoid

  • Recommending a product before discovery.
  • Treating tax, legal, securities, or fiduciary issues as settled facts.
  • Ignoring liquidity, surrender periods, fees, replacement concerns, or client alternatives.
  • Using fear-based or absolute claims like "risk-free," "best," "guaranteed market upside," or "no downside" without precise disclosure.
  • Failing to distinguish agent coaching from client-facing language.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.