Customer Billing Ops

This handles the messy human side of subscription billing: duplicate charges, failed renewals, refund requests, customers who can't cancel. It walks you through identifying the customer across Stripe and support channels, classifying the issue (accidental duplicate versus legitimate multi-seat purchase), then taking the safest reversible action before you refund anything. The workflow is opinionated about checking for self-serve fixes first and explicitly separating customer remediation from product gaps. If you're doing billing support and need to answer "who is this, what broke, what's the safest fix, and what do I tell them," this gives you a structured playbook instead of winging it every time.

skills.sh installs: 5.4K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --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