dispute-letter

GitHub

用于撰写正式争议信函,针对错误收费、账单或信用记录。生成结构清晰、语气坚定的信件,明确陈述争议事项、原因、证据及纠正要求,并附带在线表单短版和注意事项,旨在建立完整的书面记录以备后续跟进。

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

Trigger Scenarios

用户要求对未授权的信用卡扣费提出异议 用户需要质疑账单或发票金额错误 用户要求挑战信用报告中的不准确记录 用户希望正式申诉某项费用

Install

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

Non-standard path

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

Use without installing

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

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill dispute-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": "dispute-letter",
    "homepage": "https:\/\/mohitagw15856.github.io\/pm-claude-skills\/skill\/dispute-letter.html",
    "metadata": {
        "openclaw": {
            "emoji": "🗓"
        }
    },
    "description": "Write a letter to dispute an incorrect charge, bill, or record. Use when asked to dispute a credit-card charge, contest a bill or invoice, challenge a credit-report error, or formally dispute a fee. Produces a clear dispute letter — what's being disputed, why it's wrong, the evidence, and the correction requested — in the firm, paper-trail tone these situations need."
}

Dispute Letter Skill

Disputes are won on a clear paper trail: state precisely what's wrong, attach the evidence, and request a specific correction in writing. This skill writes that letter so it's easy for the other side to verify and fix — and so you have a dated record if it escalates.

Note: this is a drafting aid, not legal or financial advice. Deadlines and rights vary by jurisdiction and provider (e.g. billing-error and credit-reporting rules); confirm the process and time limits with the provider or a qualified advisor, and keep copies of everything.

Working from a brief

Given "dispute a $90 charge I didn't authorise", write the full letter anyway — structure the dispute and bracket the specifics (account/reference numbers, dates, amounts) to fill in. Note where supporting evidence should be attached. Never withhold the letter for missing detail.

Required Inputs

Ask for these only if they aren't already provided (else bracket to fill in):

  • What you're disputing — the charge/bill/record, the amount, date, and account/reference number.
  • Why it's wrong — not authorised, billed in error, wrong amount, service not received, already paid, inaccurate record.
  • The evidence — receipts, statements, prior correspondence, confirmations you can attach.
  • The correction wanted — reverse the charge, correct the record, refund, written confirmation.
  • Recipient — the bank/merchant/bureau and any required dispute address/process.

Output Format

Dispute Letter

  • Header — your details, date, recipient, and a Re: line with the account/reference number and amount in dispute.
  • 1. Statement of dispute — exactly what you're disputing (item, amount, date), in one clear sentence.
  • 2. Why it's incorrect — the specific reason, with the relevant facts.
  • 3. Evidence — the documents you're relying on / enclosing (listed).
  • 4. Correction requested — the specific action and written confirmation of the outcome, with a reasonable response timeframe.
  • 5. Record note — that you're keeping copies and will escalate (to the regulator/ombudsman) if unresolved.
  • Close — professional sign-off and contact details.

Provide a short version for an online dispute form, and notes on documents to attach and any deadline to confirm.

Quality Checks

  • The disputed item is identified precisely (amount, date, reference) — no ambiguity
  • The reason it's wrong is specific and tied to facts, not just "this seems off"
  • Supporting evidence is listed/enclosed and referenced in the letter
  • A specific correction and written confirmation are requested, with a timeframe
  • The tone is firm and factual, building a clean paper trail
  • A note to confirm jurisdiction-specific deadlines/rights is included

Anti-Patterns

  • Do not be vague about which charge/record and how much — precision is the whole game
  • Do not omit evidence or fail to reference it — assertions without proof stall
  • Do not present this as legal/financial advice or guess at statutory deadlines — flag them to confirm
  • Do not get emotional — a factual record is more persuasive and more useful if it escalates
  • Do not forget to request written confirmation of the resolution

Based On

Consumer dispute practice — precise identification, evidence-backed reasoning, a specific requested correction, and a documented paper trail.

Version History

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

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
1d6b25a8
Indexed
2026-07-19 12:17

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