Finance Billing Ops

This is for when you need to separate what your billing system actually does from what your marketing says it does. It walks you through live Stripe data, duplicate subscriptions, team seat logic, and then cross-checks the code to see if per-seat pricing or quota stacking is real or just aspirational. The output format is tight: snapshot, customer impact, product truth, decision, and product gap. It's explicitly broader than customer support remediation. You use it when the question mixes revenue facts with implementation reality, like whether checkout quantity actually changes entitlements or if you're refunding someone for a duplicate charge that gave them nothing.

skills.sh installs: 5.4K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill finance-billing-ops --agent claude-code

Installs into .claude/skills of the current project.

Files

Finance Billing Ops

Use this when the user wants to understand money, pricing, refunds, team-seat logic, or whether the product actually behaves the way the website and sales copy imply.

This is broader than customer-billing-ops. That skill is for customer remediation. This skill is for operator truth: revenue state, pricing decisions, team billing, and code-backed billing behavior.

Skill Stack

Pull these ECC-native skills into the workflow when relevant:

customer-billing-ops for customer-specific remediation and follow-up
research-ops when competitor pricing or current market evidence matters
market-research when the answer should end in a pricing recommendation
github-ops when the billing truth depends on code, backlog, or release state in sibling repos
verification-loop when the answer depends on proving checkout, seat handling, or entitlement behavior