$ loading_
Verify revenue, pricing, refunds, and billing truth with evidence-backed answers.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "finance-billing-ops" skill from askskill: 1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/finance-billing-ops/SKILL.md 2. Save it as ~/.claude/skills/finance-billing-ops/SKILL.md 3. Reload skills and tell me it's ready
Using the available billing, order, and refund records, create a weekly sales snapshot with gross revenue, net revenue, refund amount, number of paying teams, and key anomalies with data sources.
A sales and revenue summary with metrics, anomaly notes, and supporting evidence sources.
Compare the actual billing differences among the Basic, Pro, and Team plans, including monthly versus annual pricing, seat rules, overage charges, and which users fit each plan best.
A structured pricing comparison covering rule differences, fit by user type, and likely confusion points.
A user reports being charged twice. Use billing events, subscription status, and payment records to determine whether a duplicate charge occurred, explain why, and provide an evidence-backed refund conclusion.
A duplicate-charge diagnosis with a timeline, cause assessment, and refund recommendation.
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.
Pull these ECC-native skills into the workflow when relevant:
customer-billing-ops for customer-specific remediation and follow-upresearch-ops when competitor pricing or current market evidence mattersmarket-research when the answer should end in a pricing recommendationgithub-ops when the billing truth depends on code, backlog, or release state in sibling reposverification-loop when the answer depends on proving checkout, seat handling, or entitlement behaviorPrefer live billing data. If the data is not live, state the snapshot timestamp explicitly.
Normalize the picture:
If the question is customer-specific, classify first:
Then separate that from the broader product question:
If the answer depends on implementation truth, inspect the code path:
Report:
SNAPSHOT
- timestamp
- revenue / subscriptions / anomalies
CUSTOMER IMPACT
- who is affected
- what happened
PRODUCT TRUTH
- what the code actually does
- what the website or sales copy claims
DECISION
- refund / preserve / convert / no-op
PRODUCT GAP
- exact follow-up item to build or fix
Build testable Swift code with protocol-based dependency injection and focused mocks.
Learn Rust testing patterns and TDD to improve code quality and reliability.
Record polished web app UI demo videos for walkthroughs, tutorials, and showcases.
Check live messages, recover recent codes, and verify the exact source inspected.
Review Solidity AMM, liquidity pool, and swap flow security risks.
Create, configure, and refine Hookify rules and syntax patterns.
Audit ECC Tools cost anomalies and trace misuse, leakage, and duplicate jobs.
Look up orders, check returns, handle billing, and escalate support cases.
Manage B2B SaaS billing, subscriptions, and quotes in one tool.
Check agent quotas, usage, invoices, receipts, and earnings in one place.
Forecast 30/60/90-day cash flow with risks from accounting and payment data.
Get electrical pricing, cable sizing, and profit analysis for US construction estimates.