court-formatting

Standardizes U.S. court-filing formatting for pleadings, motions, and briefs. Enforces caption structure, margins, fonts, spacing, pagination, line numbering, and e-filing constraints. Use when formatting court documents, preparing filings, or validating local-rules compliance.

11 stars

Best use case

court-formatting is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Standardizes U.S. court-filing formatting for pleadings, motions, and briefs. Enforces caption structure, margins, fonts, spacing, pagination, line numbering, and e-filing constraints. Use when formatting court documents, preparing filings, or validating local-rules compliance.

Teams using court-formatting should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/court-formatting/SKILL.md --create-dirs "https://raw.githubusercontent.com/CaseMark/skills/main/skills/legal/court-formatting/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/court-formatting/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How court-formatting Compares

Feature / Agentcourt-formattingStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Standardizes U.S. court-filing formatting for pleadings, motions, and briefs. Enforces caption structure, margins, fonts, spacing, pagination, line numbering, and e-filing constraints. Use when formatting court documents, preparing filings, or validating local-rules compliance.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Court Document Formatting

Apply court formatting requirements using a local-rules-first workflow. Local rules and judge-specific standing orders always control over baselines.

## Prerequisites

Gather before starting:

1. Court, division, and governing rule set (FRCP/FRAP/state + local rules)
2. Case number and full party names
3. Document type (pleading, motion, brief, notice, etc.)
4. Judge's individual practices or standing orders
5. E-filing portal requirements and file-size limits
6. Required certificates (service, word count, compliance)

## Core Workflow

### Step 1 — Identify Controlling Sources

Collect in priority order:

1. Judge's individual practices / standing orders
2. Local rules
3. General rules (FRCP/FRAP/state)
4. Court-provided forms or templates
5. E-filing portal requirements

### Step 2 — Apply Baseline Formatting

Apply defaults, then override per local rule:

| Element | Default | Override by |
|---|---|---|
| Paper | 8.5 × 11" | Local rule |
| Margins | 1" all sides | Local rule |
| Font | 12 pt serif (e.g., Times New Roman) | Local rule |
| Body spacing | Double-spaced | Local rule |
| Pagination | Consecutive page numbers | Local rule |
| Line numbers | If required by jurisdiction | Local rule |
| Block quotes | Single-spaced, indented | Local rule |
| Footnotes | Single-spaced, same or smaller font | Local rule |

### Step 3 — Build the Caption

Required elements (verify each against docket):

- Court name (full official name)
- Division (if applicable)
- Party names (exactly as on docket)
- Case number
- Document title
- Filing party designation (if required)
- Assigned judge / magistrate (if required)

Template:

```
IN THE [COURT NAME]
[DIVISION, IF APPLICABLE]

[PLAINTIFF NAME],                     )
     Plaintiff,                       )
v.                                    )   Case No. [NUMBER]
[DEFENDANT NAME],                     )
     Defendant.                       )

[DOCUMENT TITLE]
```

### Step 4 — Check Local Variations

Verify each item against local rules:

- [ ] Page or word limits (and what is excluded from the count)
- [ ] Font typeface and minimum size
- [ ] Spacing rules for body, headings, block quotes, footnotes
- [ ] Line numbering requirements
- [ ] Signature block format
- [ ] Certificate of service content and placement
- [ ] Exhibit labeling, pagination, and separators
- [ ] Proposed order format and file type
- [ ] Redaction rules and notation

### Step 5 — E-Filing Compliance

- [ ] File format: PDF or PDF/A as required
- [ ] Scanned PDFs are OCR'd (unless court prohibits)
- [ ] File size within portal limits; split if needed
- [ ] Bookmarks included for long filings
- [ ] Appendices/exhibits uploaded per portal rules (separate or combined)
- [ ] Privacy redactions applied

### Step 6 — Final Compliance Check

- [ ] Caption matches docket exactly (case number, division, party names)
- [ ] Page/word limits satisfied
- [ ] All required certificates included in correct format and location
- [ ] All exhibits labeled and cross-referenced in text
- [ ] File name follows local-rule naming convention
- [ ] E-filing requirements satisfied

## Common Pitfalls

