Finance Billing Ops

When you need to separate billing reality from marketing copy, this pulls Stripe snapshots, diagnoses duplicate charges or failed checkouts, and checks whether "per-seat billing" actually exists in the code or just lives on the pricing page. It's built for operators who need to answer refund questions, compare competitor pricing with evidence, or figure out if team billing is real or vaporware. The workflow forces you to timestamp your data, separate customer incidents from product gaps, and end with a concrete decision plus what needs to get built. Honestly most useful when sales numbers don't match expectations and you need to know if it's a product lie, a broken flow, or just confused customers.

skills.sh installs: 3.7K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --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