본문으로 건너뛰기
cccskills
무료GitHub에 공개

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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.

Example Trigger Phrases

  • "Write an apology."
  • "Say sorry to a customer."
  • "Make amends after a mistake."
  • "Respond to a complaint with an apology."

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

mohitagw15856의 스킬 모두 보기

이 스킬의 문제 신고