Wardn HubTrusted MCP server directory.

Registry

  • MCP Servers
  • Skills
  • Categories

Resources

  • API docs
  • Score method

Contribute

  • Submit server
  • Advertise
© 2026 Wardn Hub
Wardn Hub
MCP ServersSkillsCategoriesAPI docsSubmit server
Submit server
skills/mohitagw15856/pm-claude-skills/demand-letter

demand-letter

1
mohitagw15856/pm-claude-skills·Audit passed·Snapshot 3ffd8294601d

Summary

This source did not publish a separate summary. Review SKILL.md before using the skill.

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
    • Burying the actual demand in a wall of grievance

    Related skills

    capacity-planningcompetitor-teardowncontext-engineering-reviewrunbook-writerreceipts-audit