Demand Letter Skill for Muse
Firm, factual demand letters — structured asks with deadlines and no empty threats.
- What
- Firm, factual demand letters — structured asks with deadlines and no empty threats.
- Cost
- Free
- Needs
- none beyond standard skill tooling — no external services, APIs, or dependencies. You bring the dispute facts (parties, dates, amounts, basis, desired outcome).
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Drafts firm, professional demand letters that stay calm, factual, and specific: header with sender/recipient/date, a neutral chronological statement of facts, the contract clause or obligation relied on, a precise demand with an explicit deadline, and consequences stated factually — never lurid threats. Handles payment demands, breach of contract, cease-and-desist, refunds, and return of property, ending with a pre-send verification checklist (exact figures, governing clause, notice periods, whether counsel should send it). Guardrails run throughout: no insults or defamation, no vague demands, no threats the sender can't lawfully pursue. Discovered via skills.sh. Honest note: this is a drafting tool, not legal advice — laws and remedies vary by jurisdiction; have a qualified lawyer review before sending, especially before threatening litigation. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Curated by Skill Harbor — free, open-source skill (MIT) by @mohitagw15856.
Version:
Quick answer
Demand Letter is a free Muse skill for firm, factual demand letters with structured asks, deadlines and no empty threats. It keeps the tone serious and the facts clear, so the recipient understands exactly what is requested and by when. That discipline makes letters more credible and more likely to produce a real response.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 1cbf1f0Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: none beyond standard skill tooling — no external services, APIs, or dependencies. You bring the dispute facts (parties, dates, amounts, basis, desired outcome). Install "Demand Letter Skill for Muse" for me. Draft firm, professional demand letters — chronological facts, contractual basis, precise demand with deadline, factual consequences, and a pre-send verification checklist. Repository: https://raw.githubusercontent.com/mohitagw15856/pm-claude-skills/1cbf1f0a58f78f4daf742a278484b89768a7e961/skills/demand-letter/SKILL.md Pinned version: install the code at commit 1cbf1f0a58f78f4daf742a278484b89768a7e961 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file from the repository path into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code; credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "demand-letter". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. provide the facts of the dispute, and arrange a lawyer review before sending). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 1cbf1f0 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.