Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
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
  • Authors
  • 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
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Pre Hearing Statement

ASecurity

Drafts a Pre-Hearing Statement of Proof for personal injury litigation. Use when preparing prehearing statements, statements of proof, or evidentiary summaries for hearings before courts or administrative agencies.

15 stars
0 votes
0 copies
2 views
Added 6/7/2026
ai-agentsgogit

Security Analysis

A100/100

Scanned 6/7/2026

$npx -y skills add ThomasMoreAI/legal-skills-open --skill pre-hearing-statement --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pre Hearing Statement?

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

Security grade badge for Pre Hearing Statement
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thomasmoreai-pre-hearing-statement/badge)](https://www.skillsdirectory.com/skills/thomasmoreai-pre-hearing-statement)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: pre-hearing-statement
title: Pre-Hearing Statement of Proof
description: Drafts a Pre-Hearing Statement of Proof for personal injury litigation. Use when preparing prehearing statements, statements of proof, or evidentiary summaries for hearings before courts or administrative agencies.
author: CaseMark
author_url: https://github.com/CaseMark/skills/tree/main/skills/legal/pre-hearing-statement
license: Apache-2.0
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: personal-injury
language: en
tags: [brief, drafting, litigation]
---

# Pre-Hearing Statement of Proof

Produces a numbered-paragraph prehearing submission presenting evidentiary foundation, witness summaries, and legal arguments for a personal injury matter.

## Required Inputs

1. **Case identifiers** — name, number, forum/agency, hearing date, submitting party
2. **Chronological facts** — key dates, events, parties, relationships
3. **Witness list** — names, contact info, relationship, expected testimony
4. **Documentary evidence** — medical records, photos, correspondence, reports
5. **Medical records** — providers, diagnoses, treatment history, causation opinions
6. **Damages** — itemized breakdown by category and time period

## Quick Start

1. Gather all required inputs above.
2. Draft each section below using numbered paragraphs throughout.
3. Tie every factual assertion to identified evidence — no unsupported claims.
4. Mark uncertain citations with `[VERIFY]`.
5. Review against the Pitfalls checklist before finalizing.

## Document Sections

### I. Introduction

| Element | Content |
|---|---|
| Caption | Case name, number, forum/agency |
| Hearing date | Date and location |
| Submitting party | Name, role (plaintiff/claimant) |
| Nature of claim | Concise description of dispute |
| Legal basis | Statutes, regulations, or common law grounds |
| Relief sought | Specific remedy or damages requested |

### II. Statement of Facts

- Strict chronological order
- Identify all parties and relationships
- Every assertion tied to evidence to be presented
- Objective tone building factual foundation for legal position

### III. Issues for Determination

- Frame each disputed question as a precise issue statement
- Order logically for the hearing officer
- Distinguish legal questions from factual disputes

### IV. Witness Summary

Per witness:

| Field | Content |
|---|---|
| Name | Full name |
| Contact | Address, phone |
| Relationship | Connection to case |
| Expected testimony | Key facts/opinions to establish |
| Purpose | How testimony supports position |

For **expert witnesses**, add: qualifications, expertise area, substance of opinions.

### V. Exhibit List

| Exhibit | Description | Relevance |
|---|---|---|
| A, B, C… | Document type | What it proves |

Organize chronologically or by category. Assign identification letters/numbers.

### VI. Medical Proof

- All treating/evaluating providers
- Diagnoses and treatment history
- Opinions on **causation** and **impairment/disability**
- Connect to applicable legal standards
- Persuasive but accurate tone favoring submitting party

### VII. Legal Argument

- Cite applicable statutes, regulations, case law
- Show how evidence satisfies each legal element
- Anticipate and rebut likely opposing arguments

### VIII. Damages / Relief Sought

- Itemize monetary damages by category (medical, lost wages, pain/suffering, etc.)
- Show calculation methodology and time periods
- For non-monetary relief, specify action requested and legal basis

### IX. Stipulations

- Facts agreed to by both parties
- Exhibits admitted without objection
- Any narrowing of issues

### X. Procedural History

- Prior hearings or proceedings
- Relevant discovery conducted
- **Never reference settlement discussions** (inadmissible)

## Pitfalls

- **Unsupported facts** — every assertion needs identified evidence; no speculation
- **Settlement references** — exclude all settlement communications per FRE 408 / state equivalents
- **Unverified citations** — tag with `[VERIFY]`; do not present uncertain authority as definitive
- **Local rule non-compliance** — incorporate jurisdiction-specific procedural requirements when known
- **Missing numbered paragraphs** — all sections must use numbered paragraphs for easy reference

Attribution

ThomasMoreAIThomasMoreAI
View sourceSee grades on GitHubMore from ThomasMoreAI →
SSkills Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

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 Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →