Finance Billing Ops
Evidence-first billing truth: revenue snapshots, pricing reality checks, and code-backed answers on what your billing actually does.
- What
- Evidence-first billing truth: revenue snapshots, pricing reality checks, and code-backed answers on what your billing actually does.
- Cost
- Free
- Needs
- Use "finance-billing-ops" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: an operator-grade billing workflow for founders who want the truth about their money, not generic payments advice. It starts from the freshest billing evidence (live data preferred; snapshots get an explicit timestamp), normalizes the picture (paid sales, active subscriptions, failed checkouts, refunds, disputes, duplicate subscriptions), then separates three things most tools conflate: the customer incident (duplicate checkout? broken self-serve? failed payment?), the product truth (does team billing really exist in code? are seats actually counted? does the site overstate current behavior?), and the recommendation. The discipline is evidence-first: never say "per seat" unless the entitlement path enforces it, never infer team billing from marketing language, never compare competitor pricing from memory when current evidence is available. Output follows a fixed shape: snapshot, customer impact, product truth, decision (refund, preserve, convert, no-op), and the exact product or backlog gap to build next. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: it references sibling ECC skills (customer-billing-ops, github-ops, verification-loop) for full depth on remediation and code inspection; standalone it works as a rigorous operator checklist, but pair it with those for the complete loop. It answers from the data you give it, so connect your billing source (Stripe dashboard export, for example) before asking for a snapshot. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseCommunity-built. Skill Harbor doesn't audit code — review the source before installing.
Use "finance-billing-ops" with your Muse. Prerequisites: the Muse app (mobile or web). No installation, no API key, no extra account. Have your billing data handy (Stripe dashboard export, subscription list, or the specific customer case). 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/finance-billing-ops/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Billing truth check: [your question, e.g. is our per-seat billing real in code, or diagnose this duplicate charge]. Data: [paste the export or describe the case, with timestamps]." 3. Ask Muse to keep the three layers separate in its answer: revenue fact, customer impact, code-backed product truth, then the decision. Tip: state whether your data is live or a snapshot with its timestamp. The skill's first rule is distinguishing the two, and it will hold you to it. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste secrets or API keys into it (paste exports with keys redacted), and review anything Muse proposes before it acts.
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.