Customer Billing Ops

This handles the messy reality of customer billing support: duplicate subscriptions, refund triage, failed renewals, and churn incidents in tools like Stripe. It walks you through identifying the customer cleanly, classifying the issue (accidental duplicate vs. real team purchase vs. product failure), then taking the safest reversible action before you fire off a refund. The workflow is opinionated about using hosted billing portals over custom code and explicitly separating customer remediation from product backlog work. If you're the person who gets pinged when someone says "your checkout charged me twice" or "I can't cancel," this gives you a structured way to investigate, act, and document without exposing PII or making expensive mistakes.

skills.sh installs: 3.8K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill customer-billing-ops --agent claude-code

Installs into .claude/skills of the current project.

Files

Customer Billing Ops

Use this skill for real customer operations, not generic payment API design.

The goal is to help the operator answer: who is this customer, what happened, what is the safest fix, and what follow-up should we send?

When to Use

Customer says billing is broken, they want a refund, or they cannot cancel
Investigating duplicate subscriptions, accidental charges, failed renewals, or churn risk
Reviewing plan mix, active subscriptions, yearly vs monthly conversion, or team-seat confusion
Creating or validating a billing portal flow
Auditing support complaints that touch subscriptions, invoices, refunds, or payment methods

Preferred Tool Surface

Use connected billing tools such as Stripe first
Use email, GitHub, or issue trackers only as supporting evidence
Prefer hosted billing/customer portals over custom account-management code when the platform already provides the needed controls