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

Initial Contact Summary

ASecurity

Generates a structured initial contact summary memorandum from a potential client's first interaction with the firm. Captures case facts, liability indicators, damages, insurance details, and screening criteria. Use during client intake to support conflict checks, case evaluation, and engagement decisions.

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

Works with

cli

Security Analysis

A100/100

Scanned 6/7/2026

$npx -y skills add ThomasMoreAI/legal-skills-open --skill initial-contact-summary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Initial Contact Summary?

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

Security grade badge for Initial Contact Summary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thomasmoreai-initial-contact-summary/badge)](https://www.skillsdirectory.com/skills/thomasmoreai-initial-contact-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: initial-contact-summary
title: Initial Contact Summary
description: Generates a structured initial contact summary memorandum from a potential client's first interaction with the firm. Captures case facts, liability indicators, damages, insurance details, and screening criteria. Use during client intake to support conflict checks, case evaluation, and engagement decisions.
author: CaseMark
author_url: https://github.com/CaseMark/skills/tree/main/skills/legal/initial-contact-summary
license: Apache-2.0
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: personal-injury
language: en
tags: [litigation, summarization, summary]
---

# Initial Contact Summary

Produces a privileged internal memo from a potential client's first contact — the foundation for conflict checking, case evaluation, and engagement decisions. Mark all output as **PRIVILEGED AND CONFIDENTIAL**.

## Required Inputs

Gather from intake interview, referral, or initial documents:

1. **Contact info** — name, phone, email, address, preferred contact method
2. **Incident details** — date, location, description of events
3. **Injuries/damages** — physical, financial, emotional, property
4. **Parties involved** — opposing parties, witnesses, employers, insurers
5. **Insurance** — client's and adverse party's coverage
6. **Prior legal actions** — existing attorneys, filed claims, administrative complaints
7. **Referral source** — how client found the firm
8. **Statute of limitations** — calculate deadline; flag if < 6 months

## Output Sections

### 1. Contact Information

Table with: Name, Phone, Email, Address, Preferred contact, Intake date, Intake by, Referral source.

### 2. Conflict Check

- List all parties to check: potential client, opposing parties, employers, insurers, witnesses, related entities (parent companies, subsidiaries)
- Flag: conflict check **completed** or **pending**

### 3. Incident Summary

- Date/time, location (address + jurisdiction), matter type
- Chronological narrative in client's own words (use quotation marks for key statements)
- Police/incident report: number, agency, obtained/requested status

### 4. Liability Assessment

- Client's theory of fault
- Adverse party conduct (specific negligent/wrongful acts)
- Comparative fault concerns
- Available evidence: photos, video, documents, electronic data
- Witnesses: names, contact info, relationship, anticipated testimony
- Preservation needs: surveillance footage, vehicles, medical devices — **flag deadlines**

### 5. Damages

**Physical**: injuries, treatment to date (providers, facilities), ongoing needs, pre-existing conditions

**Economic**: medical expenses (current + estimated future), lost wages (dates, rate, employer), property damage, out-of-pocket costs

**Non-economic**: pain/suffering indicators, daily activity impact, emotional distress factors

### 6. Insurance

Table with rows for Client, Adverse, and UM/UIM. Columns: Carrier, Policy #, Limits, Claim #, Adjuster.

### 7. Critical Dates

- Date of incident
- **Statute of limitations** — calculate and prominently display; **flag if < 6 months**
- Government claim deadline (if applicable)
- Insurance claim deadline
- Evidence preservation deadline

### 8. Screening Assessment

- **Case strength**: Strong / Moderate / Weak — with brief explanation
- **Damages potential**: High / Medium / Low
- **Recommended action**: Accept / Decline / Further investigation needed
- **Conflicts**: Clear / Potential conflict identified

### 9. Follow-Up Checklist

- [ ] Conflict check completed
- [ ] Statute of limitations calendared
- [ ] Evidence preservation letter sent
- [ ] Medical records authorization obtained
- [ ] Police report requested
- [ ] Insurance claims filed/confirmed
- [ ] Engagement letter prepared
- [ ] Declined letter prepared (if not accepting)

## Pitfalls

- **Statute of limitations**: always calculate and display prominently — missed deadlines are malpractice risk
- **Conflict check gaps**: include all parties and related entities, not just named opponents
- **Narrative inconsistencies**: flag contradictions for follow-up rather than resolving them
- **Declining representation**: document reason and confirm declination letter includes limitations warning
- **Client demeanor**: note emotional state and communication style — relevant to case evaluation

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 →