Best fit
- 使用 Stripe 等连接计费工具操作客户计费工作流，例如订阅、退款、流失分类、计费门户恢复和计划分析。当用户需要帮助客户、检查订阅状态或管理影响收入的计费操作时使用。
affaan-m/ECC
customer-billing-ops
使用 Stripe 等连接计费工具操作客户计费工作流，例如订阅、退款、流失分类、计费门户恢复和计划分析。当用户需要帮助客户、检查订阅状态或管理影响收入的计费操作时使用。
62Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/customer-billing-ops"Automated source guide
Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Reorganized from the pinned upstream SKILL.md
Turn customer-billing-ops's source instructions into a guide you can follow
According to the pinned SKILL.md from affaan-m/ECC: 此技能用于真实的客户运营操作，而非通用的支付 API 设计。
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/customer-billing-ops"Bring this context
- A concrete task that matches the documented purpose of customer-billing-ops.
- The files, examples, or context the task depends on.
- Your constraints, target environment, and definition of done.
Expected outputs
- A result that follows the pinned customer-billing-ops instructions.
- A concise record of assumptions, inputs used, and unresolved questions.
- A final check against the source workflow and relevant permission signals.
Key source sections
Read customer-billing-ops through these 5 source sections
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
使用场景
客户反馈计费异常、要求退款或无法取消订阅 调查重复订阅、意外扣费、续费失败或流失风险 审查套餐组合、活跃订阅、年付与月付转换、或团队席位混淆 创建或验证计费门户流程 审计涉及订阅、发票、退款或支付方式的支持投诉
客户反馈计费异常、要求退款或无法取消订阅调查重复订阅、意外扣费、续费失败或流失风险审查套餐组合、活跃订阅、年付与月付转换、或团队席位混淆
首选工具界面
优先使用 Stripe 等关联计费工具 仅将邮件、GitHub 或问题追踪器作为辅助证据 当平台已提供必要控制功能时，优先使用托管计费/客户门户而非自定义账户管理代码
优先使用 Stripe 等关联计费工具仅将邮件、GitHub 或问题追踪器作为辅助证据当平台已提供必要控制功能时，优先使用托管计费/客户门户而非自定义账户管理代码
安全边界
切勿在回复中暴露密钥、完整卡号或不必要的客户个人身份信息 不要盲目退款；首先对问题进行归类 区分以下情况： 意外重复购买 有意的多席位或团队购买 产品故障/价值未兑现 结账失败或不完整 因缺少自助控制功能导致的取消 对于年付方案、团队方案及按比例计费状态，在操作前需核实合同结构
切勿在回复中暴露密钥、完整卡号或不必要的客户个人身份信息不要盲目退款；首先对问题进行归类区分以下情况：
工作流程
客户邮箱 Stripe 客户 ID 订阅 ID 发票 ID 已知可关联到计费的 GitHub 用户名或支持邮箱
客户邮箱Stripe 客户 ID订阅 ID
1. 清晰识别客户身份
客户邮箱 Stripe 客户 ID 订阅 ID 发票 ID 已知可关联到计费的 GitHub 用户名或支持邮箱
客户邮箱Stripe 客户 ID订阅 ID
SkillSignal prompt templates
Provide the task, context, and acceptance criteria
These prompts were written by SkillSignal from the source structure; they are not upstream text.
Task-start prompt
Confirm source fit, inputs, and outputs before acting.
Use customer-billing-ops to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.
Source-guided execution
Make the Agent explicitly follow the key extracted sections.
Apply the pinned customer-billing-ops source to [task]. Pay particular attention to these source sections: “使用场景”, “首选工具界面”, “安全边界”, “工作流程”, “1. 清晰识别客户身份”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].
Result-review prompt
Check omissions, permissions, and source drift before delivery.
Review the current customer-billing-ops result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.
Output checklist
Verify each item before delivery
The task matches the purpose documented in the SKILL.md.
The source section “使用场景” has been checked.
The source section “首选工具界面” has been checked.
The source section “安全边界” has been checked.
The source section “工作流程” has been checked.
Inputs, constraints, and acceptance criteria are explicit.
Unverified facts, compatibility, and outcome claims are clearly marked.
Any file, command, network, or data action has been reviewed.
Choose a different workflow
When another Skill is the better fit
customer-billing-ops
Operate customer billing workflows such as subscriptions, refunds, churn triage, billing-portal recovery, and plan analysis using connected billing tools like Stripe. Use when the user needs to help a customer, inspect subscription state, or manage revenue-impacting billing operations.
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailcustomer-billing-ops
Stripeなどの接続された請求ツールを使用して、サブスクリプション、返金、チャーントリアージ、請求ポータルの回復、プラン分析などの顧客請求ワークフローを操作します。顧客を助けたい、サブスクリプション状態を検査したい、または収益に影響する請求操作を管理したい場合に使用します。
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailab-testing
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
A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.
Open source detailFAQ
What does customer-billing-ops do?
此技能用于真实的客户运营操作，而非通用的支付 API 设计。
How do I start using customer-billing-ops?
The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/customer-billing-ops". Inspect the command and pinned source before running it.
Which Agent platforms does it declare?
No dedicated Agent platform is declared in the pinned source record.
Repository stars
234,327
Repository forks
35,711
Quality
62/100
Source repository last pushed
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Documentation19/30
Specificity11/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.
customer-billing-ops by affaan-m
Operate customer billing workflows such as subscriptions, refunds, churn triage, billing-portal recovery, and plan analysis using connected billing tools like Stripe. Use when the user needs to help a customer, inspect subscription state, or manage revenue-impacting billing operations.
customer-billing-ops by affaan-m
Stripeなどの接続された請求ツールを使用して、サブスクリプション、返金、チャーントリアージ、請求ポータルの回復、プラン分析などの顧客請求ワークフローを操作します。顧客を助けたい、サブスクリプション状態を検査したい、または収益に影響する請求操作を管理したい場合に使用します。
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
客户计费运营
此技能用于真实的客户运营操作，而非通用的支付 API 设计。
目标是帮助运营人员回答：客户是谁、发生了什么、最安全的修复方案是什么、以及后续应发送什么跟进内容。
使用场景
- 客户反馈计费异常、要求退款或无法取消订阅
- 调查重复订阅、意外扣费、续费失败或流失风险
- 审查套餐组合、活跃订阅、年付与月付转换、或团队席位混淆
- 创建或验证计费门户流程
- 审计涉及订阅、发票、退款或支付方式的支持投诉
首选工具界面
- 优先使用 Stripe 等关联计费工具
- 仅将邮件、GitHub 或问题追踪器作为辅助证据
- 当平台已提供必要控制功能时，优先使用托管计费/客户门户而非自定义账户管理代码
安全边界
- 切勿在回复中暴露密钥、完整卡号或不必要的客户个人身份信息
- 不要盲目退款；首先对问题进行归类
- 区分以下情况：
- 意外重复购买
- 有意的多席位或团队购买
- 产品故障/价值未兑现
- 结账失败或不完整
- 因缺少自助控制功能导致的取消
- 对于年付方案、团队方案及按比例计费状态，在操作前需核实合同结构
工作流程
1. 清晰识别客户身份
从最可靠的标识符入手：
- 客户邮箱
- Stripe 客户 ID
- 订阅 ID
- 发票 ID
- 已知可关联到计费的 GitHub 用户名或支持邮箱
返回简洁的身份摘要：
- 客户
- 活跃订阅
- 已取消订阅
- 发票
- 明显异常（如重复的活跃订阅）
2. 对问题进行分类
在操作前将案例归入一个类别：
| 案例 | 典型操作 |
|---|---|
| 重复的个人订阅 | 取消多余订阅，考虑退款 |
| 真实的多席位/团队意图 | 保留席位，澄清计费模式 |
| 支付失败/结账不完整 | 通过门户恢复或更新支付方式 |
| 缺少自助控制功能 | 提供门户、取消路径或发票访问权限 |
| 产品故障或信任破裂 | 退款、道歉、记录产品问题 |
3. 优先采取最安全的可逆操作
推荐顺序：
- 恢复自助管理功能
- 修复重复或异常的计费状态
- 仅对受影响的扣费或重复项进行退款
- 记录原因
- 发送简短的客户跟进信息
若修复需要产品工作，需区分：
- 当前客户补救措施
- 待办事项中的产品缺陷/工作流缺口
4. 检查运营端产品缺口
若客户痛点源于缺少运营界面，需明确指出。常见示例：
- 无计费门户
- 无用量/速率限制可见性
- 无套餐/席位说明
- 无取消流程
- 无重复订阅防护
将这些视为 ECC 或网站跟进事项，而非单纯的支持事件。
5. 生成运营交接文档
最终需包含：
- 客户状态摘要
- 已执行操作
- 收入影响
- 待发送的跟进文本
- 需创建的产品或待办事项
输出格式
使用以下结构：
客户
- 姓名 / 邮箱
- 相关账户标识
计费状态
- 活跃订阅
- 发票或续费状态
- 异常情况
决策
- 问题分类
- 为何此操作正确
已执行操作
- 退款 / 取消 / 门户 / 无操作
后续跟进
- 简短客户消息
产品缺口
- 产品或网站中应修复的内容
优质建议示例
- "正确的修复方案是计费门户，而非自定义仪表盘"
- "这看起来是重复的个人结账，而非真实的团队席位购买"
- "退还一笔重复扣费，保留剩余活跃订阅，后续如有需要再将客户转为组织计费"
- Source repo
- affaan-m/ECC
- Skill path
- docs/zh-CN/skills/customer-billing-ops/SKILL.md
- Commit SHA
- 4e973d3eaf92
- Repository license
- MIT
- Data collected