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:
Install
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://github.com/mohitagw15856/pm-claude-skills/blob/main/skills/demand-letter/SKILL.md 1. Fetch the SKILL.md file from the repository path into a temporary folder and summarize what it does in one or two sentences. 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.