Customer Billing Ops
Operate real customer billing workflows with Muse: identify the customer, classify the issue, apply the safest fix for subscriptions, refunds and churn, from connected tools like Stripe.
- What
- Operate real customer billing workflows with Muse: identify the customer, classify the issue, apply the safest fix for subscriptions, refunds and churn, from connected tools like Stripe.
- Cost
- Free
- Needs
- Use "Customer Billing Ops" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: use this skill for real customer operations, not generic payment API design. The goal is to help the operator answer four questions: who is this customer, what happened, what is the safest fix, and what follow-up should be sent. Workflow: identify the customer cleanly from the strongest identifier available (customer email, Stripe customer ID, subscription ID, invoice ID), returning a concise identity summary of active and canceled subscriptions, invoices, and obvious anomalies like duplicate active subscriptions; classify the issue before touching anything, distinguishing accidental duplicate purchases, deliberate multi-seat or team purchases, broken product or unmet value, failed or incomplete checkouts, and cancellations caused by missing self-serve controls; apply the safest fix, verifying the contract shape for annual plans, team plans and prorated states; then define the follow-up. Guardrails: prefer connected billing tools like Stripe first and hosted billing portals over custom account code; never expose secret keys, full card details or unnecessary customer PII in responses; do not refund blindly, classify first. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: this needs connected billing tools to be useful; judgment stays human, the skill classifies and recommends but you approve the refund. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Customer Billing Ops" with your Muse. Prerequisites: access to connected billing tools (e.g. Stripe dashboard or API). Never paste secret keys, full card numbers or unnecessary customer PII in chat. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/customer-billing-ops/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "A customer says billing is broken: [email or subscription ID]" or "Triage this churn risk: [customer email]." 3. Work through the workflow with Muse: identify, classify, safest fix, follow-up. You approve any refund before it happens. Tip: for duplicate-subscription complaints, always check whether it is an accidental double purchase or a deliberate multi-seat setup before refunding; the fix is different. Safety: a skill is plain-text instructions; it runs nothing by itself. Keep secrets out of chat; use hosted billing portals over custom account code whenever possible.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.