SkillAgentSearch skills...

apology-letter

Write a sincere, effective apology to a customer, group, or the public

Install / Use

npx skills add mohitagw15856/pm-claude-skills --skill apology-letter

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

79/100

Supported Platforms

Universal

Our assessment of apology-letter

apology-letter scores 79/100 on our quality scale, 2660th of 4,140 Development & Engineering skills we index.

Its SKILL.md is 3.3 KB long, well organised into 8 sections and no code examples: a solid amount of guidance for an agent.

With 1,396 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
12/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 6 days ago, so apology-letter is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

apology-letter compared with similar skills

All 4 of these similar skills score higher than apology-letter; compare them before choosing.

SkillScoreStarsUpdatedFormat
apology-letter (this skill)by mohitagw15856791.4k6d agoSKILL.md
ai-job-searchby MadsLorentzen10044.6k1d agoCLAUDE.md
claude-howtoby luongnv8910041.7ktodayCLAUDE.md
algorithmic-artby anthropics100177.9k8d agoSKILL.md
pptxby anthropics100177.9k8d agoSKILL.md

Frequently asked questions

How do I install apology-letter?
Run npx skills add mohitagw15856/pm-claude-skills --skill apology-letter. The install tabs above show the steps for each supported agent.
Which AI agents does apology-letter work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is apology-letter safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is apology-letter still maintained?
The repository was last updated 6 days ago, so apology-letter is actively maintained.

name: apology-letter 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.

Related Skills

View on GitHub
GitHub Stars1.4k
CategoryDevelopment
Updated6d ago
Forks249

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions