Agent skill · Business & Finance

finance-billing-ops

Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ecc. Use when the user wants a sales snapshot, pricing comparison, duplicate-charge diagnosis, or code-backed billing reality instead of generic payments advice.

mturacgithub.com/mturacGitHub ↗
codexcopilotcursorMIT
Install
npx skills add mturac/everything-openai-codex --skill finance-billing-ops --agent codex

Same command for any agent — swap --agent for claude-code, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/finance-billing-ops/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 84
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 ## When to Use - user asks for Stripe sales, refunds, MRR, or recent customer activity - user asks whether team billing, per-seat billing, or quota stacking is real in code - user wants competitor pricing comparisons or pricing-model benchmarks - the question mixes revenue facts with product implementati

What's inside
Steps it walks through
  1. Skill Stack
  2. When to Use
  3. Guardrails
  4. Workflow
  5. 1. Start from the freshest billing evidence
  6. 2. Separate customer incidents from product truth
  7. 3. Inspect code-backed billing behavior
  8. 4. End with a decision and product gap
  9. Output Format
  10. Pitfalls
  11. Verification
More from everything-openai-codex
All skills →
About this skill
What does the finance-billing-ops skill do?

Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ecc. Use when the user wants a sales snapshot, pricing comparison, duplicate-charge diagnosis, or code-backed billing reality instead of generic payments advice.

How do I install it?

Run `npx skills add mturac/everything-openai-codex --skill finance-billing-ops --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mturac/everything-openai-codex, a repository with 84 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going