菜单
Reads a customer's support health — open ticket load, recurring themes, aging issues, and escalation candidates. Use when asked "how is support going for X", before meetings with support-sensitive accounts, or when ticket friction might explain churn risk.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Produces a full account snapshot on demand — profile, health, revenue, stakeholders, activity, and risks in one view. Use when someone asks "catch me up on X", "give me the full picture on X", or needs to get oriented on an account they don't know.
Identifies reference, case-study, and advocacy candidates — healthy, tenured accounts with strong outcomes and vocal fans. Use when marketing needs references, sales needs proof points for a vertical, or building an advocacy program.
Leadership-ready roll-up of at-risk accounts — who is at risk, why, how much ARR is exposed, and what's being done. Use for weekly risk reviews, leadership updates, or when asked "which accounts are at risk right now".
Responds to a champion or sponsor departure — maps the remaining relationship surface, assesses exposure, and builds a re-entry plan for the new stakeholder. Use when a key contact leaves, changes roles, or a new decision-maker inherits the account.
Deep-dives a red account and produces a structured save plan — root causes ranked, save plays matched to causes, and a realistic assessment of whether the account is savable. Use when an account turns red, gives churn signals, or someone says "we're going to lose X".
Performs a structured customer health review using usage data, support interactions, renewal signals, and stakeholder sentiment. Use when asked to assess customer health, identify churn risk, prepare for QBRs, or generate a health score.
| name | ticket-pulse |
| description | Reads a customer's support health — open ticket load, recurring themes, aging issues, and escalation candidates. Use when asked "how is support going for X", before meetings with support-sensitive accounts, or when ticket friction might explain churn risk. |
| license | MIT |
| compatibility | Tool calls resolve natively in Quivly, or in Claude Code / claude.ai / any MCP-enabled agent via the Quivly MCP connector. Without tools, the skill degrades to a guided manual workflow. |
| metadata | {"author":"quivly","version":"1.0","category":"customer-engineering","quivly-tools":"platform-data.search-tickets communication.search-conversations customer-data.get-customer health.get-insights"} |
You assess whether support experience is helping or hurting this customer relationship.
Core principle: volume is engagement; aging, repetition, and escalating severity are the risk.
get-customer) for tier and context — a P1 for an enterprise account 30 days from renewal is different from the same ticket at a small account.search-tickets), last 90 days. Bucket them:
search-conversations) for frustration that never became a ticket — often the loudest signal.get-insights) for support-related risk already flagged.Support pulse: {Customer} — one-line verdict: Healthy / Friction building / Escalation needed
The numbers — open count, oldest unresolved, volume trend vs. prior period
Themes — recurring issues grouped, each with occurrence count and current status
Sentiment check — what the customer's tone says beyond the tickets
Recommended actions — e.g., escalate ticket X to product, proactive check-in on theme Y, close-the-loop message on resolved-but-unacknowledged items
Related skills: friction has boiled over → escalation-brief; support friction is driving churn risk → churn-save-plan.