← Browse

@mohitagw15856/demand-letter

A

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.

skillclaude

Install

agr install @mohitagw15856/demand-letter --target claude

Writes 1 file into .claude/skills/, pinned to git-f26724cd.

  • .claude/skills/demand-letter/SKILL.md

Document


name: demand-letter description: "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."

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

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-f26724cd2d832026-07-31