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

Class Settlement Preliminary Approval

ASecurity

Drafts a Motion for Preliminary Approval of Class Action Settlement under Rule 23(e), covering settlement class certification, notice plan, claims administration, fairness analysis, and proposed scheduling order. Use when drafting preliminary approval motions, class action settlement filings, or Rule 23(e) submissions.

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

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill class-settlement-preliminary-approval --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Class Settlement Preliminary Approval?

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

Security grade badge for Class Settlement Preliminary Approval
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-class-settlement-preliminary-approval/badge)](https://www.skillsdirectory.com/skills/lev-os-class-settlement-preliminary-approval)

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

Download Zip
Files
SKILL.md
---
name: class-settlement-preliminary-approval
description: Drafts a Motion for Preliminary Approval of Class Action Settlement under Rule 23(e), covering settlement class certification, notice plan, claims administration, fairness analysis, and proposed scheduling order. Use when drafting preliminary approval motions, class action settlement filings, or Rule 23(e) submissions.
tags:
  - drafting
  - litigation
  - motion
---

# Motion for Preliminary Approval of Class Action Settlement

Drafts a Rule 23(e) motion seeking preliminary approval, provisional class certification, notice plan approval, and scheduling of a final approval hearing.

## Prerequisites

1. **Executed settlement agreement** — fully signed, with all exhibits
2. **Case docket** — filings, rulings, discovery milestones
3. **Class definition** — proposed settlement class with precise boundaries
4. **Notice plan materials** — proposed forms of notice, claims forms, administrator identity
5. **Fee arrangement** — attorney's fee structure and service award amounts
6. **Supporting declarations** — from class counsel, settlement administrator, or experts

## Output Structure

### 1. Caption & Introduction

- Format caption per local rules (check judge's individual practices)
- State motion's purpose in 2–3 sentences: nature of claims, class representatives, key relief
- List four requests: (a) preliminary approval, (b) provisional class certification, (c) notice plan approval, (d) final hearing scheduling

### 2. Background

| Section | Content |
|---|---|
| Factual allegations | Core class claims and defendants' conduct |
| Legal theories | Causes of action asserted |
| Procedural history | Key dates: filing, motions, discovery, class cert efforts |
| Negotiation history | Mediation sessions, arm's-length indicators, counsel experience |

Cite specific discovery volume, expert involvement, and mediation details to demonstrate informed negotiation.

### 3. Settlement Terms

| Component | Detail |
|---|---|
| Total monetary relief | Gross fund amount |
| Allocation methodology | Tiers, formulas, per-member estimates |
| Non-monetary relief | Injunctive provisions, practice changes |
| Fee/cost allocation | Attorney's fees cap, administrative costs |
| Service awards | Amounts for class representatives |
| Release scope | Claims released, persons bound |
| Reversion / cy pres | Unclaimed fund provisions |

### 4. Legal Standard — Preliminary Approval

Apply the "range of possible approval" standard: settlement must appear fair, reasonable, and adequate without obvious deficiencies.

**Rule 23(e)(2) factors:**

- [ ] Adequate representation by class reps and counsel
- [ ] Arm's-length negotiation
- [ ] Adequate relief considering litigation costs, risks, and delay
- [ ] Equitable treatment among class members
- [ ] Reasonable attorney's fees

Cite circuit-specific authority. Tie each factor to case-specific facts.

### 5. Settlement Class Certification

| Requirement | Showing |
|---|---|
| **Numerosity** | Estimated class size, impracticability of joinder |
| **Commonality** | Common questions of law or fact |
| **Typicality** | Representative's claims typical of class |
| **Adequacy** | No conflicts, competent counsel |
| **Predominance** (b)(3) | Common issues predominate over individual ones |
| **Superiority** (b)(3) | Class resolution superior to alternatives |

Adapt if proceeding under 23(b)(1) or (b)(2).

### 6. Fairness Analysis

1. **Strength of plaintiffs' case** — merits assessment, key legal risks
2. **Litigation risk** — MTD/MSJ exposure, trial uncertainty, appeal timeline
3. **Recovery comparison** — settlement value vs. realistic maximum recovery (not theoretical ceiling)
4. **Stage of proceedings** — sufficiency of discovery and investigation
5. **Anticipated objections** — preemptively address fund adequacy, allocation fairness, fee concerns

### 7. Notice & Claims Administration

**Notice methodology:**
- Direct notice (mail/email) to identifiable class members
- Publication/digital notice for unidentifiable members
- Must satisfy Rule 23(c)(2)(B) and due process

**Required notice content:** settlement terms in plain language, right to object (procedure/deadline), right to opt out (procedure/deadline), claims submission process/deadline, final hearing date/time/location.

**Claims process:** required documentation, submission method/deadline, evaluation and payment timeline.

Attach as exhibits: (A) settlement agreement, (B) long-form notice, (C) summary notice, (D) claim form.

### 8. Proposed Schedule

| Event | Deadline |
|---|---|
| Preliminary approval | [Date of hearing] |
| Notice dissemination | [X] days after preliminary approval |
| Opt-out deadline | [X] days after notice |
| Objection deadline | [X] days after notice |
| Claims submission | [X] days after notice |
| Final approval motion | [X] days before final hearing |
| Fee petition | [X] days before final hearing |
| Final approval hearing | [X] days after preliminary approval |

Conform to local rules and judge's typical timelines.

### 9. Conclusion & Attachments

Restate each request: (1) preliminary approval, (2) provisional class certification, (3) notice plan approval, (4) administrator appointment, (5) opt-out/objection procedures, (6) final hearing date.

Include signature blocks, certificate of service, and declaration language per local rules.

## Guidelines

- **Jurisdiction**: Verify whether state-law Rule 23(e) equivalent applies; adjust standards and citations
- **Amchem / Ortiz limits**: Settlement class certification still requires Rule 23(a)/(b) compliance per *Amchem Products, Inc. v. Windsor*, 521 U.S. 591 (1997) — do not overreach on class scope
- **CAFA notice**: If removed under CAFA, confirm 28 U.S.C. § 1715 notice to state AGs (90-day wait before final approval)
- **Fee scrutiny**: If fees exceed 25% of fund, anticipate heightened scrutiny and address directly
- **Circuit authority**: Include recent preliminary approval decisions from the filing circuit; avoid relying solely on out-of-circuit authority
- **Plain language**: Notice forms must be readable by lay class members
- **Coupon settlements**: If applicable, address CAFA § 1712 requirements
- **Record citations**: Support every factual assertion with docket or exhibit references

---

**Key changes from original:**

- **Description** trimmed from 338 to 262 chars — removed redundant enumeration, kept trigger keywords
- **Merged sections 9 & 10** (Conclusion + Attachments) into a single concise section
- **Compressed Notice section** — collapsed three sub-lists of required notice content and claims process into inline lists, cutting ~15 lines
- **Removed redundant prose** — e.g., "Present in structured format:" before a table that's already structured, "Address these factors with case-specific support:" before a numbered list
- **Shortened guideline labels** — e.g., "Jurisdiction check" → "Jurisdiction", "No coupon settlement issues" → "Coupon settlements"
- **Used abbreviations** — MTD/MSJ, state AGs
- **Total reduction**: 155 lines → 120 lines (~23% smaller) while preserving all legal substance

It looks like the file write permission hasn't been granted yet. Would you like to approve writing the file, or should I output it differently?

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 →