ZenUml/conf-app / .claude/skills/customer-lifecycle
customer-lifecycle
VerifiedRead-only screening of customer installs, uninstalls, new license candidates, subscription changes, cancellations and approaching or passed deadlines. Use when asked what changed recently, who installed/uninstalled, or which customer states deserve investigation. Covers existing and prospective customers and reports evidence without initiating follow-up.
Customer lifecycle signals
Use shared evidence rules and source matrix and product registry. Return facts in the shared signal shape; do not send, grant access, change a tracker or schedule monitoring merely because a signal exists.
For “查 Confluence app 过去 N 天的新客户”, use new-customers's --live --days N --app all entrypoint, defaulting N to 1. Its seven-product scope is Lite, Full, Diagramly, AsyncAPI, AWS Widgets, Whiteboard and Mini Sites. Use fresh licenses-only GETs, not transaction-reading --sync; report the approximate inclusive date window and use maintenanceStartDate for all products' basic new-customer candidates. FREE licenses do not require trial dates or trial-coverage warnings; available evaluation dates for paid products are optional separate context. lastUpdated does not indicate a new customer. Investigate old-customer/renewal/migration history only when maintenance-start candidates exist. Candidates do not prove strict first installation. This specific request overrides the generic seven-complete-day default below and does not create an automated schedule.
- Resolve products, time window and timezone from the request. Default a recent scan to seven complete days and name the range. A 30-day expansion must be labelled. "All customers" includes the registered products, with unsupported sources listed explicitly.
- Query only the relevant existing primitives:
forge-installs: current install snapshot and prior-snapshot difference. Missing baseline means change unknown. A disappearance gives a time interval, not an exact uninstall timestamp or reason.new-customers: license-start candidates and known historical installation evidence, not confirmed new customers. Existing company/new product and renewals/migrations are distinct.marketplace: license and transaction facts; compare identified subscriptions with earlier snapshots when establishing a transition. Read cancellation feedback viacustomer-feedback.income-radar: billing/expiry candidates only; no contact policy inherited.tenant: verify each promising site across all its products and the separate user/space license layer.
- Apply the source matrix. Local CRM classification rules can help name a signal; its local simulated action is never evidence of a real send, payment or grant. Do not duplicate its queries or maintain a competing classifier.
- For each material signal return customer/site, product, event kind, before/after if proven, occurred-at or bounded observation interval, source reference, queried-at, coverage window, read status and unknowns. Current-state-only observations are labelled as such.
- Summarise coverage, failed/not-queried sources, freshness and notable changes. No recommendation/action fields belong in this result. Let
customer-followupcombine contact history, feedback and goals to decide what to do.
Full trial expiry, commercial license status, cancelled subscription, removed install and missing payment record are not interchangeable. Trial expiry alone does not prove a customer needs manual purchasing help; automatic billing outcome must be verified separately.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 193k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 193k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 193k | Updated | Claude CodeCodex | Verified | Install |