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

Complaint Breach Of Contract

ASecurity

Drafts a U.S. plaintiff-side breach of contract complaint with caption, jurisdiction/venue, four-element cause of action, and prayer for relief. Trigger when user needs to draft a breach of contract complaint for state or federal court filing.

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

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill complaint-breach-of-contract --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Complaint Breach Of Contract?

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

Security grade badge for Complaint Breach Of Contract
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-complaint-breach-of-contract/badge)](https://www.skillsdirectory.com/skills/lev-os-complaint-breach-of-contract)

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

Download Zip
Files
SKILL.md
---
name: complaint-breach-of-contract
description: Drafts a U.S. plaintiff-side breach of contract complaint with caption, jurisdiction/venue, four-element cause of action, and prayer for relief. Trigger when user needs to draft a breach of contract complaint for state or federal court filing.
tags:
  - drafting
  - litigation
  - pleading
---

# Complaint for Breach of Contract

Generates a litigation-ready plaintiff-side complaint structured around the four breach-of-contract elements with jurisdiction-appropriate procedural compliance.

## Prerequisites

Collect before drafting:

1. **Governing contract** — executed agreement with amendments, exhibits, attachments
2. **Correspondence** — emails, letters, cure/notice communications (chronological)
3. **Performance evidence** — invoices, delivery records, payment confirmations
4. **Breach evidence** — documentation of defendant's failure, cure notices, responses
5. **Damage calculation** — itemized losses with supporting documentation
6. **Filing court** — jurisdiction, division, and applicable local rules

## Quick Start

1. Identify filing court and confirm jurisdiction (federal diversity/question vs. state general)
2. Extract party details, contract terms, and breach facts from uploaded documents
3. Draft complaint sections in order: caption, jurisdiction/venue, parties, facts, cause of action, relief
4. Verify procedural requirements (jury demand, verification, Rule 11) against local rules

## Complaint Sections

### 1. Caption

- Full court name with division/department
- Case number (if pre-assigned)
- Complete legal names and capacities of all parties
- Jurisdiction-specific formatting per local rules

### 2. Jurisdiction & Venue

| Element | Federal | State |
|---|---|---|
| Subject matter | Diversity: 28 U.S.C. § 1332 (complete diversity + AIC > $75K) or federal question: § 1331 | Statutory/constitutional general jurisdiction |
| Venue | 28 U.S.C. § 1391: defendant residence, contract performance, or breach location | Defendant residence, place of business, or performance/breach location |

State amount in controversy when jurisdictionally required.

### 3. Party Identification

- **Individuals**: legal name, address, contractual role
- **Entities**: legal form, state of organization, principal place of business, registered agent
- **Representative parties**: capacity and source of authority

### 4. Factual Background

Chronological narrative covering:

- **Formation** — date, place, consideration, essential terms
- **Plaintiff's performance** — dates, amounts, deliverables
- **Defendant's breach** — obligations unperformed, breach date, cure notice status
- **Defendant's response** — acknowledgment, dispute, or silence
- **Resulting harm** — causal link from breach to damages

Ground all allegations in uploaded documents with specific dates, amounts, and quoted contract language.

### 5. Cause of Action

Allege each element with dedicated factual paragraphs:

1. **Valid enforceable contract** — parties, subject matter, consideration, mutual assent; address statute of frauds if applicable
2. **Plaintiff's performance** — conditions precedent satisfied or excused/waived
3. **Defendant's material breach** — provisions violated, manner, date
4. **Resulting damages** — causal link to quantified harm

Incorporate contract-specific provisions: notice requirements, cure periods, liquidated damages, attorney's fees clauses. [VERIFY jurisdiction-specific element variations beyond standard four elements]

### 6. Prayer for Relief

- Compensatory damages (itemized where calculable)
- Consequential/special damages (allege foreseeability at contracting)
- Specific performance or injunctive relief (where legally available)
- Pre-judgment and post-judgment interest (cite applicable rate/statute)
- Costs of suit
- Attorney's fees (if contract or statute authorizes)
- Punitive damages (only if jurisdiction permits and facts support bad faith)
- General relief catch-all

### 7. Procedural Requirements

- **Jury demand** — include in body or file separately per local rules
- **Rule 11 certification** — good faith factual and legal basis for all allegations
- **Verification** — sworn verification if required by state court
- **Signature block** — attorney name, bar number, firm, address, phone, email

## Pitfalls & Checks

- Number all paragraphs consecutively for cross-reference in motions
- Keep factual, objective tone — no inflammatory language; reserve argument for briefs
- Ensure factual narrative preemptively addresses likely affirmative defenses: statute of frauds, waiver, impossibility, accord and satisfaction
- All allegations must be supportable by documents in counsel's possession at filing
- Verify local rules for page limits, margins, font, and spacing before finalizing

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 →