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

Hearing Prep Summary

ASecurity

Produces a quick-reference hearing preparation summary synthesizing pleadings, evidence, witnesses, and governing law into issue matrices, exhibit cross-references, and procedural checklists. Use when preparing for motion hearings, evidentiary hearings, trials, administrative or arbitration hearings, or when asked for "hearing prep," "trial prep summary," "hearing brief," or "prep memo."

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

Security Analysis

A100/100

Scanned 6/7/2026

$npx -y skills add ThomasMoreAI/legal-skills-open --skill hearing-prep-summary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Hearing Prep Summary?

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

Security grade badge for Hearing Prep Summary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thomasmoreai-hearing-prep-summary/badge)](https://www.skillsdirectory.com/skills/thomasmoreai-hearing-prep-summary)

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: hearing-prep-summary
title: Hearing Preparation Summary
description: Produces a quick-reference hearing preparation summary synthesizing pleadings, evidence, witnesses, and governing law into issue matrices, exhibit cross-references, and procedural checklists. Use when preparing for motion hearings, evidentiary hearings, trials, administrative or arbitration hearings, or when asked for "hearing prep," "trial prep summary," "hearing brief," or "prep memo."
author: CaseMark
author_url: https://github.com/CaseMark/skills/tree/main/skills/legal/hearing-prep-summary
license: Apache-2.0
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: litigation
language: en
---

# Hearing Preparation Summary

Single document that orients counsel, frames issues, and serves as a fast in-hearing reference. Covers every hearing type—motion, evidentiary, trial, administrative, arbitration.

## Prerequisites

Gather before starting:

1. Hearing notice/order (date, time, forum, scope)
2. Operative pleadings and amendments
3. Key motions, briefs, and oppositions
4. Docket sheet and relevant prior orders
5. Evidence: exhibits, declarations, discovery excerpts, transcripts
6. Witness list with contact info and prior statements
7. Applicable rules and authorities (or a request to research them)

## Output Sections

Fill every section that applies. Omit sections that are irrelevant to the hearing scope.

### 1. Hearing Snapshot

| Field | Value |
|---|---|
| Hearing type | |
| Date / time | |
| Location / courtroom / link | |
| Judge / officer / panel | |
| Matter(s) set | |
| Time limits | |
| Burdens of proof | |
| Applicable rules | |

### 2. Case Background

5–10 chronological, fact-only bullets with source citations.

### 3. Procedural Posture

| Item | Date | Source | Impact |
|---|---|---|---|
| Complaint / petition | | | |
| Answer / response | | | |
| Key motions / rulings | | | |
| Pending issues | | | |

### 4. Issues Matrix

Core section. One row per disputed issue.

| Issue | Standard | Moving party position | Opposing position | Key facts | Key authorities | Evidence tie-ins |
|---|---|---|---|---|---|---|

### 5. Legal Standards & Authorities

Include pin cites when available. Flag uncertain citations with `[VERIFY]`.

| Issue | Statute / Rule | Leading cases | Notes |
|---|---|---|---|

### 6. Evidence & Exhibits

| Exhibit ID | Description | Authenticity status | Relevance to issue | Sponsor witness |
|---|---|---|---|---|

### 7. Witnesses

| Witness | Role | Expected testimony | Prior statements | Cross targets | Impeachment |
|---|---|---|---|---|---|

### 8. Evidentiary / Procedural Flags

Include only what is relevant:

- Foundation / authentication gaps to cure
- Hearsay risks and available exceptions
- Motions in limine status and rulings
- Likely objections from each side
- Expert admissibility issues (methodology, qualifications, relevance)

### 9. Strategy & Risk

| Strengths | Weaknesses | Opponent likely themes | Recommended responses | Settlement / stipulation leverage |
|---|---|---|---|---|

### 10. Hearing Logistics & Deadlines

- Briefing or exhibit exchange deadlines
- Required filings (trial brief, witness list, exhibit list, proposed order)
- Tech needs (presentation, video, remote witness)
- Courtroom procedures (local rules, standing orders)
- Interpreter or accessibility needs

### 11. Examination Outlines

Include only if testimony is expected.

```
Witness: [Name]
Purpose: [Theme + issue]
Direct:
  - Topic 1: [Q objectives]
  - Topic 2: [Q objectives]
Cross:
  - Topic 1: [Impeachment / concession]
  - Topic 2: [Contradiction / bias]
```

### 12. Open Items

Actionable items with owner and due date if known.

## Guardrails

- Cite sources for every factual assertion and quote.
- Separate facts from arguments; label advocacy explicitly.
- Never assume law or local rules—verify and mark uncertainties with `[VERIFY]`.
- Prefer tables and checklists over narrative.
- Stay within hearing scope; omit unrelated case history.
- Note jurisdiction and forum in the Hearing Snapshot; adjust standards accordingly.

Attribution

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

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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', ...

698621 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 →