Back to browse

affaan-m/ECC

finance-billing-ops

面向ECC的以证据为先的收入、定价、退款、团队计费和计费模型真相工作流。当用户需要销售快照、定价比较、重复收费诊断或基于代码的计费现实而非通用支付建议时使用。

54Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/finance-billing-ops"

Quick start

Start using it in three steps

Install it or open the source, trigger it with a clear task, then follow the source workflow.

1

Install the Skill

npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/finance-billing-ops"
2

Describe the task

Use finance-billing-ops to help me with: [describe your task]. Before you begin, tell me what input you need, the steps you will follow, and the expected output.

3

Follow the workflow

No structured workflow was detected; follow the original SKILL.md below.

Continue to the workflow

Direct answers

Answers to review before you install

What is finance-billing-ops?

面向ECC的以证据为先的收入、定价、退款、团队计费和计费模型真相工作流。当用户需要销售快照、定价比较、重复收费诊断或基于代码的计费现实而非通用支付建议时使用。

Who should use finance-billing-ops?

It is relevant to workflows involving the tasks described in the upstream documentation.

How do you install finance-billing-ops?

SkillSignal detected this source-specific command: npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/finance-billing-ops". Inspect the repository and command before running it.

Which Agent platforms does it support?

The upstream source does not declare a dedicated Agent platform.

What permissions or risks should you review?

No obvious permission action was detected by the static rules. This is not proof that the Skill is safe.

What are the current evidence limits?

This page combines upstream documentation with deterministic repository, quality, and static-risk signals. It is not described as a manual test or security review.

SkillSignal brief

Decide whether it fits your work first

面向ECC的以证据为先的收入、定价、退款、团队计费和计费模型真相工作流。当用户需要销售快照、定价比较、重复收费诊断或基于代码的计费现实而非通用支付建议时使用。

Useful in these contexts

Not yet included in a workflow collection

Core capabilities

Repository stars
234,327
Repository forks
35,711
Quality
54/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

54/100
Documentation15/30
Specificity7/25
Maintenance20/20
Trust signals12/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

finance-billing-ops by affaan-m

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.

finance-billing-ops by affaan-m

ECCの証拠優先の収益、価格設定、返金、チーム請求、請求モデルの実態確認ワークフロー。ユーザーが販売スナップショット、価格比較、重複請求の診断、または汎用的な支払いアドバイスではなくコードに裏付けられた請求の実態を必要とする場合に使用します。

ab-testing by coreyhaines31

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

churn-prevention by coreyhaines31

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

design-intelligence by event4u-app

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min

财务计费运营

当用户想要了解资金、定价、退款、团队席位逻辑，或产品是否真的如网站和销售文案所暗示的那样运作时，使用此技能。

此技能比 customer-billing-ops 更广泛。该技能用于客户补救。此技能用于运营者真相：收入状态、定价决策、团队计费以及基于代码的计费行为。

技能栈

在相关时，将这些 ECC 原生技能引入工作流程：

  • customer-billing-ops 用于特定客户的补救和跟进
  • research-ops 当竞争对手定价或当前市场证据重要时
  • market-research 当答案应以定价建议结束时
  • github-ops 当计费真相取决于兄弟仓库中的代码、待办事项或发布状态时
  • verification-loop 当答案取决于验证结账、席位处理或权限行为时

使用时机

  • 用户询问 Stripe 销售额、退款、MRR 或近期客户活动
  • 用户询问团队计费、按席位计费或配额叠加在代码中是否真实存在
  • 用户想要竞争对手定价比较或定价模型基准
  • 问题混合了收入事实与产品实现真相

护栏

  • 区分实时数据与保存的快照
  • 区分：
    • 收入事实
    • 客户影响
    • 基于代码的产品真相
    • 建议
  • 除非实际的权限路径强制执行，否则不要说“按席位”
  • 不要假设重复订阅意味着重复价值

工作流程

1. 从最新的计费证据开始

优先使用实时计费数据。如果数据不是实时的，请明确说明快照时间戳。

规范化视图：

  • 已付款销售
  • 活跃订阅
  • 失败或不完整的结账
  • 退款
  • 争议
  • 重复订阅

2. 将客户事件与产品真相分开

如果问题是针对特定客户的，请先分类：

  • 重复结账
  • 真实的团队意图
  • 自助服务控制失效
  • 未满足的产品价值
  • 付款失败或设置不完整

然后将其与更广泛的产品问题分开：

  • 团队计费真的存在吗？
  • 席位是否实际被计数？
  • 结账数量是否会改变权限？
  • 网站是否夸大了当前行为？

3. 检查基于代码的计费行为

如果答案取决于实现真相，请检查代码路径：

  • 结账
  • 定价页面
  • 权限计算
  • 席位或配额处理
  • 安装与用户使用逻辑
  • 计费门户或自助管理支持

4. 以决策和产品差距结束

报告：

  • 销售快照
  • 问题诊断
  • 产品真相
  • 建议的运营者行动
  • 产品或待办事项差距

输出格式

快照
- 时间戳
- 收入 / 订阅 / 异常

客户影响
- 谁受影响
- 发生了什么

产品真相
- 代码实际执行的操作
- 网站或销售文案声称的内容

决策
- 退款 / 保留 / 转化 / 无操作

产品差距
- 需要构建或修复的具体后续事项

陷阱

  • 不要将失败的尝试与净收入混为一谈
  • 不要仅从营销语言推断团队计费
  • 在有当前证据可用时，不要凭记忆比较竞争对手定价
  • 不要在没有对问题进行分类的情况下，直接从诊断跳到退款

验证

  • 答案包含实时数据声明或快照时间戳
  • 产品真相声明有代码支持
  • 客户影响与更广泛的定价/产品结论被清晰区分
Source repo
affaan-m/ECC
Skill path
docs/zh-CN/skills/finance-billing-ops/SKILL.md
Commit SHA
4e973d3eaf92
Repository license
MIT
Data collected