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:
- Acknowledge — name specifically what happened, up front.
- Take responsibility — own it directly ("we got this wrong"), no "if", no "but", no blame-shifting.
- Empathy — show you understand the actual impact on them.
- Make it right — the concrete fix and, where appropriate, a make-good (refund, replacement, credit).
- Prevent recurrence — briefly, what changes so it doesn't happen again (only if true).
- 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
Anti-Patterns
Based On
Effective-apology practice — specific acknowledgement, unconditional responsibility, empathy, concrete remedy, and credible prevention.
Example Trigger Phrases
- "Write an apology."
- "Say sorry to a customer."
- "Make amends after a mistake."
- "Respond to a complaint with an apology."
1---2name: apology-letter3description: "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."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/apology-letter7---89# Apology Letter Skill1011A real apology rebuilds trust; a non-apology ("we're sorry you feel that way") destroys it. The difference is12specific: acknowledge what happened, own it without excuses, show you understand the impact, and say concretely13what you'll do. This skill writes apologies that actually land — sincere, accountable, and specific to the14situation.1516## Working from a brief1718Given "apologise to a customer whose order we lost", **write the full apology anyway** — infer the impact and a19reasonable remedy, label assumptions, and bracket only details to confirm (names, dates, specific compensation).20Never hand back advice about apologising instead of the apology itself.2122## Required Inputs2324Ask for these only if they aren't already provided (else infer and label):2526- **What happened** — the mistake, and who was affected.27- **The impact** — how it affected them (inconvenience, cost, trust, harm).28- **Your responsibility** — what you got wrong (own your part plainly).29- **The remedy** — what you'll do to fix it and prevent recurrence, and any make-good offer.30- **Recipient & tone** — one customer / a community / the public; and how formal.3132## Output Format3334### Apology: [situation]3536A complete, ready-to-send message in this order:371. **Acknowledge** — name specifically what happened, up front.382. **Take responsibility** — own it directly ("we got this wrong"), no "if", no "but", no blame-shifting.393. **Empathy** — show you understand the actual impact on them.404. **Make it right** — the concrete fix and, where appropriate, a make-good (refund, replacement, credit).415. **Prevent recurrence** — briefly, what changes so it doesn't happen again (only if true).426. **Close** — sincere, human, with a way to reach a real person.4344Then provide a **short version** (2–4 sentences) for chat/social, and **notes** on anything to confirm.4546## Quality Checks4748- [ ] Acknowledges the specific mistake — not a vague "issues occurred"49- [ ] Takes real responsibility — no "if we offended", "but", or blaming the customer/circumstances50- [ ] Shows genuine understanding of the impact, in their terms51- [ ] Offers a concrete fix and, where fitting, a way to make it right52- [ ] Prevention is mentioned only if true, not as empty reassurance53- [ ] Tone matches the severity — proportionate, sincere, not grovelling or glib5455## Anti-Patterns5657- [ ] Do not write a non-apology ("we're sorry you feel that way", "mistakes were made") — it makes it worse58- [ ] Do not use conditional language ("if this caused any inconvenience") when harm clearly occurred59- [ ] Do not bury the apology under excuses, context, or self-justification60- [ ] Do not over-promise prevention you can't deliver61- [ ] Do not be so brief it reads as dismissive, or so effusive it reads as insincere — match the harm6263## Based On6465Effective-apology practice — specific acknowledgement, unconditional responsibility, empathy, concrete remedy, and credible prevention.6667## Example Trigger Phrases6869- "Write an apology."70- "Say sorry to a customer."71- "Make amends after a mistake."72- "Respond to a complaint with an apology."