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
- rade-nugroho/Agentic-Enteprises-Skillword for word, first seen May 20, 2026
Other versions1 project uses a version of this.
Word for word · 1
- rade-nugroho/Agentic-Enteprises-Skill★ 9100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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.
In this repository197 other files it gives its agents.
- ab-testing-engineerSkill
- actuarial-analystSkill
- actuarial-consultingSkill
- actuarySkill
- advanced-long-term-actuarial-mathematicsSkill
- advanced-persistent-threatSkill
- advanced-short-term-actuarial-mathematicsSkill
- agentic-ai-developerSkill
- ai-adversarial-robustness-engineerSkill
- ai-context-engineerSkill
- ai-engineerSkill
- ai-lead-opsSkill
- ai-memory-developerSkill
- ai-redteamSkill
- ai-researcherSkill
- ai-risk-governanceSkill
- ai-skill-managerSkill
- ai-token-improvement-plan-engineerSkill
- aml-cftSkill
- aml-complianceSkill
- analytics-data-engineering-manager-productSkill
- analytics-data-engineerSkill
- anti-false-positive-decision-makingSkill
- applied-ai-architect-commercial-enterpriseSkill
- appointed-chief-actuarySkill
- asset-liability-managementSkill
- associate-actuarySkill
- auditorSkill
- bcm-disaster-recovery-specialistSkill
- bi-analystSkill
- build-validatorSkill
- business-analystSkill
- business-consultantSkill
- business-model-researcherSkill
- certified-information-systems-security-professionalSkill
- chief-information-security-officerSkill
- ci-cd-engineerSkill
- cicd-engineerSkill
- cisco-certified-network-professionalSkill
- classified-cyber-security-senior-managerSkill
- classified-software-devsecops-engineerSkill
- cloud-architectSkill
- cloud-compliance-specialistSkill
- cloud-economistSkill
- cloud-engineerSkill
- cloud-security-engineerSkill
- cloud-system-administratorSkill
- cluster-deployment-engineerSkill
- code-securitySkill
- commercial-counselSkill
- communication-leadSkill
- community-executive-escalations-program-managerSkill
- compliance-engineerSkill
- compliance-specialistSkill
- compute-accounting-managerSkill
- control-software-developerSkill
- corporate-counselSkill
- country-managerSkill
- cross-department-translationSkill
- cryptographer-specialistSkill
- The first 60 shown.
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
- Distinctive: line 20
Document assumption rationale, sources, and effective dates for governance or audit
- Very specific: line 80
Run or reference experience studies (A/E).
- Distinctive: line 82
Document expert judgment when overriding data
- Distinctive: line 102
Keep grids parsimonious—avoid combinatorial explosion
- Distinctive: line 104
Document correlations or explicit independence assumptions
- Distinctive: line 120
Before models run, confirm:
≈ “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.
Files
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
| Need | Skill |
| Pricing, reserving, triangles, A/E studies, capital overview | actuary |
| Engagement scoping, SOW, due diligence, opinion support | actuarial-consulting |
| P&C lines, claims, cat, reinsurance product context | property-casualty-insurance |
| Life, health, annuity product and benefit context | life-health-insurance |
| DB/DC pensions, funding, demographic tables for plans | pension-retirement-funds |
| Financial statements, variance, non-insurance analytics | financial-analyst (if installed) |
| Executive strategy without assumption governance | business-consultant |
| IFRS 17 measurement presentation (coordinate assumptions) | ifrs |
| Regulatory control implementation and audit evidence | compliance-engineer |
Core Workflows
1. Scope the assumption exercise
- Purpose — Pricing, valuation, capital, ALM, planning, or stress testing
- Model — Name, version, owner; which outputs consume each assumption
- Materiality — Drivers ranked by impact on key metrics (LR, reserves, SCR, surplus)
- Population — In-force, new business, closed block; segment dimensions
- Effective date — Align with valuation date, rate filing, or budget cycle
See references/assumption_setting_scope_and_principles.md.
2. Inventory categories and sources
- List assumptions by category (economic, demographic, behavioral, operational)
- Map each to source (company experience, industry table, vendor, judgment)
- Flag prescribed vs company-specific and jurisdictional constraints
- Note dependencies (e.g., lapse tied to crediting rate; trend tied to inflation)
- Record data period and quality caveats per assumption
See references/assumption_categories_and_sources.md.
3. Select and justify assumptions
- Run or reference experience studies (A/E); coordinate with
actuaryfor technical fitting - Apply credibility blending where data is thin
- Document expert judgment when overriding data
- Set level, trend, and volatility components separately when material
- Compare to benchmarks and prior approved set; explain deltas
See references/selection_methodology_and_judgment.md.
4. Govern, document, and control changes
- Assign owner and approver per assumption or pack tier
- Version the assumption pack (ID, date, model compatibility)
- Maintain change log: prior → proposed → approved, with rationale
- Attach exhibits: A/E tables, sensitivity summary, peer review sign-off
- Archive reproducible data cuts per model risk policy
See references/governance_documentation_and_change_control.md.
5. Sensitivities, scenarios, and stress
- Identify top drivers from materiality or prior sensitivity work
- Define base, adverse, favorable, and regulatory/stress scenarios
- Keep grids parsimonious—avoid combinatorial explosion
- Align scenarios with risk appetite and ORSA/capital narrative (overview)
- Document correlations or explicit independence assumptions
See references/sensitivity_scenarios_and_stress.md.
6. Line-of-business assumption packs
- Select pack template: P&C, life/health, pension, or multi-line
- Pull LOB-specific drivers (e.g., development factors vs mortality improvement)
- Cross-check pack against product and regulatory context skills
- Separate packs for pricing vs reserving vs capital when conventions differ
- Hand off model execution to
actuaryafter 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
| Deliverable | Minimum content |
| Assumption register | ID, name, category, value, unit, source, owner, effective date |
| Assumption paper | Executive summary, changes vs prior, studies cited, approvals |
| Governance memo | Roles, change control, model mapping, retention |
| Sensitivity exhibit | Drivers, shocks, metric impacts, scenario definitions |
| Pack manifest | Files/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
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
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.

