Agent Skillsmohitagw15856/pm-claude-skills › complaint-letter

complaint-letter

GitHub

生成专业、有力的投诉信,通过清晰陈述事实、影响及具体诉求并设定截止日期,促使对方解决争议。支持根据简要信息自动推断细节,提供正式信函与邮件版本,确保语气坚定且具可执行性。

exports/openclaw/complaint-letter/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

撰写针对产品或服务的投诉信 要求退款或更换商品 升级处理糟糕的服务体验

Install

npx skills add mohitagw15856/pm-claude-skills --skill complaint-letter -g -y
More Options

Non-standard path

npx skills add https://github.com/mohitagw15856/pm-claude-skills/tree/main/exports/openclaw/complaint-letter -g -y

Use without installing

npx skills use mohitagw15856/pm-claude-skills@complaint-letter

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill complaint-letter -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "name": "complaint-letter",
    "homepage": "https:\/\/mohitagw15856.github.io\/pm-claude-skills\/skill\/complaint-letter.html",
    "metadata": {
        "openclaw": {
            "emoji": "🗓"
        }
    },
    "description": "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."
}

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.

Version History

  • 54fad50 Current 2026-07-19 12:14

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
3cafd2d1
Indexed
2026-07-19 12:14

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-30 19:26
浙ICP备14020137号-1 $방문자$