customer-success-manager

Analyze adoption risks and translate engineering signals into customer-success guidance.

22|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill customer-success-manager-jshsakura
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: customer-success-manager
Source: https://github.com/jshsakura/awesome-opencode-skills/tree/main/skills/customer-success-manager
Command: npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill customer-success-manager-jshsakura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams translate adoption risk signals into actionable customer-success guidance that aligns engineering reality with customer outcomes.

Core Features & Use Cases

  • Adoption-risk synthesis and prioritization
  • Onboarding optimization and issue-resolution guidance
  • Engineering-contextualized customer communications and playbooks

Quick Start

Given a new onboarding friction signal, map the customer journey, identify root causes, and propose high-impact interventions with measurable success indicators.

Frequently Asked Questions about customer-success-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate engineering signals into actionable customer success guidance?

To translate engineering signals into customer success guidance, you analyze adoption risks and map them to customer outcomes, ensuring product reality aligns with retention and onboarding strategies through measurable success indicators.

What is the best way to prioritize adoption risk signals during user onboarding?

Prioritizing adoption risk signals involves mapping the customer journey to identify friction points, determining root causes from engineering context, and proposing high-impact interventions to optimize the onboarding experience.

How do I create customer communications that align with engineering reality during support escalations?

Creating engineering-aligned customer communications requires synthesizing support escalation signals into contextualized playbooks, prioritizing high-impact issues, and defining measurable success indicators for follow-up validation.

Can I use this approach for retention planning across product and engineering teams?

Yes, you can use adoption risk synthesis for retention planning by translating engineering signals into actionable guidance, ensuring product teams and engineering stakeholders align around measurable customer success outcomes.

What do I need to define measurable success indicators for customer adoption interventions?

Defining measurable success indicators requires analyzing the root causes of onboarding friction, proposing targeted interventions based on engineering signals, and establishing validation metrics for follow-up across customer stakeholders.