apology-letter

GitHub

撰写真诚有效的道歉信,适用于客户、群体或公众。要求明确承认错误、承担责任、表达共情、提供具体补救措施及预防方案,避免借口和非正式道歉,确保语气得体且重建信任。

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

触发场景

需要为客户写道歉信 回复投诉并致歉 犯错后向社区或公众致歉 请求弥补过失

安装

npx skills add mohitagw15856/pm-claude-skills --skill apology-letter -g -y
更多选项

非标准路径

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

不安装直接使用

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

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill apology-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": "apology-letter",
    "homepage": "https:\/\/mohitagw15856.github.io\/pm-claude-skills\/skill\/apology-letter.html",
    "metadata": {
        "openclaw": {
            "emoji": "🚨"
        }
    },
    "description": "Write a sincere, effective apology to a customer, group, or the public. Use when asked to write an apology, say sorry to a customer or community, make amends after a mistake, or respond to a complaint with an apology. Produces a genuine apology — acknowledgement, taking responsibility, empathy for the impact, the concrete fix and prevention, and an offer to make it right — in the right tone, without excuses or non-apologies."
}

Apology Letter Skill

A real apology rebuilds trust; a non-apology ("we're sorry you feel that way") destroys it. The difference is specific: acknowledge what happened, own it without excuses, show you understand the impact, and say concretely what you'll do. This skill writes apologies that actually land — sincere, accountable, and specific to the situation.

Working from a brief

Given "apologise to a customer whose order we lost", write the full apology anyway — infer the impact and a reasonable remedy, label assumptions, and bracket only details to confirm (names, dates, specific compensation). Never hand back advice about apologising instead of the apology itself.

Required Inputs

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

  • What happened — the mistake, and who was affected.
  • The impact — how it affected them (inconvenience, cost, trust, harm).
  • Your responsibility — what you got wrong (own your part plainly).
  • The remedy — what you'll do to fix it and prevent recurrence, and any make-good offer.
  • Recipient & tone — one customer / a community / the public; and how formal.

Output Format

Apology: [situation]

A complete, ready-to-send message in this order:

  1. Acknowledge — name specifically what happened, up front.
  2. Take responsibility — own it directly ("we got this wrong"), no "if", no "but", no blame-shifting.
  3. Empathy — show you understand the actual impact on them.
  4. Make it right — the concrete fix and, where appropriate, a make-good (refund, replacement, credit).
  5. Prevent recurrence — briefly, what changes so it doesn't happen again (only if true).
  6. Close — sincere, human, with a way to reach a real person.

Then provide a short version (2–4 sentences) for chat/social, and notes on anything to confirm.

Quality Checks

  • Acknowledges the specific mistake — not a vague "issues occurred"
  • Takes real responsibility — no "if we offended", "but", or blaming the customer/circumstances
  • Shows genuine understanding of the impact, in their terms
  • Offers a concrete fix and, where fitting, a way to make it right
  • Prevention is mentioned only if true, not as empty reassurance
  • Tone matches the severity — proportionate, sincere, not grovelling or glib

Anti-Patterns

  • Do not write a non-apology ("we're sorry you feel that way", "mistakes were made") — it makes it worse
  • Do not use conditional language ("if this caused any inconvenience") when harm clearly occurred
  • Do not bury the apology under excuses, context, or self-justification
  • Do not over-promise prevention you can't deliver
  • Do not be so brief it reads as dismissive, or so effusive it reads as insincere — match the harm

Based On

Effective-apology practice — specific acknowledgement, unconditional responsibility, empathy, concrete remedy, and credible prevention.

版本历史

  • 54fad50 当前 2026-07-19 12:10

同 Skill 集合

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-hiring-panel/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-severance/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/agm-in-a-box/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/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/behavior-intervention-plan/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bennett-time-audit/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-game-designer/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

元信息

文件数
0
版本
e4def4c
Hash
fc831507
收录时间
2026-07-19 12:10

首页 - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-08-01 17:27
浙ICP备14020137号-1 $访客地图$