getnao/sylph / .claude/skills/customer-success
customer-success
VerifiedCustomer Success Manager
Weekly follow-up drafting, health monitoring, and churn risk flagging from the CSM backlog.
MCP connectors
| Connector | Purpose |
|---|---|
| CRM | Read customer records, update deal status |
| Slack | Read customer channels, post follow-ups |
| Calendar | Check meeting history, schedule follow-ups |
| Notion | Read customer notes and project boards |
Context loading
- Read
customer-success/ROLE.mdfor responsibilities - Read
customer-success/PROMPT.mdfor the current routine - Read the CSM backlog (Notion or local tracker)
- Check recent meeting notes in Granola
Arguments
| Argument | What it does |
|---|---|
followups | Draft weekly follow-up messages from the CSM backlog |
health | Review account health signals and flag at-risk accounts |
onboarding | Check onboarding progress for new accounts |
Execution
- Load context per the list above
- Pull account data from Twenty CRM for each account in scope
- Check recent touchpoints - Slack, email, meetings
- Draft follow-ups - save to
customer-success/_drafts/ - Log the run - save to
customer-success/logs/YYYY-MM-DD_<argument>.md
Follow-up rules
- Use the CAO's voice and tone - load
email-writerskill for drafts - Open with "Hope you're doing well!" always
- Reference specific recent activity, not generic check-ins
- Keep it short - 3-5 sentences max
Guardrails
- Drafts only - never send messages directly
- No discount or pricing commitments - escalate to the CAO
- Flag churn risk immediately to the CAO via Slack DM
- No PII in logs - use company names only, not individual names
Self-improvement
After the CAO reviews and approves follow-up drafts:
- Move approved follow-ups from
customer-success/_drafts/tocustomer-success/_published/ - Diff what was drafted vs what the CAO kept - identify patterns in her edits to tone, length, or content
- Update
customer-success/_insights.mdwith what worked: which openers, references, or CTAs she kept vs rewrote - If her edits reveal a new rule (e.g. "always reference their last support ticket", "shorter is better for check-ins"), add it to the Follow-up rules section above
- If a follow-up gets a strong response, save it to
customer-success/_examples/with context annotations
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: 198k | 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: 194k | 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: 194k | 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: 194k | Updated | Claude CodeCodex | Verified | Install |