skills/legal/class-settlement-preliminary-approval/SKILL.md
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.
npx skillsauth add casemark/skills class-settlement-preliminary-approvalInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Drafts a Rule 23(e) motion seeking preliminary approval, provisional class certification, notice plan approval, and scheduling of a final approval hearing.
| 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.
| 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 |
Apply the "range of possible approval" standard: settlement must appear fair, reasonable, and adequate without obvious deficiencies.
Rule 23(e)(2) factors:
Cite circuit-specific authority. Tie each factor to case-specific facts.
| 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).
Notice methodology:
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.
| 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.
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.
Key changes from original:
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?
development
name: automated-contract-summary language: en description: Generates structured executive summaries of contracts using ML — captures key terms, party obligations, risk allocations, and compliance requirements in a standardized format. Optimized for high-volume review where speed and consistency matter. tags: - summarization - agreement - corporate --- # Automated Contract Summarization Produces standardized executive summaries of contracts using machine learning, capturing essential term
tools
Extracts regulatory obligations from dense regulations across jurisdictions. Breaks down multi-level regulations into clear article-level obligations, classifies applicability to a business, and prioritizes by risk level. Use when translating regulations into actionable compliance requirements.
development
Continuously monitors regulatory landscapes for changes relevant to a specific business. Ingests global regulatory updates, filters by relevance, summarizes impact, and produces an actionable change advisory. Use when tracking regulatory developments affecting a particular product or market.
testing
Compares an organization's existing compliance controls, policies, and procedures against extracted regulatory obligations to identify coverage gaps. Produces a remediation plan with prioritized actions. Use when assessing compliance maturity or preparing for regulatory audits.