casemark/breach-of-purchase-agreement-complaint
skills/legal/breach-of-purchase-agreement-complaint/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add casemark/skills breach-of-purchase-agreement-complaintInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 25, 2026, 3:30 AM26.2s1 file scanned
SKILL.md
- name:
- breach-of-purchase-agreement-complaint
- language:
- en
- description:
- >-
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:
- Executed agreement — including amendments, riders, addenda, notices, cure letters, and payment records.
- Party data — legal names, entity types/formation states, addresses, registered agents.
- Transaction timeline — negotiation, execution, performance milestones, breach event, notice, and mitigation efforts with supporting evidence.
- Jurisdictional directives — target court, forum-selection and choice-of-law terms, arbitration scope, local filing requirements.
- 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.
Related Skills
casemark/medical-records-gap-analysis
tools
VerifiedTrustedCommunity
Audits the complete in-scope medical-record universe in a litigation matter and produces an attorney-facing, Bates-cited analysis of treatment gaps, missing records or providers, baseline coverage, material billing or production mismatches, and complaint evolution. Use when asked to find missing medical records, analyze treatment gaps or first-care timing, identify absent providers, assess whether a production is complete, or prepare a records-request target list. Use medical-record-chronology instead when the primary request is a chronological clinical narrative.
40SKILL.mdUpdated Sep 3, 2026
casemark/private-placement-memo
development
VerifiedTrustedCommunity
Drafts a legally compliant Private Placement Memorandum for Regulation D offerings (Rule 506(b)/506(c)), covering full disclosure framework including risk factors, capitalization, securities terms, use of proceeds, and investor qualification requirements. Enforces SEC anti-fraud compliance under Section 10(b)/Rule 10b-5, blue sky law considerations, and accredited investor verification under Rule 501. Use this skill when drafting PPMs, offering memorandums, Reg D disclosure documents, or private offering circulars for issuers raising capital from sophisticated investors. Also trigger when the user mentions private placement disclosure, offering memorandum, Reg D fundraising, or accredited investor verification. Even if the user just says "PPM" or "draft our offering memo," use this skill.
40SKILL.mdUpdated Apr 17, 2026
casemark/privacy-law-updates
data-ai
VerifiedTrustedCommunity
Generates structured privacy and data protection law briefings across US, EU, UK, and other jurisdictions. Organizes by jurisdiction with compliance deadlines, enforcement actions, and legislative changes. Use when preparing privacy law briefings, compliance updates, regulatory change summaries, or data protection landscape reviews.
40SKILL.mdUpdated Apr 17, 2026
casemark/prior-art-summary
testing
VerifiedTrustedCommunity
Generates structured summaries of prior art references for patent prosecution, validity analysis, and freedom-to-operate assessments. Maps disclosures to claim elements with precise citations. Use when summarizing prior art, analyzing patent landscapes, mapping references to claims, or preparing office action responses.
40SKILL.mdUpdated Apr 17, 2026