Apology Letter logo

Apology Letter

CommunityPopular
mohitagw15856
apology-letter

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.

Overview

Publishermohitagw15856
Repositorypm-claude-skills
Skill nameapology-letter
Stars
1.4K
Forks
240
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by mohitagw15856 on GitHub. Read the source before you install it.

Installation

Install the Apology Letter AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git /tmp/pm-claude-skills
mkdir -p .claude/skills
cp -r /tmp/pm-claude-skills/exports/openclaw/apology-letter .claude/skills/apology-letter
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Apology Letter in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Apology Letter on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Apology Letter is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Frequently asked questions

What does the Apology Letter AI skill do?

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.

Why use Apology Letter on TypingMind?

Because you install it once and use it with any model. Apology Letter is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Apology Letter in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mohitagw15856/pm-claude-skills/tree/main/exports/openclaw/apology-letter. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Apology Letter?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Apology Letter?

As many as you like. As long as a model supports skills, you can use Apology Letter with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Apology Letter AI skill free?

Yes. It is published on GitHub by mohitagw15856 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