Skip to content
Skills Library
Sales & customer service · Automation

close-customer-loop

/close-customer-loop

Close the loop with a customer or partner after their reported bug/request ships. Use whenever a customer/partner-reported fix reaches production, a ticket that came from a customer report is about to be marked Done/closed, or you're deciding whether follow-up is still owed. Enforces verify-in-prod-then-reply-in-the-original-thread, and adds the two acceptance-criteria lines when creating customer/partner tickets.

Licence
MIT
Last repository change
01.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 01.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Close the loop with a customer or partner after their reported bug/request ships. Use whenever a customer/partner-reported fix reaches production, a ticket that came from a customer report is about to be marked Done/closed, or you're deciding whether follow-up is still owed. Enforces verify-in-prod-then-reply-in-the-original-thread, and adds the two acceptance-criteria lines when creating customer/partner tickets.

Original author description

Close the loop with a customer or partner after their reported bug/request ships. Use whenever a customer/partner-reported fix reaches production, a ticket that came from a customer report is about to be marked Done/closed, or you're deciding whether follow-up is still owed. Enforces verify-in-prod-then-reply-in-the-original-thread, and adds the two acceptance-criteria lines when creating customer/partner tickets.

How it works

  1. The rule
  2. When marking a customer/partner ticket Done
  3. When creating a customer/partner-reported ticket
  4. Honesty guardrails
  5. Project-specific notes
Original SKILL.md headings · 41 lines, 467 words
SKILL.md preview
---
name: close-customer-loop
description: Close the loop with a customer or partner after their reported bug/request ships. Use whenever a customer/partner-reported fix reaches production, a ticket that came from a customer report is about to be marked Done/closed, or you're deciding whether follow-up is still owed. Enforces verify-in-prod-then-reply-in-the-original-thread, and adds the two acceptance-criteria lines when creating customer/partner tickets.
disable-model-invocation: false
user-invocable: true
---

> Cross-runtime: follow [runtime compatibility](../../references/runtime-compatibility.md) for invocation, delegation, configuration precedence, state paths, and permissions.

# Close the customer loop

When work originates from a **customer or partner report** (a Slack/Telegram thread, a shared doc, a support ticket, an email), the job is **not done when the fix ships — it's done when the reporter has been told, in the original thread, that it's live.** A silent prod fix reads as no progress and is exactly how follow-ups get dropped and partners go cold.

## The rule

A customer/partner-reported item is only truly closed when **both** are true:

1. **Verified live in prod** — a real check against production, not "the release tag went out" or "it merged." Actually exercise the changed behavior (curl the endpoint, run the flow, query live data). Staging passing is not prod.
2. **Reply sent in the original thread** — confirm it's live and say what to re-test. If some of the report is still not addressed, say so honestly rather than implying everything is done.

If you (the agent) can't post to the thread yourself, **hand the user a ready-to-send draft** and explicitly flag the reply as *still owed* — do not present the ticket as closed until it's actually sent.

## When marking a customer/partner ticket Done

- Do the prod verification first (step 1). If it fails, don't close it — reopen/diagnose.
- Draft or send the thread reply (step 2).
- Only then move the ticket to the terminal/Done state.
- Never batch-close customer tickets on merge — each needs its own prod check + reply.

## When creating a customer/partner-reported ticket

Add these two lines to the ticket's Acceptance Criteria so the loop can't be forgotten:

- `Fix verified live in prod`
- `Reply in the original customer thread once live in prod (link the thread)`

If the tracker (e.g. Linear) has a bug/issue template, the same two lines belong there — but templates are usually UI-only and not editable via API/MCP, so add the lines to the issue body yourself when creating.

## Honesty guardrails

- Never tell a customer something is fixed/live that you haven't verified against prod. If you're inferring from a release tag, verify before you claim it (some prod routes are auth/tier-gated and a default key won't reach them — use a valid key to actually hit the endpoint).
- Separate what shipped from what's still backlog. Tell the customer both, plus a real next step or timeline for the open items rather than a vague "soon."

## Project-specific notes

If the current repo has its own ticket-workflow skill (e.g. a `linear-workflow` skill), follow that for column names, projects/cycles, and any repo-specific prod-verification details (like which key reaches gated routes). This skill is the general principle; the repo skill wins on repo specifics.

Versions

The database has no other skills named close-customer-loop.

Database snapshot: 13.11.2026 · package version 5feda13ab082 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100support-loop
    End-to-end founder customer support loop. Ingests a customer bug report or inquiry, investigates the codebase, reproduces the issue, triggers engineer-mode bug-fix if valid, or prepares a workaround, and drafts an empathetic, contextual customer reply. Use for /support-loop,…
  • 100partner-potential
    Audits a call about a deal a partner wants to bring, to see whether it is a real partner deal, with a named end customer, a fit that the partner and the customer both state, a purchase or registration step, a timeline, who sells and what terms apply. Use when the user asks…
  • 100partner-competition-landscape
    Audits a call with a channel partner to see whether it learned which rival vendors the partner carries, how much of their business each is, what the rivals offer that the vendor does not, how terms compare in the partner's words, what would make the partner switch a customer,…
  • 100voice-of-customer
    Voice of Customer program - multi-source signal collection, theming and prioritization, evidence-to-action routing, and product / CS / marketing feedback loop closure. Use when: voice of customer, VoC program, customer feedback, NPS / CSAT / CES, qualitative theming, feedback…
  • 100om-customer-success
    Run customer success and support in Whalyom: ticket taxonomy and deflection through the help center, macros in the brand voice, a health score from usage, billing and support signals, onboarding to first value, QBRs for B2B accounts, closing the voice-of-customer loop to product…
  • 96customer-research
    When the user wants to conduct, analyze, or synthesize customer research.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.