agentleFS
daemon-blockint-techdaemon-blockint-tech/Agentic-Enteprises-Skill/associate-actuary/SKILL.md

associate-actuary

Skill8 starsChanged 6 months agoMITView on GitHub

Guides associate-level actuarial practice for ASA (SOA, US), ASAI (IAI, India), and analogous associate credentials—role boundaries vs analyst and fellow/chief actuary; credential pathways (high-level); professional standards and confidentiality; signing limits and review chains; leading reserving/pricing workstreams, methodology memos, and peer review; stakeholder communication with management, auditors, and regulators at associate depth; CE/professionalism; career progression; brief cross-border recognition. Use when the user mentions associate actuary, ASA, ASAI, associate of the society of actuaries, actuarial credential, signing authority actuary, professional standards actuary, peer review actuarial, fellowship path, continuing education actuary, or actuarial memo review—not triangle/Excel work (actuarial-analyst), appointed actuary or enterprise risk (actuary), consulting engagements (actuarial-consulting), assumption governance (assumption-setting), or exam tutoring.

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

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
  1. Distinctive:

    Before advising on authority or deliverables:

    line 61
  2. Distinctive:

    Document conflicts, confidentiality, and data handling

    line 84
  3. Distinctive:

    Never imply statutory sign-off the user cannot provide

    line 97
  4. Distinctive:

    Run peer review with documented comments and resolution

    line 106
  5. Distinctive:

    Before circulating a draft externally or upward:

    line 123

≈ “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

Associate Actuary

When to Use

  • Clarify associate-level responsibilities vs actuarial analyst vs fellow/chief actuary
  • Explain ASA, ASAI, or analogous associate credential pathways and credit structures (overview)
  • Apply professional standards, code of conduct, and confidentiality at associate depth
  • Define signing authority limits, review tiers, and approval chains for actuarial work
  • Lead reserving or pricing workstreams, methodology memos, and peer-review cycles
  • Communicate with management, auditors, or regulators on actuarial topics (associate-appropriate depth)
  • Frame continuing education and professionalism requirements (framework-level)
  • Plan career progression from analyst → associate → fellow
  • Summarize cross-border credential recognition concepts (non-exhaustive, not legal advice)

When NOT to Use

  • Day-to-day triangles, IBNR builds, pricing spreadsheets, and exhibit prep → actuarial-analyst
  • Appointed actuary opinions, chief actuary strategy, enterprise capital, or final sign-off → actuary
  • Client SOW, consulting engagement design, M&A DD framing → actuarial-consulting
  • Enterprise assumption governance, assumption papers, and change control → assumption-setting
  • P&C coverage, claims, and underwriting mechanics without credential/role lens → property-casualty-insurance
  • Life/health product and benefit mechanics only → life-health-insurance
  • Pension funding policy and trustee advice → pension-retirement-funds
  • ALM strategy, duration matching, and investment policy → asset-liability-management
  • SOC 2 / ISO control evidence without actuarial judgment → compliance-engineer
  • Exam prep, study plans, or question banks as the primary deliverable (route to education resources if user only wants tutoring)

Related skills

NeedSkill
Hands-on triangles, workpapers, model I/O, reporting tie-outsactuarial-analyst
Technical pricing, reserving, capital overview, governance memos, opinionsactuary
Consulting engagement, SOW, client communication, DD framingactuarial-consulting
Enterprise assumption policy, papers, change controlassumption-setting
P&C products, claims, underwriting contextproperty-casualty-insurance
Life/health benefits and product mechanicslife-health-insurance
Pension funding policy and plan design (overview)pension-retirement-funds
ALM, duration, asset–liability strategyasset-liability-management
Audit evidence pipelines and control automationcompliance-engineer

Core Workflows

1. Role and credential context

