actuarial-consulting
Skill9 starsChanged 6 months agoMITView on GitHub
Guides actuarial consulting engagements—client scoping and SOW design, stakeholder communication (CFO, risk, boards, regulators at overview level), due diligence and M&A actuarial support, reserving/pricing/capital review programs, model validation and opinion support, regulatory interaction prep, and deliverable governance (memos, exhibits, management presentations). Use when the user mentions actuarial consulting, actuarial engagement, reserve opinion, due diligence actuarial, model validation engagement, actuarial memo, SOW actuarial, regulatory actuarial, M&A reserves, or actuarial review—not deep technical modeling execution (actuary), P&C line education only (property-casualty-insurance), legal advice (commercial-counsel), or generic management consulting without actuarial lens (business-consultant).
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Run project governance: timeline, quality review, documentation, and sign-off chain
- Distinctive: line 58
Document independence constraints (prior work, management roles, advocacy vs advisory)
- Distinctive: line 99
Document findings severity, remediation, and re-test criteria
- Distinctive: line 140
When multiple types apply (e.g., M&A plus validation), split workstreams in the SOW with separate timelines and reviewers.
- Distinctive: line 144
Before any client-facing draft:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Actuarial Consulting
When to Use
- Frame a new actuarial consulting engagement (objectives, boundaries, independence)
- Draft or review SOW, fees, data access, and deliverable list for actuarial work
- Plan stakeholder communications (CFO, CRO, board, audit committee, regulators—overview)
- Support M&A, divestiture, or reinsurance due diligence on reserves, pricing, and capital
- Structure reserve opinion, pricing review, or capital assessment engagements (not sole modeler)
- Scope model validation, peer review, or opinion-support workpapers
- Prepare regulatory meeting materials (talking points, exhibit index—not legal filings)
- Design deliverable packages: actuarial memo, exhibits, management presentation, Q&A log
- Run project governance: timeline, quality review, documentation, and sign-off chain
When NOT to Use
- Execute pricing triangles, IBNR development, or assumption fitting as primary deliverable →
actuary - Teach P&C coverages, claims handling, or underwriting mechanics without engagement lens →
property-casualty-insurance - Interpret contracts, policy wording, or provide legal/regulatory enforcement advice →
commercial-counsel - Corporate FP&A, budgets, or non-insurance investor metrics →
financial-analyst(if installed) - Strategy, operating model, or transformation without actuarial workstream →
business-consultant - SOC 2 / ISO control mapping and technical audit evidence →
compliance-engineer - Cross-team software delivery, RAID, and program milestones only →
technical-program-manager
Related skills
| Need | Skill |
| Technical pricing, reserving, triangles, assumptions | actuary |
| P&C products, claims, underwriting context | property-casualty-insurance |
| Financial statements, variance, non-insurance analytics | financial-analyst (if installed) |
| Executive strategy without actuarial deliverables | business-consultant |
| Contract, DPA, regulatory interpretation | commercial-counsel |
| Control evidence and compliance automation | compliance-engineer |
| Multi-team timelines, dependencies, launch governance | technical-program-manager |
Core Workflows
1. Engagement framing and independence
- Clarify client role (insurer, reinsurer, investor, regulator-facing company, TPA)
- Define decision the engagement supports (transaction, opinion year, model approval, board review)
- Document independence constraints (prior work, management roles, advocacy vs advisory)
- Identify conflicts (same team pricing and opining; data vendor ties)
- Set success criteria and explicit out-of-scope items
See references/actuarial_consulting_scope.md.
2. Scoping and SOW
- List deliverables with format (memo, workbook, presentation, data request)
- Specify data owners, cutoffs, legal hold, and confidentiality
- Define methods at headline level; defer technical picks to
actuaryworkstream - Agree timeline, review gates, and client point-of-contact
- Include fees, change-control, and reliance limitations
See references/engagement_scoping_and_sow.md.
3. Client deliverables and communication
- Map audiences (CFO, CRO, board, external auditor, regulator—overview)
- Build storyline: issue → analysis → implication → decision or open item
- Separate executive summary from technical appendix and exhibits
- Prepare management presentation and anticipated Q&A
- Log version control, distribution list, and redaction rules
See references/client_deliverables_and_communication.md.
4. Due diligence and M&A support
- Scope blocks (reserves, pricing, capital, reinsurance, run-off, embedded value)
- Request data room index aligned to actuarial questions
- Define red-flag checklist (development spikes, one-time items, model changes)
- Structure findings by materiality and deal impact (not investment advice)
- Hand off deep modeling to
actuary; legal terms tocommercial-counsel
See references/due_diligence_and_ma_support.md.
5. Model review and validation engagements
- Classify engagement type (validation, peer review, opinion support, use test)
- Inventory models, owners, version, and intended use
- Plan testing themes (assumions, implementation, governance, output reasonability)
- Document findings severity, remediation, and re-test criteria
- Coordinate with appointed actuary or signatory where applicable
See references/model_review_and_validation_engagements.md.
6. Regulatory, board, and governance
- Clarify forum (examination prep, board risk committee, audit committee)
- Align messages to prior filings and public disclosures
- Prepare exhibit index and backup schedules—not substitute for counsel
- Track action items, responsible owners, and dates
- Archive workpapers per firm policy and professional standards (overview)
See references/regulatory_board_and_governance.md.
Engagement kickoff checklist
Copy and track at project start:
Engagement kickoff:
- [ ] Signed SOW / engagement letter with limitations
- [ ] Independence and conflict memo on file
- [ ] Data request issued; owners and cutoff agreed
- [ ] Internal team: EM, technical actuary, reviewer, PM (if needed)
- [ ] Client RACI: sponsor, data SME, signatory actuary
- [ ] Deliverable formats and draft review dates
- [ ] Escalation path (client + firm risk/quality)Engagement type matrix
| Trigger phrase | Primary workflow | Lead reference |
| SOW actuarial / actuarial engagement | Scoping and SOW | engagement_scoping_and_sow.md |
| actuarial memo / management presentation | Deliverables and comms | client_deliverables_and_communication.md |
| due diligence actuarial / M&A reserves | DD framing and findings | due_diligence_and_ma_support.md |
| model validation engagement | Validation plan and findings | model_review_and_validation_engagements.md |
| reserve opinion / actuarial review | Opinion support + governance | regulatory_board_and_governance.md |
| regulatory actuarial | Prep pack (overview) | regulatory_board_and_governance.md |
When multiple types apply (e.g., M&A plus validation), split workstreams in the SOW with separate timelines and reviewers.
Quality review and sign-off
Before any client-facing draft:
- Technical completeness — exhibits tie to data cutoff; bridges reconcile
- Narrative consistency — memo, deck, and appendix use same definitions
- Audience test — executive summary understandable without actuarial training
- Independence check — no advocacy language beyond supported analysis
- EQ / peer review — logged comments resolved or documented as exceptions
- Versioning — draft watermark until final; distribution list approved
Coordinate with technical-program-manager when actuarial work is one stream in a larger transaction program (shared milestones only).
Deliverable standards
| Deliverable | Minimum content |
| Engagement letter / SOW | Scope, deliverables, data, timeline, fees, limitations, reliance |
| Actuarial memo | Purpose, scope, summary conclusion, methods overview, limitations, exhibits list |
| Management deck | 5–12 slides: context, findings, impact, recommendations, open items |
| DD report section | Material issues, evidence pointers, quantified range where supported |
| Validation report | Scope, criteria, findings, management responses, follow-up |
| Board / regulatory pack | Agenda fit, consistent metrics, glossary, appendix index |
| Workshop readout | Decisions, open items, owners, dates |
| Finding register | ID, severity, evidence, management response, re-test status |
State uncertainty, reliance limits, and non-advice boundaries. Do not present consulting output as statutory filing, legal opinion, or appointed-actuary sign-off without qualified human review.
Common pitfalls
- Scope creep without change order when new LOBs or models are added mid-engagement
- Orphan exhibits that do not support a stated conclusion in the memo
- Metric drift between deck, memo, and public filings
- Dual role pressure (consultant validates own prior model build)
- Missing data treated as zero rather than flagged as limitation
- Regulatory meeting prep that crosses into legal interpretation—escalate to
commercial-counsel
When to load references
- Scope, independence, ethics →
references/actuarial_consulting_scope.md - SOW and scoping →
references/engagement_scoping_and_sow.md - Memos, decks, stakeholder comms →
references/client_deliverables_and_communication.md - M&A and due diligence →
references/due_diligence_and_ma_support.md - Model validation and review →
references/model_review_and_validation_engagements.md - Board, regulatory prep, governance →
references/regulatory_board_and_governance.md
Other versions1 project uses a version of this.
Word for word · 1
- daemon-blockint-tech/Agentic-Enteprises-Skill★ 8100% 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
- 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
- assumption-settingSkill
- 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

