agentleFS
daemon-blockint-techdaemon-blockint-tech/Agentic-Enteprises-Skill/assumption-setting/SKILL.md

assumption-setting

Skill8 starsChanged 6 months agoMITView on GitHub

Guides defining, documenting, and governing actuarial and risk assumptions for insurance and related models—mortality, morbidity, lapse, discount rates, inflation, loss development, expense, cat, credit; categories and sources; selection methodology and judgment; sensitivity and scenarios; governance and change control; pricing vs reserving vs capital packs; audit trail—not legal or accounting sign-off. Use for assumption setting, set assumptions, mortality/lapse/discount rate/ loss development assumption, assumption governance, assumption documentation, assumption review, change assumptions—not full model build (actuary), consulting SOW (actuarial-consulting), LOB education (property-casualty-insurance, life-health-insurance), pensions (pension-retirement-funds), or FP&A without actuarial context (financial-analyst).

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Document assumption rationale, sources, and effective dates for governance or audit

    line 20
  2. Very specific:

    Run or reference experience studies (A/E).

    line 80
  3. Distinctive:

    Document expert judgment when overriding data

    line 82
  4. Distinctive:

    Keep grids parsimonious—avoid combinatorial explosion

    line 102
  5. Distinctive:

    Document correlations or explicit independence assumptions

    line 104
  6. Distinctive:

    Before models run, confirm:

    line 120

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Assumption Setting

When to Use

  • Define or update assumption sets for pricing, reserving, capital, or ALM models
  • Document assumption rationale, sources, and effective dates for governance or audit
  • Classify assumptions by category (economic, demographic, behavioral, operational)
  • Apply selection methodology (experience, industry tables, judgment, blending)
  • Design sensitivity and scenario grids tied to material drivers
  • Establish governance: owners, approval tiers, change control, version history
  • Build assumption packs differentiated by use case (rate indication vs valuation vs ORSA)
  • Reconcile emerging experience vs last-approved assumptions before model runs
  • Benchmark assumptions against industry or regulatory reference points (overview)

When NOT to Use

  • Execute full pricing indications, IBNR triangles, or reserve ultimates as primary deliverable → actuary
  • Scope actuarial consulting engagements, SOW, due diligence, or opinion support governance → actuarial-consulting
  • Teach P&C coverages, FNOL, or underwriting without assumption governance lens → property-casualty-insurance
  • Teach life/health products, benefits, or distribution without assumption pack focus → life-health-insurance
  • Pension funding, ERISA, or retirement plan design → pension-retirement-funds
  • Corporate budgets, investor metrics, or non-insurance FP&A → financial-analyst (if installed)
  • Executive strategy without actuarial/risk assumption workstream → business-consultant
  • Legal interpretation of policy wording, filings, or statutory sign-off → commercial-counsel
  • IFRS note legal wording or general ledger recognition → ifrs
  • SOC 2 / ISO control evidence without actuarial models → compliance-engineer

Related skills

NeedSkill
Pricing, reserving, triangles, A/E studies, capital overviewactuary
Engagement scoping, SOW, due diligence, opinion supportactuarial-consulting
P&C lines, claims, cat, reinsurance product contextproperty-casualty-insurance
Life, health, annuity product and benefit contextlife-health-insurance
DB/DC pensions, funding, demographic tables for planspension-retirement-funds
Financial statements, variance, non-insurance analyticsfinancial-analyst (if installed)
Executive strategy without assumption governancebusiness-consultant
IFRS 17 measurement presentation (coordinate assumptions)ifrs
Regulatory control implementation and audit evidencecompliance-engineer

Core Workflows

1. Scope the assumption exercise

  1. Purpose — Pricing, valuation, capital, ALM, planning, or stress testing
  2. Model — Name, version, owner; which outputs consume each assumption
  3. Materiality — Drivers ranked by impact on key metrics (LR, reserves, SCR, surplus)
  4. Population — In-force, new business, closed block; segment dimensions
  5. Effective date — Align with valuation date, rate filing, or budget cycle

See references/assumption_setting_scope_and_principles.md.

2. Inventory categories and sources

  1. List assumptions by category (economic, demographic, behavioral, operational)
  2. Map each to source (company experience, industry table, vendor, judgment)
  3. Flag prescribed vs company-specific and jurisdictional constraints
  4. Note dependencies (e.g., lapse tied to crediting rate; trend tied to inflation)
  5. Record data period and quality caveats per assumption

See references/assumption_categories_and_sources.md.

3. Select and justify assumptions

  1. Run or reference experience studies (A/E); coordinate with actuary for technical fitting
  2. Apply credibility blending where data is thin
  3. Document expert judgment when overriding data
  4. Set level, trend, and volatility components separately when material
  5. Compare to benchmarks and prior approved set; explain deltas

See references/selection_methodology_and_judgment.md.

4. Govern, document, and control changes

  1. Assign owner and approver per assumption or pack tier
  2. Version the assumption pack (ID, date, model compatibility)
  3. Maintain change log: prior → proposed → approved, with rationale
  4. Attach exhibits: A/E tables, sensitivity summary, peer review sign-off
  5. Archive reproducible data cuts per model risk policy

See references/governance_documentation_and_change_control.md.

5. Sensitivities, scenarios, and stress

  1. Identify top drivers from materiality or prior sensitivity work
  2. Define base, adverse, favorable, and regulatory/stress scenarios
  3. Keep grids parsimonious—avoid combinatorial explosion
  4. Align scenarios with risk appetite and ORSA/capital narrative (overview)
  5. Document correlations or explicit independence assumptions

See references/sensitivity_scenarios_and_stress.md.

6. Line-of-business assumption packs

  1. Select pack template: P&C, life/health, pension, or multi-line
  2. Pull LOB-specific drivers (e.g., development factors vs mortality improvement)
  3. Cross-check pack against product and regulatory context skills
  4. Separate packs for pricing vs reserving vs capital when conventions differ
  5. Hand off model execution to actuary after pack is approved

See references/line_of_business_assumption_packs.md.

Assumption pack checklist

Before models run, confirm:

  • Every material driver has owner, source, and effective date
  • Pricing vs valuation vs capital basis differences documented
  • Changes from prior pack bridged with quantified impact where possible
  • Sensitivities on top 3–5 drivers completed or scheduled
  • Judgment overrides explicitly approved and time-bounded if interim
  • No legal, statutory, or accounting sign-off claimed by the agent

Deliverable standards

DeliverableMinimum content
Assumption registerID, name, category, value, unit, source, owner, effective date
Assumption paperExecutive summary, changes vs prior, studies cited, approvals
Governance memoRoles, change control, model mapping, retention
Sensitivity exhibitDrivers, shocks, metric impacts, scenario definitions
Pack manifestFiles/worksheets, model version, LOB, use case (price/reserve/capital)

State uncertainty and data limitations. Do not present outputs as appointed-actuary, legal, or audit opinions.

When to load references

  • Scope and principles → references/assumption_setting_scope_and_principles.md
  • Categories and sources → references/assumption_categories_and_sources.md
  • Selection and judgment → references/selection_methodology_and_judgment.md
  • Governance and change control → references/governance_documentation_and_change_control.md
  • Sensitivity and stress → references/sensitivity_scenarios_and_stress.md
  • LOB packs → references/line_of_business_assumption_packs.md

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.