Skip to content
Back to skills

Separate Frequency And Severity

ASecurity

Decompose a loss-ratio move into frequency and severity, since they have opposite responses, before prescribing. Reach for this when the loss ratio moves.

  • 7 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agents

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add mcorbett51090/RavenClaude --skill separate-frequency-and-severity --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Separate Frequency And Severity?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Separate Frequency And Severity
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-separate-frequency-and-severity/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-separate-frequency-and-severity)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: separate-frequency-and-severity
description: "Decompose a loss-ratio move into frequency and severity, since they have opposite responses, before prescribing. Reach for this when the loss ratio moves."
---

# Skill: Separate frequency from severity

Frequency and severity look like one number and need opposite fixes.

## Step 1 — Split the loss ratio
Claim count (frequency) vs cost per claim (severity) (§3 #3).

## Step 2 — Attribute severity
Social inflation, mix shift, or reserve strengthening.

## Step 3 — Attribute frequency
Risk selection, exposure growth, or external trend.

## Step 4 — Match the response
Risk-selection fix for frequency; pricing/claims fix for severity.

## Output
A frequency/severity split, an attribution of each, and the matched response.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…