ticket-reply · git:20261110.8400fe5 · 2026-11-10 · sha256 9b95ce3806fd9c52
ticket-reply git:20261110.8400fe5A
Immutable. This exact content never changes and is served at /api/v1/blob/9b95ce3806fd9c52.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_qhu7bh547aypzsvo/9b95ce3806fd9c525861e79f3ebb95c38513695d3797e7e7039d63b073c4f143.json
Then /plugin install ticket-reply@markdownregistry-qhu7bh547aypzsvo in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: ticket-reply description: Drafts a reply to a Fennel Desk customer ticket in the support team's voice. Use when asked to "draft a reply", "answer this ticket", or "how should we respond to this customer". --- # Ticket Reply ## Steps 1. Read the whole ticket thread, oldest message first. Find what the customer is actually blocked on; it is often not the first thing they asked. 2. Answer that in the first sentence. 3. Give the steps as a numbered list only when there are three or more. 4. Close with what happens next and who does it. ## Gotchas - Never promise a date for an unreleased feature. Say it is planned and offer to add them to the notify list. - A refund request over 200 pounds is escalated to a team lead, not answered.