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 Of Purchase Agreement Complaint

ASecurity

Drafts a filing-ready U.S. complaint for breach of a purchase agreement. Trigger when the user requests a breach-of-contract complaint, forum-selection analysis, or remedy package for a real-estate or asset purchase dispute.

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

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Breach Of Purchase Agreement Complaint?

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

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

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

Download Zip
Files
SKILL.md
---
name: breach-of-purchase-agreement-complaint
description: >-
  Drafts a filing-ready U.S. complaint for breach of a purchase agreement.
  Trigger when the user requests a breach-of-contract complaint, forum-selection
  analysis, or remedy package for a real-estate or asset purchase dispute.
tags:
  - drafting
  - litigation
  - pleading
---

# Complaint for Breach of Purchase Agreement

Produces a court-ready complaint with jurisdiction, liability elements, and damages precision for purchase-agreement disputes.

## Prerequisites

Gather before drafting:

1. **Executed agreement** — including amendments, riders, addenda, notices, cure letters, and payment records.
2. **Party data** — legal names, entity types/formation states, addresses, registered agents.
3. **Transaction timeline** — negotiation, execution, performance milestones, breach event, notice, and mitigation efforts with supporting evidence.
4. **Jurisdictional directives** — target court, forum-selection and choice-of-law terms, arbitration scope, local filing requirements.
5. **Damages inputs** — direct, consequential, incidental amounts; interest expectations; attorney-fee basis.

## Workflow

### 1. Filing Scaffold

Generate caption, court heading, case-number placeholder, title of action, attorney block, and party designation blocks in court-compliant order.

### 2. Jurisdiction and Venue

Plead each ground with paragraph-supported facts:

- **Subject-matter jurisdiction** — diversity, federal question, or state-law basis.
- **Personal jurisdiction** — defendant presence, contacts, or minimum contacts.
- **Venue** — contract formation/performance/breach location; defendant residence.
- **Forum-selection / choice of law** — enforce contractual forum and governing-law clauses; note arbitration scope.

### 3. Parties

For each party: legal name, capacity/status, role in transaction, full address. Include aliases, registered agent (defendant), and guarantors/assignees/successors as needed.

### 4. Factual Chronology

Numbered paragraphs in strict temporal order. Attach exhibit references to each key event.

### 5. Breach of Contract Cause of Action

Map each element to specific facts and exhibits:

- **Formation** — valid agreement, authority, consideration, essential terms.
- **Duty** — exact breached provision and expected performance.
- **Breach** — specific act/omission, date, breach-notice timeline.
- **Plaintiff performance** — performance completed or valid excuse.
- **Causation and damages** — direct link between breach and resulting harm.

### 6. Damages Ledger

Itemize by category with calculation method and supporting evidence:

- **Expectancy/direct** — contract-differential or replacement-cost.
- **Consequential** — foreseeable losses tied to breach.
- **Incidental** — re-listing, storage, administrative costs.
- **Fees/costs** — only if contract or statute authorizes.

### 7. Prayer for Relief

State each relief bucket explicitly: damages (sum or proof at trial), specific performance (if unique subject matter), pre/post-judgment interest, costs, attorney fees (if authorized), injunctive relief (if warranted).

### 8. Closing Blocks

- Jury demand and filing-status labels.
- Liquidated-damages interpretation or damages-cap caveats.
- Verification block — unsworn declaration or notarized statement per jurisdiction; penalty-of-perjury wording if required.
- Attorney signature block — name, bar number, firm, address, phone, email, date.

### 9. Compliance Checklist

Append to the draft:

- [ ] Jurisdiction and venue internally consistent and sufficient
- [ ] Party descriptors complete and uniformly styled
- [ ] Each breach element has paragraph-level fact support
- [ ] Remedy requests match contractual/statutory authority
- [ ] Court formatting and signature standards met

### 10. Verification Markers

Insert `[VERIFY]` on any assertion of statute, rule, interest rate, filing prerequisite, or remedy authorization not directly supplied by user materials.

## Pitfalls

- Keep factual allegations separate from legal conclusions in each paragraph.
- Quote contract language directly for breach-trigger allegations — do not paraphrase.
- Never invent forum, amount-in-controversy, or statutory authority.
- Preserve forum-selection, arbitration, and liquidated-damage clauses as written.
- Do not embed settlement posture or demand-letter language in the pleading.
- Flag all unverified legal assertions with `[VERIFY]` and confirm with user 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

Springboot Security

Java Spring Boot 服务中关于身份验证/授权、验证、CSRF、密钥、标头、速率限制和依赖安全的 Spring Security 最佳实践。

2456590 votes

Security Review

Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.

2456590 votes

Paperclip Task Bridge

Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.

805540 votes

Summarize Status

Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.

805540 votes

Paperclip Evals

Choose, inspect, validate, and report Paperclip Runner or Product E2E evaluations while preserving evidence, provenance, cost, and failure classification.

805540 votes
View all in security →