apology-letter

Featured

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.

AI & Automation 1,231 stars 221 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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. **Mak...

Details

Author
mohitagw15856
Repository
mohitagw15856/pm-claude-skills
Created
6 months ago
Last Updated
today
Language
HTML
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category