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 Action Claim Form

ASecurity

Drafts official class action claim forms balancing plain-language accessibility with FRCP 23 enforceability. Trigger when creating settlement claim forms, proof-of-claim documents, or class member claim submissions.

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

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill class-action-claim-form --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Class Action Claim Form?

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

Security grade badge for Class Action Claim Form
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-class-action-claim-form/badge)](https://www.skillsdirectory.com/skills/lev-os-class-action-claim-form)

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

Download Zip
Files
SKILL.md
---
name: class-action-claim-form
description: Drafts official class action claim forms balancing plain-language accessibility with FRCP 23 enforceability. Trigger when creating settlement claim forms, proof-of-claim documents, or class member claim submissions.
tags:
  - drafting
  - litigation
  - pleading
---

# Class Action Claim Form

Draft an enforceable claim form enabling lay claimants to submit settlement claims while satisfying FRCP 23, court orders, and the settlement agreement.

## Prerequisites

Gather before drafting:

1. **Settlement agreement** — approved or pending, with class definition, claim categories, compensation structure
2. **Court orders** — preliminary/final approval with any form-specific requirements
3. **Class definition** — precise membership criteria (dates, transactions, geography)
4. **Administrator details** — name, address, email, phone, website
5. **Release scope** — released parties, released claims, statutory waiver requirements

## Quick Start

1. Confirm jurisdiction (FRCP 23 vs. state equivalent) and adapt statutory language accordingly
2. Draft each section below in order
3. Write at 8th-grade reading level — short sentences, active voice, defined terms
4. Do not simplify release or certification language to the point of unenforceability
5. Run the checks in Pitfalls before finalizing

## Form Sections

### 1. Header & Case Identification

- Title: "OFFICIAL CLAIM FORM" — bold, prominent
- Full case caption, court name, docket number
- Administrator contact (mail, email, phone, website)
- **Deadline**: bold, specific date/time with timezone; state postmark vs. receipt rule
- Intro paragraph: plain-language eligibility summary, reference to settlement agreement date and approval order

### 2. Claimant Information

Structured fields:

- Full legal name (as during class period), current name if different
- Current address, email, phone, alternative contact
- **Class-specific identifiers**: purchase dates, account numbers, employment periods — explain why each is needed
- **Special claimants** (if applicable): deceased (executor + authority docs), minors/incapacitated (guardian + docs), entities (name + authorized rep)
- Privacy disclosure: how personal information will be used and protected

### 3. Claim Details & Documentation

Per claim category from the settlement:

- Checkbox, category description, applicable date range
- Fields for amount/damages, reference number, description of harm

Documentation tiers:

| Claim Amount | Required | Acceptable Forms |
|---|---|---|
| Under threshold | Declaration only | N/A |
| Above threshold | Submit with form | Receipts, statements, contracts, correspondence |

Specify copies acceptable (not originals). Include false-information warning (claim denial, civil penalties, criminal prosecution).

### 4. Certification & Release

**Certification** — under penalty of perjury, claimant affirms:

- Information is true, accurate, and complete
- Claimant meets the class definition
- Claims not previously released; no prior compensation received
- Bound by settlement terms and court orders

**Release** (separate section, own acknowledgment checkbox):

- List all released parties (defendants, affiliates, officers, directors, agents, successors)
- Describe released claims — enforceable specificity, lay-reader clarity
- Include statutory waiver for unknown claims where applicable (e.g., Cal. Civ. Code § 1542 — verify jurisdiction)
- State consequences: bound by settlement/judgment, waive separate suit, bound by appeals

### 5. Signature Block

- Signature line, date, printed name
- Title/relationship field for representatives
- Note electronic signatures acceptable if e-filing permitted
- Representatives must state authority and relationship

### 6. Submission Instructions

| Method | Details |
|---|---|
| Mail | Full address; postmark by deadline |
| Email | Address; received by deadline with timezone |
| Online | URL; uploaded by deadline with timezone |

Include: receipt confirmation process, what to do if no confirmation within stated business days, post-submission timeline (review, notification, challenge process).

Remind claimant: **retain copies of form and all supporting documentation**.

## Pitfalls & Checks

- **Required disclaimers**: (1) submission does not guarantee payment; (2) settlement subject to court approval; (3) attorney fees/costs deducted as applicable
- **Accessibility**: screen-reader compatible; note if translations required for the class
- **Page formatting**: number all pages; case name/number in header/footer; if >2 pages, add first-page checklist
- **No legal advice**: form must not constitute or appear to constitute legal advice
- **Jurisdiction**: confirm FRCP 23 vs. state equivalent; adapt waiver language to all applicable jurisdictions

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 →