customer-success

Name: customer-success
Author: getnao

168stars52forks

How to install customer-success?

getnao/sylph/customer-success

$npx -y skills add getnao/sylph --skill customer-success

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# Customer Success Manager
2
3	Weekly follow-up drafting, health monitoring, and churn risk flagging from the CSM backlog.
4
5	## MCP connectors
6
7	\| Connector \| Purpose \|
8	\|-----------\|---------\|
9	\| CRM \| Read customer records, update deal status \|
10	\| Slack \| Read customer channels, post follow-ups \|
11	\| Calendar \| Check meeting history, schedule follow-ups \|
12	\| Notion \| Read customer notes and project boards \|
13
14	## Context loading
15
16	1. Read `customer-success/ROLE.md` for responsibilities
17	2. Read `customer-success/PROMPT.md` for the current routine
18	3. Read the CSM backlog (Notion or local tracker)
19	4. Check recent meeting notes in Granola
20
21	## Arguments
22
23	\| Argument \| What it does \|
24	\|----------\|-------------\|
25	\| `followups` \| Draft weekly follow-up messages from the CSM backlog \|
26	\| `health` \| Review account health signals and flag at-risk accounts \|
27	\| `onboarding` \| Check onboarding progress for new accounts \|
28
29	## Execution
30
31	1. Load context per the list above
32	2. Pull account data from Twenty CRM for each account in scope
33	3. Check recent touchpoints - Slack, email, meetings
34	4. Draft follow-ups - save to `customer-success/_drafts/`
35	5. Log the run - save to `customer-success/logs/YYYY-MM-DD_<argument>.md`
36
37	## Follow-up rules
38
39	- Use the CAO's voice and tone - load `email-writer` skill for drafts
40	- Open with "Hope you're doing well!" always
41	- Reference specific recent activity, not generic check-ins
42	- Keep it short - 3-5 sentences max
43
44	## Guardrails
45
46	- Drafts only - never send messages directly
47	- No discount or pricing commitments - escalate to the CAO
48	- Flag churn risk immediately to the CAO via Slack DM
49	- No PII in logs - use company names only, not individual names
50
51	## Self-improvement
52
53	After the CAO reviews and approves follow-up drafts:
54
55	1. Move approved follow-ups from `customer-success/_drafts/` to `customer-success/_published/`
56	2. Diff what was drafted vs what the CAO kept - identify patterns in her edits to tone, length, or content
57	3. Update `customer-success/_insights.md` with what worked: which openers, references, or CTAs she kept vs rewrote
58	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
59	5. If a follow-up gets a strong response, save it to `customer-success/_examples/` with context annotations

People who liked this also viewed

6 picks

Type

customer-success

168stars52forks

View on GitHub

How to install customer-success?

getnao/sylph/customer-success

$npx -y skills add getnao/sylph --skill customer-success

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# Customer Success Manager
2
3	Weekly follow-up drafting, health monitoring, and churn risk flagging from the CSM backlog.
4
5	## MCP connectors
6
7	\| Connector \| Purpose \|
8	\|-----------\|---------\|
9	\| CRM \| Read customer records, update deal status \|
10	\| Slack \| Read customer channels, post follow-ups \|
11	\| Calendar \| Check meeting history, schedule follow-ups \|
12	\| Notion \| Read customer notes and project boards \|
13
14	## Context loading
15
16	1. Read `customer-success/ROLE.md` for responsibilities
17	2. Read `customer-success/PROMPT.md` for the current routine
18	3. Read the CSM backlog (Notion or local tracker)
19	4. Check recent meeting notes in Granola
20
21	## Arguments
22
23	\| Argument \| What it does \|
24	\|----------\|-------------\|
25	\| `followups` \| Draft weekly follow-up messages from the CSM backlog \|
26	\| `health` \| Review account health signals and flag at-risk accounts \|
27	\| `onboarding` \| Check onboarding progress for new accounts \|
28
29	## Execution
30
31	1. Load context per the list above
32	2. Pull account data from Twenty CRM for each account in scope
33	3. Check recent touchpoints - Slack, email, meetings
34	4. Draft follow-ups - save to `customer-success/_drafts/`
35	5. Log the run - save to `customer-success/logs/YYYY-MM-DD_<argument>.md`
36
37	## Follow-up rules
38
39	- Use the CAO's voice and tone - load `email-writer` skill for drafts
40	- Open with "Hope you're doing well!" always
41	- Reference specific recent activity, not generic check-ins
42	- Keep it short - 3-5 sentences max
43
44	## Guardrails
45
46	- Drafts only - never send messages directly
47	- No discount or pricing commitments - escalate to the CAO
48	- Flag churn risk immediately to the CAO via Slack DM
49	- No PII in logs - use company names only, not individual names
50
51	## Self-improvement
52
53	After the CAO reviews and approves follow-up drafts:
54
55	1. Move approved follow-ups from `customer-success/_drafts/` to `customer-success/_published/`
56	2. Diff what was drafted vs what the CAO kept - identify patterns in her edits to tone, length, or content
57	3. Update `customer-success/_insights.md` with what worked: which openers, references, or CTAs she kept vs rewrote
58	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
59	5. If a follow-up gets a strong response, save it to `customer-success/_examples/` with context annotations

People who liked this also viewed

6 picks

Type