Customer Billing Ops
Operate customer billing workflows such as subscriptions, refunds, churn triage, billing-portal recovery, and plan analysis using connected billing tools like Stripe. Use when the user needs to help a customer, inspect subscription state, or manage revenue-impacting billing operations.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Customer Billing Ops when an AI agent needs a reusable SKILL.md workflow for this job: Operate customer billing workflows such as subscriptions, refunds, churn triage, billing-portal recovery, and plan analysis using connected billing tools like Stripe. Use when the user needs to help a customer, inspect subscription state, or manage revenue-impacting billing operations.
When not to use it
Skip Customer Billing Ops when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/customer-billing-ops # Save SKILL.md to ~/.claude/skills/customer-billing-ops/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/customer-billing-ops/SKILL.md. For a shared project, commit the folder at .claude/skills/customer-billing-ops/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Customer Billing Ops skill for this task: Customer says billing is broken, they want a refund, or they cannot cancel. Confirm any required inputs or files before making changes.
What supports this recommendation?
74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 82/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# 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
- "The right fix is a billing portal, not a custom dashboard yet" - "This looks like duplicate personal checkout, not a real team-seat purchase" - "Refund one duplicate charge, keep the remaining active subscription, then convert the customer to org billing later if needed"
Intended uses
- 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
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.