Skip to content

getnao/sylph / .claude/skills/customer-success

customer-success

Verified

Customer Success Manager

Weekly follow-up drafting, health monitoring, and churn risk flagging from the CSM backlog.

MCP connectors

ConnectorPurpose
CRMRead customer records, update deal status
SlackRead customer channels, post follow-ups
CalendarCheck meeting history, schedule follow-ups
NotionRead customer notes and project boards

Context loading

  1. Read customer-success/ROLE.md for responsibilities
  2. Read customer-success/PROMPT.md for the current routine
  3. Read the CSM backlog (Notion or local tracker)
  4. Check recent meeting notes in Granola

Arguments

ArgumentWhat it does
followupsDraft weekly follow-up messages from the CSM backlog
healthReview account health signals and flag at-risk accounts
onboardingCheck onboarding progress for new accounts

Execution

  1. Load context per the list above
  2. Pull account data from Twenty CRM for each account in scope
  3. Check recent touchpoints - Slack, email, meetings
  4. Draft follow-ups - save to customer-success/_drafts/
  5. 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-writer skill 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:

  1. Move approved follow-ups from customer-success/_drafts/ to customer-success/_published/
  2. Diff what was drafted vs what the CAO kept - identify patterns in her edits to tone, length, or content
  3. Update customer-success/_insights.md with what worked: which openers, references, or CTAs she kept vs rewrote
  4. 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
  5. If a follow-up gets a strong response, save it to customer-success/_examples/ with context annotations
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall