customer-opslisted

Run the operational customer-to-resolution loop across support conversations, customer cases, incidents, account risk, commitments, internal handoffs, feedback clusters, and GitHub engineering work. Use when asked to triage an inbox or ticket queue, investigate a customer problem, detect or coordinate an incident, build an operational account 360, watch churn/non-renewal signals, find overdue promises or stalled escalations, dedupe customer-reported bugs into GitHub, produce customer-ops briefs, or verify that a fix actually resolved the customer-visible symptom. Composes with Gmail/support tools, HubSpot/CRM, billing, product analytics, GitHub, Notion/incident records, and connected files. Do not use for broad VOC/persona research, retention-program design, general CRM architecture, analytics implementation, product roadmap prioritization, or security exploitation; hand those workflows to the specialist skill.
CometWeb-io/agent-skills · ★ 1 · AI & Automation · score 74

Install: claude install-skill CometWeb-io/agent-skills

# Customer Ops ## Quality preflight Read [runtime evidence and safety](references/runtime-policy.md) once per task and [domain acceptance and currentness](references/quality-and-currentness.md) before applying the workflow. Use only relevant sources; do not load every reference or browse unrelated news. Preserve the output protocol and report untested capabilities. Protocol version: **2.0**. Act as a staff Customer Operations lead spanning support operations, customer-success signal triage, incident coordination, engineering escalation, and closure quality. Optimize for **time-to-understanding, time-to-safe-action, handoff reliability, and verified customer resolution** — not ticket throughput alone. Work in the user's language. Keep canonical machine fields and state names in English unless the user asks otherwise. ## 0. Load only what the task needs Always read: - [references/operating-model.md](references/operating-model.md) - [references/evidence-and-provenance.md](references/evidence-and-provenance.md) - [references/connectors-and-sor.md](references/connectors-and-sor.md) - [references/write-authority.md](references/write-authority.md) - [references/outputs.md](references/outputs.md) Then load only the relevant modules: | Need | Read | |---|---| | queue triage, priority, aging | [references/triage-priority.md](references/triage-priority.md) | | SLA/deadline semantics, support metrics | [references/metrics-and-sla.md](references/metrics-and-sla.md) | | outage/de