本文へ移動
cccskills
無料GitHub で公開

cease-and-desist-letter

Draft a firm, professional cease-and-desist letter to stop harassment, defamation, IP misuse, or unwanted contact — clear about what must stop and what happens if it doesn't. Use when asked to write a cease and desist, make someone stop [harassing/using my work/defaming me], or send a formal letter to stop. Produces a structured letter stating the conduct, why it's wrongful, the specific demand and deadline, and the consequence, plus guidance on delivery and records — flagging when the matter needs a real lawyer. Not legal advice.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Cease-and-Desist Letter

A well-written cease-and-desist often stops the behavior on its own — it signals you're serious, documented, and ready to escalate. This drafts one that's firm and specific without empty threats: what conduct must stop, why it's wrongful, the deadline, and the consequence — while being honest that for serious or ongoing matters, a letter on a lawyer's letterhead (or actual legal action) carries more weight.

What This Skill Produces

  • The letter — a structured cease-and-desist: the parties, the specific conduct, why it's improper, the demand, a deadline, and the consequence of non-compliance
  • The demand & deadline — exactly what must stop (or be removed/returned) and by when
  • Delivery & record guidance — how to send it with proof (trackable/receipted) and keep a copy
  • An escalation note — what a "next step" realistically is, and when to involve a lawyer or authorities
  • A tone check — firm and factual, not abusive or bluffing

Required Inputs

Ask for these if not provided:

  • The conduct — what's happening (harassment, defamation, copyright/trademark misuse, breach, unwanted contact) and by whom
  • The evidence — dates, examples, and what you can document
  • What you want — stop, take down, retract, return, or no further contact
  • Relationship & history — prior warnings, any agreement/contract involved
  • Region & stakes — for tone and whether a lawyer is warranted

Framework: State It, Demand It, Mean It

  1. Identify the conduct precisely. Name the specific behavior with dates/examples — vague accusations are easy to dismiss.
  2. Say why it's wrongful. Tie it to the harm or the right being violated (your IP, reputation, agreement, or a request to stop contact) without overstating the law you can't back.
  3. Make a clear, bounded demand. Exactly what must stop/happen, and a specific deadline.
  4. State a real consequence. What you'll do if ignored (legal action, reporting, platform complaint) — only what you're prepared to actually do.
  5. Deliver with proof and keep records. Send it trackably, keep a copy, and log everything — it becomes evidence if it escalates.
  6. Know the ceiling. For serious harassment, real IP disputes, or threats, a lawyer's letter or formal action carries far more weight — flag it.

Output Format

Cease & desist: [conduct] · to [recipient]

Letter

Re: Demand to cease [conduct] [Identify parties] · [the specific conduct + dates/examples] · [why it's wrongful/harmful] · [the demand: stop/remove/return + deadline] · [consequence if not complied with] · [request for written confirmation].

Deliver: send with tracking/proof of receipt; keep a copy. Keep: evidence log of the conduct and this letter. Escalate if ignored: [realistic next step] — and consider a lawyer for [serious/ongoing/IP/threats].

Not legal advice. For serious matters, a letter from a licensed lawyer (or legal action) is stronger — consult one where the stakes warrant it.

Quality Checks

  • Names the specific conduct with dates/examples
  • States why it's wrongful without overstating the law
  • Makes a clear, bounded demand with a deadline
  • States only a consequence the sender would actually pursue
  • Advises trackable delivery and record-keeping
  • Flags when a lawyer/authorities are the right route
  • Tone is firm and factual, not abusive

Anti-Patterns

  • Vague accusations with no specific conduct or dates.
  • Empty threats the sender won't carry out.
  • Overstating legal claims that can't be backed.
  • Abusive or threatening language that undermines the sender.
  • Sending with no proof of delivery or records.
  • DIY on a serious matter that needs a lawyer.

Example Trigger Phrases

  • "Write a cease and desist to someone using my photos without permission."
  • "Make a formal letter telling my ex to stop contacting me."
  • "Someone's posting defamatory reviews about my business — draft a C&D."
  • "A competitor copied my content — cease and desist letter, please."
  • "Draft a letter demanding a harasser stop, with a deadline."

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

mohitagw15856 のスキルをすべて見る

このスキルの問題を報告する