- **Assuming baselines apply**: Never assume a default format is correct without checking local rules first.
- **Caption mismatches**: Party names, case number, and court title must match the docket exactly — do not rephrase or abbreviate.
- **Missing certificates**: Omitting certificate of service or word-count certificate is a common rejection reason.
- **Non-searchable PDFs**: Ensure all PDFs are text-searchable unless the court explicitly forbids OCR.
- **Unclear requirements**: If any formatting rule is ambiguous, flag it and request the exact rule citation before proceeding.

---

**Key changes made:**

- **Removed `tags`** — not part of the Agent Skills spec
- **Tightened description** — removed "Trigger keywords" list (the description itself contains discoverable terms); kept third-person voice
- **Added priority order** to Step 1 (controlling sources) — the original was a flat list with no hierarchy
- **Converted Steps 4-6 to checklists** (`- [ ]`) — enables copy-and-track workflow per best practices
- **Replaced "Guidelines" section with "Common Pitfalls"** — more actionable, avoids restating what's already implicit in the workflow steps
- **Reduced from 127 lines to ~95 lines** — removed redundant section headers ("Output Structure / Process"), duplicate information, and verbose labels while preserving all domain-accurate content

Related Skills

court-order-summaries

11
from CaseMark/skills

Generates structured summaries of court orders and decisions, extracting obligations, deadlines, monetary awards, injunctive relief, and procedural requirements into an action-oriented reference. Flags ambiguities for attorney review. Converts relative timeframes to calendar dates. Use when summarizing court orders, judgments, injunctions, consent decrees, or compliance orders.

court-document-formatting

11
from CaseMark/skills

Builds a filing-ready formatting blueprint for U.S. litigation pleadings, motions, and briefs by applying caption, spacing, pagination, certificate, and e-filing requirements with court-specific local-rule overrides. Use when preparing court documents, checking filing compliance, generating exhibit packages, or converting drafts for e-filing. Triggers: court filing format, caption, page limits, line numbers, service certificate, PDF/A, local rules, judge instructions.

appellate-formatting

11
from CaseMark/skills

Generates appellate-filing-ready Tables of Contents, Tables of Authorities, and Certificates of Compliance under FRAP 32(g) and related rules. Produces defensible word-count calculations with transparent exclusions and anti-hallucination guardrails for pagination and citations. Covers federal circuits, state appellate courts, and U.S. Supreme Court variations. Use when building TOC, TOA, compliance certificates, formatting briefs for filing, or when the user mentions word count calculation, FRAP 32 compliance, appellate brief assembly, or page numbering.

appellate-formatting-certification

11
from CaseMark/skills

Generates appellate-brief TOC, TOA, and Certificate of Compliance with defensible word-count methodology. Triggers on TOC/TOA rebuilds, certificate of compliance drafting, FRAP 32(g) compliance, word-count certification, or final brief formatting before filing.

managing-out-of-court-workout-processes

11
from CaseMark/skills

Structures exchange offers, consent solicitations, and amend-and-extend transactions as Chapter 11 alternatives. Use when managing out-of-court workouts, designing exchange offers, or structuring pre-negotiated deals.

skill-name

11
from CaseMark/skills

Replace with a specific description of what this skill does and when to use it. Include keywords that help agents identify relevant tasks.

writing-surgical-consultation-notes

11
from CaseMark/skills

Creates structured surgical consultation responses with assessment and surgical candidacy determination. Use when responding to surgical consults, evaluating surgical candidates, or documenting surgical recommendations.

writing-operative-reports

11
from CaseMark/skills

Creates structured operative notes with findings, technique, specimens, and estimated blood loss. Use when dictating operative reports, documenting surgical procedures, or recording intraoperative findings.

writing-irb-submissions

11
from CaseMark/skills

Creates IRB submission packages with protocol summaries, consent forms, and risk-benefit analysis. Use when submitting to IRB, preparing ethics applications, or writing consent documents.

writing-grant-applications-research

11
from CaseMark/skills

Structures NIH/foundation grant applications with specific aims, significance, and innovation sections. Use when writing research grants, preparing NIH applications, or structuring grant proposals.

writing-admission-orders

11
from CaseMark/skills

Generates structured admission order sets with diagnosis-specific protocols and safety checks. Use when admitting patients, creating admission orders, or setting up inpatient care plans.

validating-new-laboratory-tests

11
from CaseMark/skills

Structures test validation with precision, accuracy, linearity, and reference range establishment. Use when validating new assays, documenting method comparisons, or establishing reference ranges.