affaan-m/ecc

finance-billing-ops

Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ECC.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/affaan-m/ecc --skill finance-billing-ops

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

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 implementation truth

Guardrails

  • distinguish live data from saved snapshots
  • separate:
  • revenue fact
  • customer impact
  • code-backed product truth
  • recommendation
  • do not say "per seat" unless the actual entitlement path enforces it
  • do not assume duplicate subscriptions imply duplicate value

Workflow

1. Start from the freshest billing evidence

Prefer live billing data. If the data is not live, state the snapshot timestamp explicitly.

Normalize the picture:

  • paid sales
  • active subscriptions
  • failed or incomplete checkouts
  • refunds
  • disputes
  • duplicate subscriptions

2. Separate customer incidents from product truth

If the question is customer-specific, classify first:

  • duplicate checkout
  • real team intent
  • broken self-serve controls
  • unmet product value
  • failed payment or incomplete setup

Then separate that from the broader product question:

  • does team billing really exist?
  • are seats actually counted?
  • does checkout quantity change entitlement?
  • does the site overstate current behavior?

3. Inspect code-backed billing behavior

If the answer depends on implementation truth, inspect the code path:

  • checkout
  • pricing page
  • entitlement calculation
  • seat or quota handling
  • installation vs user usage logic
  • billing portal or self-serve management support

4. End with a decision and product gap

Report:

  • sales snapshot
  • issue diagnosis
  • product truth
  • recommended operator action
  • product or backlog gap

Output Format

text
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

Pitfalls

  • do not conflate failed attempts with net revenue
  • do not infer team billing from marketing language alone
  • do not compare competitor pricing from memory when current evidence is available
  • do not jump from diagnosis straight to refund without classifying the issue

Verification

  • the answer includes a live-data statement or snapshot timestamp
  • product-truth claims are code-backed
  • customer-impact and broader pricing/product conclusions are separated cleanly

按任务相关推荐

来自同一仓库

更多 Skills

全部 Skills
affaan-m
社区

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

24小时安装量
489
GitHub Stars
30.8万
最近更新
11月20日
affaan-m
社区

search-first

Research-before-coding workflow: search npm/PyPI, MCP servers, skills, and GitHub for existing tools before writing custom code, then adopt, extend, or build. Launches the researcher agent for non-trivial needs. Use when starting a feature, adding a dependency or integration, or about to write a utility that may already exist.

1小时安装量
5
GitHub Stars
30.8万
最近更新
11月20日
affaan-m
社区

browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

1小时安装量
2
GitHub Stars
30.8万
最近更新
11月20日
affaan-m
社区

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

1小时安装量
2
GitHub Stars
30.8万
最近更新
11月20日