Update to Unabyss

{
  "description": "Surface what real customers are saying right now — praise worth amplifying, frustrations worth acting on, and accounts showing churn risk. Only active customers, last 1–2 weeks. Use this skill whenever the user asks \"what are customers saying\", \"any good testimonials lately\", \"who's unhappy\", \"any churn risk\", \"what's the customer sentiment\", \"customer feedback this week\", \"are customers happy\", \"what are users complaining about\", \"any wins from customers\", \"highlight customer feedback\", or anything that implies they want a founder-level read on customer sentiment. Requires Unabyss MCP.",
  "included_files": [],
  "name": "customer-pulse",
  "skill_md_contents": "---\nname: customer-pulse\ndescription: Surface what real customers are saying right now — praise worth amplifying, frustrations worth acting on, and accounts showing churn risk. Only active customers, last 1–2 weeks. Use this skill whenever the user asks \"what are customers saying\", \"any good testimonials lately\", \"who's unhappy\", \"any churn risk\", \"what's the customer sentiment\", \"customer feedback this week\", \"are customers happy\", \"what are users complaining about\", \"any wins from customers\", \"highlight customer feedback\", or anything that implies they want a founder-level read on customer sentiment. Requires Unabyss MCP.\n---\n\n# Customer Pulse\n\nSurface what active customers are saying right now — praise worth amplifying, frustrations worth acting on, accounts at risk. Last 1–2 weeks only. No noise from churned accounts or unconverted leads.\n\n## Required Integrations\n\nThis skill uses **Unabyss MCP** — `agentic_query` for cross-source customer signal synthesis.\n\n> If Unabyss is not connected, tell the user: \"This skill requires Unabyss MCP. You can connect it from the Tools menu.\"\n\n---\n\n## How to Run\n\n### Step 1 — Run `agentic_query`\n\nCustomer signals are spread across email, support, calls, and CRM — use `agentic_query`:\n\n```\nLook across all connected sources for customer signals from the last 7–14 days. Active, paying or recently onboarded customers only — exclude people who have already cancelled, unconverted leads, and internal team members.\n\nFind:\n- Positive feedback, praise, or results customers reported — include name and company where available\n- Frustrations, complaints, or repeated problems — even indirect ones\n- Accounts that seem to be going quiet, disengaging, or showing signs they might leave\n- Feature requests or product gaps mentioned by customers\n- Any customer who gave a quote or said something that reads like a testimonial\n\nReturn individual signals — don't group or summarize. Include customer name/company and date where available.\n```\n\nCall `agentic_query_read` with the returned query id to retrieve the result.\n\n### Step 2 — Synthesize the pulse\n\n---\n\n**Customer Pulse — [Date range]**\n\n**💚 Bright spots**\nPositive signals and quotes. For each: customer name/company, what they said, and whether it's usable as a testimonial (yes / needs follow-up / no).\n\n**🔴 Needs attention**\nActive customers expressing frustration. For each: who, what the issue is, how long it's been unresolved, and a specific next step.\n\n**⚠️ Churn risk**\nAccounts going quiet or signalling doubt. For each: who, the warning sign, and a suggested action.\n\n**💬 What they're asking for**\nRecurring product gaps from active customers, grouped by theme.\n\n---\n\n## Output Rules\n\n- Only active customers — exclude churned and unconverted\n- Every item needs a name or company — anonymous signals only if strongly meaningful\n- Next steps must be specific, not just \"follow up\"\n- Quote customers directly where possible\n- Omit empty sections entirely\n- No preamble before the header\n- Keep under 400 words\n"
}