customer-billing-ops

Investigate Stripe subscription and invoice states to select reversible remediation.

Updated Sep 13, 2025
One-click install
npx skills add https://github.com/llmh333/employee_management_spring --skill customer-billing-ops-llmh333
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: customer-billing-ops
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/customer-billing-ops
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill customer-billing-ops-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Customer billing issues create urgent revenue and trust problems, and support operators need a reliable way to investigate subscription and invoice states and take the safest reversible action without exposing sensitive payment details.

Core Features & Use Cases

  • Issue identification & classification: Classifies cases like duplicate subscriptions, failed payments, incomplete checkout, missing self-serve controls, or product/value trust breaks.
  • Safe workflow execution: Guides the operator to prefer self-serve restoration first, then resolve duplicate or broken billing state, and only refund when the specific charge/duplicate is clearly identified.
  • Operator-ready handoff: Produces a structured output including customer identity summary, billing state anomalies, decision rationale, action taken, revenue impact, follow-up text, and any product gaps for backlog.

Quick Start

Use customer-billing-ops when you need to triage a customer request involving subscriptions, invoices, refunds, billing portal recovery, or churn risk based on Stripe-connected billing data.

Frequently Asked Questions about customer-billing-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot duplicate subscriptions and failed renewals in Stripe?

To troubleshoot duplicate subscriptions and failed renewals, classify the billing issue first, investigate the Stripe invoice states, and apply a safe reversible remediation like self-serve restoration or targeted cancellation.

What is the safest way to process customer refunds for incomplete checkouts?

The safest way to process customer refunds for incomplete checkouts is to identify the specific duplicate charge clearly before acting, preferring self-serve restoration first and only refunding when the exact anomaly is confirmed.

Can I use this workflow for churn triage and billing portal recovery?

Yes, you can use this workflow for churn triage and billing portal recovery by investigating subscription states and applying guardrails to select the safest reversible action without exposing sensitive payment details.

How do I audit invoices and identify product gaps during billing operations?

To audit invoices and identify product gaps during billing operations, investigate the connected billing source, classify the issue, execute a safe workflow, and output an operator handoff with identified product gaps for the backlog.

What is the best way to handle customer billing issues without exposing payment details?

The best way to handle customer billing issues without exposing payment details is to investigate subscription and invoice states through connected sources like Stripe and apply guardrails for refunds and cancellations.

When should I not use automated refunds for subscription billing problems?

You should not use automated refunds for subscription billing problems when the specific charge or duplicate cannot be clearly identified, as the workflow prefers self-serve restoration and safe reversible actions first.