executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
apology-letterWrite 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…
Independent GitHub snapshot · Automated classification · Original documentation governs
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.
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.
Ask for these only if they aren't already provided (else infer and label):
A complete, ready-to-send message in this order:
Then provide a short version (2–4 sentences) for chat/social, and notes on anything to confirm.
Effective-apology practice — specific acknowledgement, unconditional responsibility, empathy, concrete remedy, and credible prevention.