Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Insurance Correspondence Summarization

ASecurity

Produces structured summaries of insurance claims correspondence including coverage letters, reservation of rights (ROR), denial letters, and claim file documents. Extracts policy details, coverage positions, claims chronology, settlement posture, and liability exposure. Use when summarizing claim files, coverage disputes, ROR letters, denial letters, or multi-document insurance correspondence threads.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
documentationgo

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill insurance-correspondence-summarization --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Insurance Correspondence Summarization?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Insurance Correspondence Summarization
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-insurance-correspondence-summarization/badge)](https://www.skillsdirectory.com/skills/lev-os-insurance-correspondence-summarization)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: insurance-correspondence-summarization
description: Produces structured summaries of insurance claims correspondence including coverage letters, reservation of rights (ROR), denial letters, and claim file documents. Extracts policy details, coverage positions, claims chronology, settlement posture, and liability exposure. Use when summarizing claim files, coverage disputes, ROR letters, denial letters, or multi-document insurance correspondence threads.
---

# Insurance Correspondence Summarization

Synthesizes insurance claims correspondence into a structured briefing with actionable coverage and litigation intelligence. Jurisdiction: US.

## Prerequisites

1. **Claim correspondence** — coverage letters, ROR letters, denial letters, demand letters, claim notices, insurer responses
2. **Policy documents** — if available; flag if missing
3. **Underlying litigation materials** — if referenced (pleadings, case caption, court/docket)

## Output Structure

### 1. Executive Overview (2–3 paragraphs)

- Claim type, status, key parties (insured, insurer, claimant, counsel)
- Urgent coverage or liability issues needing immediate attention

### 2. Factual Background

- Underlying incident: date, location, parties, nature of alleged injury/damage/loss
- Distinguish **undisputed facts** from **contested allegations**

### 3. Coverage Analysis

| Field | Details |
|---|---|
| Policy number(s) | |
| Coverage type(s) | |
| Policy period | |
| Limits / deductibles | |
| Insurer's position | Grant / ROR / Denial |
| Policy language cited | Quote with attribution |
| Disputes / ambiguities | |

### 4. Claims Chronology

| Date | Document | Sender → Recipient | Key Points |
|---|---|---|---|
| | | | |

Include: initial notice, coverage positions, ROR letters, demands, responses, ADR/coverage litigation filings.

### 5. Settlement Posture

- All demands and offers (with dollar amounts)
- Conditions attached to proposals
- Status: ongoing / stalled / concluded

### 6. Missing Documents

List documents referenced but not provided that are needed for complete analysis.

### 7. Next Steps / Action Items

Flag: coverage response deadlines, investigation gaps, declaratory relief considerations, settlement authority needed.

## Guidelines

- **Synthesize across documents** — consolidate related information into single sections; do not summarize document-by-document
- **Quote policy language** verbatim when cited as coverage basis; include document name and date
- **Separate coverage from underlying litigation** — summarize underlying case only as it affects coverage analysis

## Critical Flags

Watch for and explicitly flag:

- **Bad faith indicators**: unreasonable delay, inadequate investigation, wrongful denial, failure to defend
- **Insured conduct issues**: cooperation clause concerns, late notice, misrepresentation
- **Procedural traps**: statute of limitations, notice requirements, conditions precedent

---

**Key changes from the original:**

- **Removed `tags`** — not part of the Agent Skills spec (only `name`, `description`, `license`, `compatibility`, `metadata`, `allowed-tools` are valid frontmatter fields)
- **Tightened description** — removed redundant enumeration of audience roles; kept trigger keywords and concise functional summary
- **Added jurisdiction inline** to overview instead of burying it as a trailing bullet
- **Compressed verbose sections** — "Missing Documents" and "Next Steps" reduced to single directive lines instead of prose paragraphs
- **Split "Guidelines" into two focused sections** — core synthesis guidelines vs. critical flags to watch for, improving scannability
- **Removed redundant wording** throughout (e.g., "List any documents referenced but not provided that are needed for complete analysis" → "List documents referenced but not provided that are needed for complete analysis")
- **Line count reduced** from 69 to 65 lines while preserving all domain-specific content

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Caveman Help

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

1023330 votes

How It Works

Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".

929660 votes
View all in documentation →