Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
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
  • 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

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Discovery Dispute Letter

ASecurity

Drafts discovery dispute resolution letters documenting meet-and-confer efforts and unresolved issues in U.S. litigation. Use when drafting meet-and-confer letters, discovery conference follow-ups, or pre-motion to compel correspondence during the discovery phase.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
documentationgo

Works with

cli

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill discovery-dispute-letter --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Discovery Dispute Letter?

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

Security grade badge for Discovery Dispute Letter
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-discovery-dispute-letter/badge)](https://www.skillsdirectory.com/skills/lev-os-discovery-dispute-letter)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: discovery-dispute-letter
description: Drafts discovery dispute resolution letters documenting meet-and-confer efforts and unresolved issues in U.S. litigation. Use when drafting meet-and-confer letters, discovery conference follow-ups, or pre-motion to compel correspondence during the discovery phase.
tags:
  - drafting
  - letter
  - litigation
---

# Discovery Dispute Resolution Letter

Drafts a court-ready letter that documents meet-and-confer efforts, memorializes agreements, and builds the record for potential motions to compel.

## Required Inputs

1. **Case info** — caption, court, case number, judge, discovery deadline
2. **Conference details** — date, participants, outcomes (if conference held)
3. **Disputed requests** — exact request language, objections raised, compromises discussed
4. **Scheduling order** — discovery cut-off, motion deadlines

## Letter Structure

**Header:** Date, opposing counsel address, Re line with full caption, case number, client name, matter number, discovery cut-off date. Include "Via Email" with address.

**Body sections in order:**

1. **Opening** — Reference conference date/participants, acknowledge agreements, identify remaining disputes. Note motion practice may follow.
2. **Agreements Reached** — Numbered list of compromises with compliance deadlines. Request written confirmation.
3. **Outstanding Disputes** — Organized by discovery method (RFPs, interrogatories, depositions). Use the per-dispute format below.
4. **Deadlines** — Specific response date tied to court schedule. State motion to compel and sanctions consequences.
5. **Closing** — Invite further discussion, propose specific follow-up date/time. Include preservation reminder.
6. **Signature Block** — Name, title, contact info, cc list, attachments (original requests, conference notes, scheduling order).

## Per-Dispute Format

Each disputed item must include all four elements:

1. **Exact Request Language** — quote verbatim as served
2. **Opposing Objection** — quote verbatim
3. **Why Objection Lacks Merit** — cite applicable rules and authority
4. **Proposed Compromise** — narrowed alternative demonstrating reasonableness

## Letter Type Variations

- **Pre-conference agenda** — collaborative tone; outlines issues for conferral; sent before meet-and-confer
- **Post-conference follow-up** — precise, collaborative; memorializes agreements, narrows disputes; sent within 24–48 hours
- **Pre-motion to compel** — firm, formal; final attempt before court involvement; allow response time before filing deadline

## Guidelines

- **Write for the judge** — every sentence may become a motion exhibit; make the client look reasonable
- **Quote exactly** — requests and objections must be verbatim as served
- **Characterize fairly** — describe opposing responses accurately even when inadequate
- **Cite authority** — FRCP 26(b)(1) (proportionality), FRCP 30(a)(1) (depositions), FRCP 33(d) (interrogatories), plus local rules
- **Demonstrate good faith** — show willingness to compromise on scope, timing, or format
- **Pin down follow-up** — always propose a specific callback date/time to prevent indefinite delay
- **Preservation language** — remind of ongoing duty to preserve documents and ESI

## Court-Specific Notes

- **Federal** — Rule 26(f) meet-and-confer required; Rule 26(b)(1) proportionality; magistrate referral; CMO deadlines
- **State** — verify local meet-and-confer requirements; check objection standards and discovery cut-off calculations
- **Complex commercial** — address e-discovery protocols, protective orders, voluminous production, privilege log disputes

## Checklist

- Local meet-and-confer rules satisfied
- Reasonable response deadline provided
- All disputed items identified with exact request language
- Good faith compromise demonstrated for each dispute
- Legal authority cited for contested positions
- Firm but professional tone throughout
- Preservation language included
- Letter is court-exhibit ready

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Caveman Help

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

1023330 votes

How It Works

Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".

929660 votes
View all in documentation →