Manages customer billing ops: subscriptions, refunds, churn triage, portal recovery, plan analysis using Stripe. For helping customers, inspecting subs, revenue-impacting actions.
From everything-claude-codenpx claudepluginhub burgebj/claude_everythingThis skill uses the workspace's default tool permissions.
Orchestrates large features via RFC decomposition into verifiable work units in a multi-agent DAG, with quality gates, merge queues, complexity tiers, and recovery. Use for complex, multi-pass tasks.
Provides decision framework and Python code for hybrid regex-LLM parsing of structured text like quizzes, forms, and invoices—prioritize regex, LLM for edge cases.
Guides NCR investigations, root cause analysis, CAPA management, SPC interpretation, and supplier quality control in FDA/IATF16949/AS9100 regulated manufacturing.
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?
Start from the strongest identifier available:
Return a concise identity summary:
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 |
Preferred order:
If the fix requires product work, separate:
If the customer pain comes from a missing operator surface, call it out explicitly. Common examples:
Treat those as ECC or website follow-up items, not just support incidents.
End with:
Use this structure:
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