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

complaint-letter

Write a firm, effective complaint letter that gets a resolution. Use when asked to write a complaint letter, complain to a company about a product/service, escalate poor service, or demand a refund/replacement. Produces a structured complaint — the facts, the impact, the specific resolution you want, and a deadline — in a firm, professional tone that's hard to ignore and easy to act on.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.5 KB

SKILL.md(原文)

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

Complaint Letter Skill

A complaint gets resolved when it's specific, reasonable, and makes the desired action obvious — not when it's angry. This skill writes a letter that lays out the facts, states exactly what you want, and gives a clear deadline, in a firm professional tone that a customer-service team can actually action.

Working from a brief

Given "complain about a flight that was cancelled and they won't refund me", write the full letter anyway — infer the standard facts and a reasonable resolution, and bracket the specifics (dates, order/reference numbers, amounts) to fill in. Never hand back advice instead of the letter.

Required Inputs

Ask for these only if they aren't already provided (else infer and bracket):

  • What went wrong — the product/service, what happened, and when (dates, order/reference numbers).
  • The impact — how it affected you (cost, time, inconvenience, harm).
  • What you've done — prior contact and their response, if any.
  • What you want — the specific resolution (refund, replacement, repair, apology) and any deadline.
  • Recipient & tone — company/person, and how formal.

Output Format

Complaint Letter

A ready-to-send letter:

  • Header — your details, date, recipient, and a clear Re: line with the order/reference number.
  • 1. The issue — what you bought/used, when, and exactly what went wrong (facts, dated, specific).
  • 2. The impact — the concrete consequence for you.
  • 3. Prior attempts — what you've already tried, if anything (shows you've been reasonable).
  • 4. What you want — the specific resolution, stated plainly, with a reasonable deadline for response.
  • 5. Next step — what you'll do if unresolved (escalate, regulator/ombudsman, review) — stated factually, not as a threat.
  • Close — professional sign-off and how to reach you.

Provide a short email version too, and notes on anything to confirm.

Quality Checks

  • The facts are specific and dated, with reference/order numbers where relevant
  • The requested resolution is concrete and reasonable — not vague dissatisfaction
  • A clear, reasonable deadline for response is included
  • Tone is firm and professional, not abusive (abuse gives them a reason to dismiss you)
  • The escalation path is stated as a fact, not an empty threat
  • Both a formal letter and a short email version are provided

Anti-Patterns

  • Do not vent without asking for anything — name the specific resolution you want
  • Do not be abusive or sarcastic — it lets the recipient dismiss the complaint
  • Do not omit reference numbers and dates — they slow or stall the response
  • Do not make threats you won't act on — state real next steps factually
  • Do not bury the ask — the resolution and deadline must be impossible to miss

Based On

Consumer-advocacy correspondence practice — factual specificity, a concrete remedy, a reasonable deadline, and a stated escalation path.

Example Trigger Phrases

  • "Write a complaint letter."
  • "Escalate poor service."
  • "Demand a refund/replacement."

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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 のスキルをすべて見る

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