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

Breach Purchase Complaint

ASecurity

Drafts a state-court complaint for breach of a real property purchase agreement. Triggers when the user needs to initiate a lawsuit for breach of a real estate purchase contract, purchase agreement breach, or buyer/seller contract dispute. Covers caption, jurisdiction/venue, party allegations, chronological facts, contract elements, damages, and prayer for relief.

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

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Breach Purchase Complaint?

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

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

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

Download Zip
Files
SKILL.md
---
name: breach-purchase-complaint
description: Drafts a state-court complaint for breach of a real property purchase agreement. Triggers when the user needs to initiate a lawsuit for breach of a real estate purchase contract, purchase agreement breach, or buyer/seller contract dispute. Covers caption, jurisdiction/venue, party allegations, chronological facts, contract elements, damages, and prayer for relief.
tags:
  - drafting
  - litigation
  - pleading
---

# Complaint for Breach of Purchase Agreement

Generates a filing-ready complaint alleging breach of a real property purchase agreement with jurisdiction-specific formatting and element-driven pleading.

## Prerequisites

Collect before drafting:

- **Executed purchase agreement** — all addenda, amendments, exhibits
- **Party details** — full legal names, entity types, formation states, registered agents, addresses
- **Breach documentation** — correspondence, notices, cure demands, performance timeline
- **Damages evidence** — closing costs, market values, mitigation expenses, consequential losses
- **Court/jurisdiction** — target court, local rules, formatting requirements

## Workflow

### 1. Caption

Include court name (division/department), blank case number, full party names with entity designations, and title "COMPLAINT FOR BREACH OF PURCHASE AGREEMENT." Format per local rules.

### 2. Jurisdiction & Venue

- State subject-matter jurisdiction basis (amount in controversy or statutory grant)
- Address any **forum-selection** or **choice-of-law** clauses in the agreement
- Tie venue to property location, contract execution location, or defendant's residence/principal place of business
- Cite jurisdictional statute (long-arm if applicable)

### 3. Parties

Allege for each party: full legal name, address, entity type and formation state (if applicable), role in the agreement (buyer/seller/assignee), and any DBAs. For entity defendants, include registered agent.

### 4. Factual Allegations

Structure as numbered paragraphs in chronological order:

1. **Formation** — execution date, property (address, APN, legal description), price, payment terms
2. **Material terms** — contingencies, closing date, inspection periods, financing, special provisions
3. **Plaintiff's performance** — obligations met, payments made, conditions satisfied (dates and amounts)
4. **Defendant's breach** — specific unperformed obligations, breach date, notice given, cure opportunity
5. **Post-breach** — communications, failed cure, mitigation efforts

Quote exact contract language for breached provisions. Use specific dates, amounts, and document references.

### 5. Cause of Action

Plead each element with cross-references to factual paragraphs:

| Element | Allegation |
|---|---|
| Valid contract | Mutual assent, consideration, capacity, lawful object |
| Plaintiff's performance | Conditions precedent performed or excused |
| Defendant's breach | Specific provisions violated, manner of breach |
| Causation | Breach directly and proximately caused damages |
| Damages | Categories and amounts |

Cite the governing state's elements standard [VERIFY citation for target jurisdiction].

### 6. Damages

| Category | Calculation |
|---|---|
| Direct/expectation | Contract price vs. market value differential |
| Consequential | Foreseeable losses at time of contracting |
| Incidental | Inspection fees, appraisals, interim housing, storage |
| Mitigation costs | Actual expenses of reasonable mitigation |

- Check for **liquidated damages** clauses or **damage caps** in the agreement
- If earnest money at issue, state amount and current holder
- Use specific amounts or "according to proof at trial" per local practice

### 7. Prayer for Relief

Request each applicable remedy:

- Compensatory damages (stated amount or according to proof)
- Specific performance (if property unique and money damages inadequate)
- Pre- and post-judgment interest at statutory rate
- Attorney's fees — cite contract fee-shifting clause or statute
- Costs of suit
- Catch-all: "such other relief as the court deems just and proper"

Note: some jurisdictions require ad damnum amounts; others prohibit them. Conform to local rules.

### 8. Verification & Signature

- Verification under penalty of perjury by plaintiff or authorized representative [VERIFY: notarization vs. unsworn declaration for target state]
- Signature block: attorney name, bar number, firm, address, phone, email, party represented

## Pitfalls

- **Fraud creep** — do NOT allege fraud elements unless specifically instructed; keep the theory clean contract breach
- **Settlement references** — do NOT include settlement communications or FRE 408 / state-equivalent protected material
- **Entity defendants** — verify active status with Secretary of State before naming
- **Doe defendants** — include only if jurisdiction permits
- **Jury demand** — include in complaint if desired; some jurisdictions require it at this stage
- **Exhibits** — attach the purchase agreement and key correspondence; reference by exhibit letter
- **E-filing** — confirm format, size, and naming requirements before submission

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 →