finance-billing-ops

Analyze Stripe revenue data and inspect code to verify billing behavior.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/luongldptit/move-ticket --skill finance-billing-ops-luongldptit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finance-billing-ops
Source: https://github.com/luongldptit/move-ticket/tree/main/.agent/skills/finance-billing-ops
Command: npx skills add https://github.com/luongldptit/move-ticket --skill finance-billing-ops-luongldptit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of relying on unverified marketing claims or generic payments advice for ECC's billing and revenue operations, delivering accurate, evidence-based answers about actual product behavior, revenue state, and pricing logic.

Core Features & Use Cases

  • Live Revenue Snapshots: Pull current or timestamped Stripe data for sales, active subscriptions, refunds, disputes, and MRR to get an accurate view of revenue health.
  • Code-Backed Billing Validation: Verify if team billing, per-seat counting, quota stacking, and checkout entitlement logic actually function as marketed by inspecting implementation code paths.
  • Billing Incident Diagnosis: Classify and resolve customer-specific billing issues like duplicate charges, failed payments, or unmet product value while separating individual incidents from broader product gaps.
  • Use Case: If a user asks whether ECC's team billing actually enforces per-seat limits, this skill combines live billing data and code inspection to confirm the actual behavior instead of relying on sales copy.

Quick Start

Use the finance-billing-ops skill to pull a current Stripe sales snapshot for ECC and verify if team billing per-seat limits are enforced in the checkout code.

Frequently Asked Questions about finance-billing-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify if team billing per-seat limits are actually enforced in checkout code?

Diagnose duplicate charges by classifying the specific customer billing incident against live Stripe sales data and refund records. This separates individual duplicate charge incidents from broader product gaps to deliver actionable resolution recommendations.

What is the best way to get a live revenue snapshot from Stripe?

Compare competitor pricing models by analyzing code-backed pricing validation against actual implementation behavior. This verifies if pricing logic functions as marketed and delivers evidence-based pricing comparison rather than relying on sales copy.

Can I diagnose failed payments and unmet product value using billing operations data?

Yes, you can diagnose failed payments and unmet product value by classifying customer billing incidents using live Stripe data. This separates individual failures from broader product gaps to provide actionable operator recommendations.

Why does marketing claim team billing works but live revenue data shows discrepancies?

Marketing claims may diverge from live revenue data due to unverified implementation behavior. Verify code-backed billing logic against actual Stripe subscription states to identify gaps between marketed team seat functionality and real product behavior.

Does this approach work for separating individual billing incidents from broader product gaps?

Yes, this approach works for separating individual billing incidents from broader product gaps by classifying customer-specific issues against live revenue snapshots. It combines code inspection with billing evidence to isolate individual errors from systemic flaws.