subscription-plan-changes
Analyzes subscription upgrades, downgrades, prorations, and plan migrations in Stripe. Use when the user mentions "upgrade", "downgrade", "plan change", "proration", or "switching tiers".
来源信息
- 仓库
- appeeky/stripe-skills
- 最近来源活动
- 2026年7月19日 10:10
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 5
- 分支
- 1
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- subscription-plan-changes
- description
- Analyzes subscription upgrades, downgrades, prorations, and plan migrations in Stripe. Use when the user mentions "upgrade", "downgrade", "plan change", "proration", or "switching tiers".
- metadata
- {"version":"1.0.0"}
# Subscription Plan Changes
## Stripe MCP Setup
Requires **Stripe MCP** connected via OAuth or restricted key. Docs: https://docs.stripe.com/mcp
1. `GetMcpTools` with `server: "user-Stripe"` (or `plugin-stripe-stripe`) before any call
2. Prefer `stripe_api_search` → `stripe_api_details` → `stripe_api_read` for list/retrieve
3. **Always paginate** — `limit: 100`, follow `has_more` with `starting_after`
4. Amounts are in **cents** unless noted
5. Never expose secret keys in output
## Workflow
1. Review codebase checkout update path (`subscriptions.update` vs new checkout)
2. Sample recent `customer.subscription.updated` — compare `items` price changes
3. Check proration: `proration_behavior`, invoice line items for `proration`
## Anti-Patterns
- Creating **new** subscription instead of updating → double billing
- No `alreadyOnPlan` guard
## Output Template
```
Plan Change Audit
Update method: in-place / new checkout
Proration: [behavior]
Recent migrations (sample):
| Customer | From → To | Proration $ |
Recommendations: ...
```
在 GitHub 查看