Customer Billing Ops
Triage live customer billing issues—subscriptions, refunds, portal access, and plan mix—using Stripe-connected tools with safe operator guardrails.
Overview
Customer-billing-ops is an agent skill for the Operate phase that runs Stripe-grounded subscription, refund, and portal-recovery workflows for real customer tickets.
Install
npx skills add https://github.com/affaan-m/everything-claude-code --skill customer-billing-opsWhat is this skill?
- Stripe-first connected billing tools for subscriptions, invoices, and refunds
- Classifies duplicate purchase vs failed renewal vs portal confusion before acting
- Guardrails: no secret keys, full PAN, or unnecessary PII in agent replies
- Supports churn triage, plan mix review, and billing-portal recovery flows
- Uses email, GitHub, or issue trackers only as supporting evidence
Adoption & trust: 3.2k installs on skills.sh; 210k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
A customer says billing is broken or they were charged twice and you need a safe Stripe-backed triage path without leaking secrets.
Who is it for?
Live SaaS operators with Stripe (or connected billing) handling refunds, cancellations, and subscription investigations.
Skip if: Greenfield payment architecture, pricing strategy before launch, or teams without connected billing tools and audit discipline.
When should I use this skill?
Customer says billing is broken, wants a refund, cannot cancel, or you need subscription state, refunds, churn triage, portal recovery, or plan-mix analysis with connected billing tools.
What do I get? / Deliverables
You get a classified issue, recommended safest fix, and customer follow-up grounded in live subscription and invoice state—not a blind refund.
- Issue classification and safest remediation plan
- Customer-facing follow-up guidance
- Optional portal or subscription state summary without exposing secrets
Recommended Skills
Journey fit
Revenue-impacting customer fixes belong on the Operate shelf once the product is live and money is moving. Iterate covers recurring support loops: classify the incident, apply the safest billing change, and document follow-up—not one-time launch setup.
How it compares
Operator runbook skill—not a substitute for designing your own billing API or pricing model from scratch.
Common Questions / FAQ
Who is customer-billing-ops for?
Solo and indie SaaS operators who use Claude with connected Stripe tools to resolve subscriber billing and churn incidents.
When should I use customer-billing-ops?
Use it in Operate when a customer cannot cancel, disputes a charge, hits a failed renewal, or when you audit plan mix and portal flows after launch.
Is customer-billing-ops safe to install?
It instructs handling of live billing and PII—review the Security Audits panel on this Prism page and restrict tool access to least-privilege Stripe keys.
SKILL.md
READMESKILL.md - Customer Billing Ops
# 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 ## Guardrails - Never expose secret keys, full card details, or unnecessary customer PII in the response - Do not refund blindly; first classify the issue - Distinguish among: - accidental duplicate purchase - deliberate multi-seat or team purchase - broken product / unmet value - failed or incomplete checkout - cancellation due to missing self-serve controls - For annual plans, team plans, and prorated states, verify the contract shape before taking action ## Workflow ### 1. Identify the customer cleanly Start from the strongest identifier available: - customer email - Stripe customer ID - subscription ID - invoice ID - GitHub username or support email if it is known to map back to billing Return a concise identity summary: - customer - active subscriptions - canceled subscriptions - invoices - obvious anomalies such as duplicate active subscriptions ### 2. Classify the issue Put the case into one bucket before acting: | Case | Typical action | |------|----------------| | Duplicate personal subscription | cancel extras, consider refund | | Real multi-seat/team intent | preserve seats, clarify billing model | | Failed payment / incomplete checkout | recover via portal or update payment method | | Missing self-serve controls | provide portal, cancellation path, or invoice access | | Product failure or trust break | refund, apologize, log product issue | ### 3. Take the safest reversible action first Preferred order: 1. restore self-serve management 2. fix duplicate or broken billing state 3. refund only the affected charge or duplicate 4. document the reason 5. send a short customer follow-up If the fix requires product work, separate: - customer remediation now - product bug / workflow gap for backlog ### 4. Check operator-side product gaps If the customer pain comes from a missing operator surface, call it out explicitly. Common examples: - no billing portal - no usage/rate-limit visibility - no plan/seat explanation - no cancellation flow - no duplicate-subscription guard Treat those as ECC or website follow-up items, not just support incidents. ### 5. Produce the operator handoff End with: - customer state summary - action taken - revenue impact - follow-up text to send - product or backlog issue to create ## Output Format Use this structure: ```text CUSTOMER - name / email - relevant account identifiers BILLING STATE - active subscriptions - invoice or renewal state - anomalies DECISION - issue classification - why this action is correct ACTION TAKEN - refund / cancel / portal / no-op FOLLOW-UP - short customer message PRODUCT GAP - what should be fixed in the product or website ``` ## Examples of Good Recommendations