Draft a firm, professional demand letter that states the facts, the legal/contractual basis, the specific demand, and a deadline.
Use when asked to write a demand letter, send a formal demand for payment, draft a cease-and-desist, or formally request resolution before legal action.
Produces a structured, factual letter with a clear ask and consequences — assertive but not threatening or defamatory.
Not legal advice; have counsel review before sending.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars1.3K
LicenseLICENSE
Default branchmain
Open issues7
Status
Active
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md3,216 B
docsSUMMARY.md478 B
History
First seen on skills.sh
First recorded snapshot · 14 installs
SKILL.md
Demand Letter Skill
A demand letter works when it's calm, factual, and specific: here's what happened, here's the basis, here's exactly what I want, by when, or here's what follows. This skill drafts that letter. Not legal advice — laws and remedies vary; have a qualified lawyer review before sending, especially before threatening litigation.
Working from a brief
Given the dispute, draft the full letter anyway using the facts provided and clearly-labelled placeholders only where the sender must insert specifics (names, exact amounts, dates). Keep the tone firm and professional — never insulting, never an empty threat.
Required Inputs
Ask for (if not already provided):
Type (payment demand, breach of contract, cease-and-desist, refund, return of property)
Parties (sender and recipient) and the relationship (contract, invoice, etc.)
The facts — what happened, with dates and amounts
The basis — the contract clause, invoice, or obligation relied on
The demand — exactly what's wanted, and the deadline
Consequence if unmet (further action / referral to counsel) — kept factual
Output Format
A ready-to-review letter:
Header — sender, recipient, date, "RE: [subject]", and "Sent via [method]" if relevant
Opening — who you are and the purpose in one or two sentences
Statement of facts — a numbered, chronological, neutral account (dates, amounts, what was agreed)
Basis for the demand — the contract term, invoice, or legal obligation engaged
The demand — precise and unambiguous: the exact sum/action and the deadline (e.g. "within 14 days of this letter")
Consequence — what follows if the deadline passes, stated factually (not lurid threats)
Close — how to respond and to whom; "without prejudice" / reservation-of-rights line if appropriate
Signature block
End with: ⚠️ Before sending — items to verify (exact figures, the governing clause, applicable notice periods, whether counsel should review or send it).
Quality Checks
Facts are neutral, chronological, and verifiable — no insults or characterisation
The basis (clause/invoice/obligation) is stated
The demand is specific and has a clear deadline
Consequences are factual, not exaggerated or unlawful threats
Retains the "not legal advice — counsel should review" note
Anti-Patterns
Angry, insulting, or defamatory language that undermines the sender
Vague demands ("pay what you owe") with no figure or deadline
Threats of consequences the sender can't or wouldn't lawfully pursue