[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JF74STGA8SWFSC77REEXDR":3,"skill-same:01M6JF74STGA8SWFSC77REEXDR":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6JF74STGA8SWFSC77REEXDR","client-success-and-retention",null,"Use when designing client delivery for a coaching\u002Fagency program, hiring or running a Client Success Manager \u002F success coach, handling a struggling or refund-requesting client, setting onboarding-call and check-in cadence, or improving retention and continuity. Source - Grow Acquisition 3.0 (Nikk Kleinherenbrink).","S3YED\u002Fappie-kit","S3YED","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62743867?v=4","01M6JBKBRRVP6KMS0VWZ27T3R6","01M6JBKBX0KG30284PW1DBYJT1",14,"MIT","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fpersonal\u002Fclient-acquisition\u002Fclient-success-and-retention\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"client success and retention","retention","client","grow","refund","source","for","manager","agency","cadence","onboarding","coaching","continuity","delivery","call","coach","use","acquisition","check","Hiring","2026-11-10 10:12:30",false,"---\nname: client-success-and-retention\ndescription: Use when designing client delivery for a coaching\u002Fagency program, hiring or running a Client Success Manager \u002F success coach, handling a struggling or refund-requesting client, setting onboarding-call and check-in cadence, or improving retention and continuity. Source - Grow Acquisition 3.0 (Nikk Kleinherenbrink).\n---\n\n# Client Success & Retention\n\n\"Client Success = consistently getting clients the results they paid for.\" Happy clients stay longer (higher LTV), become marketing assets, and refer. It's two things together: **Results AND Experience** — you can have one without the other and still have an unhappy client.\n\n## 4 Pillars (score your program 1-10 each)\n\n- **Content** — the training curriculum; step-by-step transformation (video\u002Faudio + docs\u002Fsheets).\n- **Coaching** — helping them apply the content to their situation; implementation + troubleshooting + accountability relationship.\n- **Community** — peer support\u002Fcamaraderie (key for group offers; toxic if done wrong).\n- **Culture** — the unseen force; shaped by your values, what you celebrate and defend. Created by default or by design.\n\nSweet spot = clients get results + delivery feels sustainable + client feels supported + you love the business. Audit: strongest pillar and why; weakest and why.\n\n## When & who to hire (Success Coach)\n\nHire when you're time-poor but want to improve client experience and handle more clients. Part-time or full-time depending on model\u002Fdelivery\u002Foffer.\n\n**Interview process:** post in FB groups\u002Fyour audience → application → phone screen → zoom\u002Fin-person → offer.\nLooking for: WILL (hunger), SKILL (meets the role), coachable\u002Fopen, honesty\u002Fintegrity, certain in direction, natural rapport, can explain past job moves, income goals aligned (too-low goals is a flag).\nRed flags: never mentions past failures, exaggerating, badmouths past bosses, can't explain moves, self-absorbed, ONLY money-motivated.\n\n## Onboarding call (the 20% that drives 80%)\n\nTwo goals every onboarding call: **establish leadership** + **build a real relationship.** Client should leave thinking: \"I see the path to success,\" \"I really like who I'm working with,\" \"I'm confident they can help me — I'm in the right place.\"\n\nCadence: build rapport → learn their business (high level) → zoom into their metrics → establish constraints → find their program goals → show them their resources\u002Fhow to use them → lay out a clear 3-month game plan → give 3-5 action steps → **book the next call (5-7 days out)** before ending.\n\n## Communication & cadence\n\n- **1:1 calls** for problems a Slack message can't solve (data review, team troubleshooting). 20-40 min. Book Call 2 on the onboarding call (within 7 days), book Call 3 on Call 2 (within 7 days), then never go >14 days without a face-to-face. Always book the next call at the end of each call — it's the deadline for the action steps.\n- **Slack\u002FDiscord** is the highest-leverage tool if used right, biggest time-sink if not. Get clients in the app from day one, notifications on. Prefer **text over voice** (trains them to text; sparing voice notes feel special). Choose batch-once-daily OR ongoing-multiple-times-daily. 1-2x\u002Fweek reactivate quiet clients (\"hey\" or a relevant nudge); unresponsive 24-48h → message the onboarding chat. Don't let Slack become the ONLY support channel (prevents abuse).\n\n## Coaching tiers & keys\n\n- Make sure clients actually watch the videos — tell them EXACTLY which modules move the needle (\"go through the training\" = 90% won't).\n- Get group calls booked on their calendar or attendance decays and they lean on you as a Q&A line.\n- Use 20-30 min coaching calls every 2-3 weeks (never >3 weeks without face-to-face).\n- **Call reviews \u002F group audits \u002F DM reviews** are the highest-impact tool — frequent (1-2 weeks) early, then manager-mode every 3-4 weeks. Bigger sales team = more reviews needed.\n- Rarely, for high-revenue clients, book them with the founder right after onboarding, at a roadblock, or before a continuity conversation — huge perceived value.\n- Keys to coaching: Relationship + Leadership.\n\n## Handling client challenges — LCER\n\nRefund requests \u002F clients not getting results: **Listen → Clarify → Empathise → Resolve.** Higher-ticket → get on the phone, not DMs. Once you understand the situation, decide: do they need **accountability** (\"you hired me to help you grow, tough times and all — how can I best help you through this?\") or **compassion** (take the business hat off; right now they need a friend more than a coach; consider a timeline extension or a deserved refund if circumstances genuinely worsened).\n\n## Common mistakes\n\n- Optimizing for results OR experience, not both → unhappy clients despite good outcomes.\n- Vague \"go through the training\" instead of naming the needle-moving modules.\n- Letting the next call go unbooked — client drifts, action steps lose their deadline.\n- Slack as the only channel, or voice-noting everything (trains long messages, burns time).\n- Treating every struggling client with accountability when some need compassion (or vice versa).\n- Going >14 days without a face-to-face during active coaching.\n","# Client Success & Retention\n\n\"Client Success = consistently getting clients the results they paid for.\" Happy clients stay longer (higher LTV), become marketing assets, and refer. It's two things together: **Results AND Experience** — you can have one without the other and still have an unhappy client.\n\n## 4 Pillars (score your program 1-10 each)\n\n- **Content** — the training curriculum; step-by-step transformation (video\u002Faudio + docs\u002Fsheets).\n- **Coaching** — helping them apply the content to their situation; implementation + troubleshooting + accountability relationship.\n- **Community** — peer support\u002Fcamaraderie (key for group offers; toxic if done wrong).\n- **Culture** — the unseen force; shaped by your values, what you celebrate and defend. Created by default or by design.\n\nSweet spot = clients get results + delivery feels sustainable + client feels supported + you love the business. Audit: strongest pillar and why; weakest and why.\n\n## When & who to hire (Success Coach)\n\nHire when you're time-poor but want to improve client experience and handle more clients. Part-time or full-time depending on model\u002Fdelivery\u002Foffer.\n\n**Interview process:** post in FB groups\u002Fyour audience → application → phone screen → zoom\u002Fin-person → offer.\nLooking for: WILL (hunger), SKILL (meets the role), coachable\u002Fopen, honesty\u002Fintegrity, certain in direction, natural rapport, can explain past job moves, income goals aligned (too-low goals is a flag).\nRed flags: never mentions past failures, exaggerating, badmouths past bosses, can't explain moves, self-absorbed, ONLY money-motivated.\n\n## Onboarding call (the 20% that drives 80%)\n\nTwo goals every onboarding call: **establish leadership** + **build a real relationship.** Client should leave thinking: \"I see the path to success,\" \"I really like who I'm working with,\" \"I'm confident they can help me — I'm in the right place.\"\n\nCadence: build rapport → learn their business (high level) → zoom into their metrics → establish constraints → find their program goals → show them their resources\u002Fhow to use them → lay out a clear 3-month game plan → give 3-5 action steps → **book the next call (5-7 days out)** before ending.\n\n## Communication & cadence\n\n- **1:1 calls** for problems a Slack message can't solve (data review, team troubleshooting). 20-40 min. Book Call 2 on the onboarding call (within 7 days), book Call 3 on Call 2 (within 7 days), then never go >14 days without a face-to-face. Always book the next call at the end of each call — it's the deadline for the action steps.\n- **Slack\u002FDiscord** is the highest-leverage tool if used right, biggest time-sink if not. Get clients in the app from day one, notifications on. Prefer **text over voice** (trains them to text; sparing voice notes feel special). Choose batch-once-daily OR ongoing-multiple-times-daily. 1-2x\u002Fweek reactivate quiet clients (\"hey\" or a relevant nudge); unresponsive 24-48h → message the onboarding chat. Don't let Slack become the ONLY support channel (prevents abuse).\n\n## Coaching tiers & keys\n\n- Make sure clients actually watch the videos — tell them EXACTLY which modules move the needle (\"go through the training\" = 90% won't).\n- Get group calls booked on their calendar or attendance decays and they lean on you as a Q&A line.\n- Use 20-30 min coaching calls every 2-3 weeks (never >3 weeks without face-to-face).\n- **Call reviews \u002F group audits \u002F DM reviews** are the highest-impact tool — frequent (1-2 weeks) early, then manager-mode every 3-4 weeks. Bigger sales team = more reviews needed.\n- Rarely, for high-revenue clients, book them with the founder right after onboarding, at a roadblock, or before a continuity conversation — huge perceived value.\n- Keys to coaching: Relationship + Leadership.\n\n## Handling client challenges — LCER\n\nRefund requests \u002F clients not getting results: **Listen → Clarify → Empathise → Resolve.** Higher-ticket → get on the phone, not DMs. Once you understand the situation, decide: do they need **accountability** (\"you hired me to help you grow, tough times and all — how can I best help you through this?\") or **compassion** (take the business hat off; right now they need a friend more than a coach; consider a timeline extension or a deserved refund if circumstances genuinely worsened).\n\n## Common mistakes\n\n- Optimizing for results OR experience, not both → unhappy clients despite good outcomes.\n- Vague \"go through the training\" instead of naming the needle-moving modules.\n- Letting the next call go unbooked — client drifts, action steps lose their deadline.\n- Slack as the only channel, or voice-noting everything (trains long messages, burns time).\n- Treating every struggling client with accountability when some need compassion (or vice versa).\n- Going >14 days without a face-to-face during active coaching.\n",{"name":5,"description":7},"master","8ec37df6d71fb664ea19d32c079e7d3ff931a8e0","skills\u002Fpersonal\u002Fclient-acquisition\u002Fclient-success-and-retention",3,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit","https:\u002F\u002Fweblyfe.ai","https:\u002F\u002Fgithub.com\u002FS3YED","2026-08-27 01:54:02",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add S3YED\u002Fappie-kit --skill client-success-and-retention",{"tool":62,"command":63},"bunx","bunx skills add S3YED\u002Fappie-kit --skill client-success-and-retention",{"tool":65,"command":66},"pnpm","pnpm dlx skills add S3YED\u002Fappie-kit --skill client-success-and-retention","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fpersonal\u002Fclient-acquisition\u002Fclient-success-and-retention\u002FSKILL.md",true,[],[71,107,140,165,196,220],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":88,"publishedAt":43},"01M6JFD4M6N4DSGC7TXEJ5R3J2","ai-music","AI music generation and audio tools: HeartMuLa lyrics-to-music generation, songwriting craft (+ Suno prompts), and audio spectrogram\u002Ffeature visualization.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fwethlete\u002Fai-music\u002FSKILL.md",[77,82,85],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":83,"categoryName":84,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":86,"categoryName":87,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000023","Skill与智能体开发",[89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106],"music","ai music","humanizer","visualization","Tools","Audio","hermes","hermes agent","songwriting","suno","lyrics","prompts","heartmula","craft","generation","feature","ai music generation","music generation",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":119,"publishedAt":43},"01M6JFCZE4XNFQFMNZDHKHT5V5","agentic-webdesign-design-system-ingestion","Use v0 Design Systems 2.0, Bolt Design System Agents, or Lovable to generate production UI from a client's real design system components — not generic Tailwind. Use when building a client website where brand consistency matters.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-design-system-ingestion\u002FSKILL.md",[113,116],{"categoryNo":114,"categoryName":115,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000032","设计师",[120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139],"design","agentic","design system","system","ingestion","webdesign","agentic webdesign design system ingestion","components","generate","design systems","website","ui","Tailwind","bolt","lovable","v0","design-system","wed","design system components","appie",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":148,"publishedAt":43},"01M6JFCVPX3913CFAS6QQJ33ZB","agentic-webdesign-agent-elements","Use 21st.dev Agent Elements — 25 shadcn\u002Fui components purpose-built for AI agent UIs. Tool cards (Bash, Edit, Search, Plan, Subagent, MCP), chat, input, streaming. Open source, shadcn-registry install, no runtime lock-in.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-agent-elements\u002FSKILL.md",[146,147],{"categoryNo":86,"categoryName":87,"taxonomyType":80,"taxonomyTypeDesc":81},{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},[121,149,125,150,151,152,127,153,154,155,156,157,158,159,160,161,162,163,164,28],"elements","agentic webdesign agent elements","MCP","ai agent","registry","search","streaming","open source","open","Bash","plan","subagent","edit","install","input","lock",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":175,"publishedAt":43},"01M6JFCQC7H65M9QJ6TRE71BS1","vercel-deployment","Deploy static sites and frontends to Vercel — handles both CLI and REST API paths, including the CLI token sanitization workaround.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fvercel-deployment\u002FSKILL.md",[171,174],{"categoryNo":172,"categoryName":173,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":86,"categoryName":87,"taxonomyType":80,"taxonomyTypeDesc":81},[176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195],"deployment","vercel deployment","vercel","macos","cli","linux","windows","deploy","vercel deploy","REST","api","site","deploy to vercel","token","rest api","host","sites","paths","sanitization","static site",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":203,"publishedAt":43},"01M6JFCM4SMTXBM5A01BK2YQG1","software-quality-workflows","Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fsoftware-quality-workflows\u002FSKILL.md",[202],{"categoryNo":86,"categoryName":87,"taxonomyType":80,"taxonomyTypeDesc":81},[204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,29],"workflows","quality","software","software quality workflows","review","tdd","workflow","commit","debugging","code","debugger","pre-commit","investigation","code simplification","user","simplification",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":233,"publishedAt":43},"01M6JFCGD0M6CEATY01W7YN6DB","react-component-refactoring","Safely refactor large React components into smaller, maintainable pieces using proven patterns","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Freact-component-refactoring\u002FSKILL.md",[226,229,232],{"categoryNo":227,"categoryName":228,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":230,"categoryName":231,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":86,"categoryName":87,"taxonomyType":80,"taxonomyTypeDesc":81},[234,235,236,237,238,239,240,241,179,242,243,127,244,182,245,213,246,247,248,249],"react","component","refactoring","component refactoring","react component","react component refactoring","frontend","writing","safe","typescript","react components","modular","refactor","simplify","patterns","test-driven-development"]