Before advising on authority or deliverables:

  1. Credential — ASA, ASAI, other associate-level designation; jurisdiction of practice
  2. Employer type — Insurer, reinsurer, consultant, regulator-facing captive, pension administrator
  3. Assignment — Lead technical workstream, peer review, memo authorship, stakeholder meeting (not sign-off)
  4. Governance tier — Materiality, model tier, required reviewer (fellow, appointed actuary, EQ)
  5. Out of scope — Flag items needing fellow/chief actuary, counsel, or appointed actuary

See references/associate_actuary_scope.md.

2. Credential pathways (overview)

  1. Map exam/credit structure at headline level (SOA, IAI, mutual recognition—no tutoring)
  2. Clarify membership vs credential and continuing obligations
  3. Note experience / professionalism requirements where material
  4. Brief cross-border recognition concepts when user works internationally
  5. Escalate jurisdiction-specific filing or signing rules to qualified human actuary and counsel

See references/credential_pathways_asa_asai.md.

3. Professional standards and ethics

  1. Align work to actuarial standards of practice and firm code (overview)
  2. Document conflicts, confidentiality, and data handling
  3. Separate technical indication from implemented business decision
  4. Disclose limitations and reliance boundaries in memos
  5. Route legal interpretation to commercial-counsel; enterprise assumptions to assumption-setting

See references/professional_standards_and_ethics.md.

4. Signing authority and review

  1. Classify deliverable: workpaper, methodology memo, indication, regulatory exhibit, opinion
  2. Map who may sign or certify vs who may author or peer-review
  3. Define review chain: analyst → associate → fellow → appointed/chief
  4. Log EQ / independent review when policy requires
  5. Never imply statutory sign-off the user cannot provide

See references/signing_authority_and_review.md.

5. Leading actuarial workstreams

  1. Scope reserving, pricing, or cross-functional study with clear decision and date
  2. Assign analyst tasks; retain judgment on method selection and conclusions
  3. Draft methodology memo structure: purpose, data, methods, sensitivities, limitations
  4. Run peer review with documented comments and resolution
  5. Package stakeholder summary separate from technical appendix

See references/leading_actuarial_workstreams.md.

6. Career, CE, and stakeholder communication

  1. Outline progression analyst → associate → fellow and skill expectations
  2. Frame CE / professionalism obligations (framework, not course catalog)
  3. Prepare management or audit talking points at associate depth
  4. Coordinate with actuary for opinion-year or board-level messages
  5. Archive versioned memos and review sign-offs per model risk policy

See references/career_progression_and_ce.md.

Associate deliverable checklist

Before circulating a draft externally or upward:

Associate review:
- [ ] Role and credential appropriate to deliverable type (no implied sign-off)
- [ ] Methods and data period documented; limitations stated
- [ ] Peer review completed per tiering policy; comments resolved or excepted
- [ ] Signing/review chain identified; fellow/appointed actuary engaged if required
- [ ] Metrics and definitions consistent across memo, exhibits, and deck
- [ ] Confidentiality and conflict disclosures on file where needed
- [ ] CE/professionalism obligations not conflated with technical conclusions

Deliverable standards (associate)

DeliverableMinimum content
Methodology memoPurpose, scope, methods, sensitivities, limitations, review log
Workstream planRoles, milestones, data cutoff, review gates, escalation path
Peer review recordFindings, severity, resolution, re-test if applicable
Stakeholder briefDecision-oriented summary; technical backup indexed
Credential / career notePathway overview, gaps, next steps—no exam tutoring unless requested separately

State uncertainty, authority limits, and non-advice boundaries. Do not present associate-level output as appointed actuary sign-off, legal advice, or regulatory filing without qualified human review.

When to load references

  • Scope and role boundaries → references/associate_actuary_scope.md
  • ASA / ASAI pathways → references/credential_pathways_asa_asai.md
  • Standards and ethics → references/professional_standards_and_ethics.md
  • Signing and review → references/signing_authority_and_review.md
  • Leading workstreams → references/leading_actuarial_workstreams.md
  • Career, CE, stakeholders → references/career_progression_and_ce.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.