ziyan-retention

Analyze customer signals to identify retention risks and generate interventions.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/rajagurunath/saras-wingman --skill ziyan-retention
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ziyan-retention
Source: https://github.com/rajagurunath/saras-wingman/tree/main/startup-os/ziyan-retention/wingman
Command: npx skills add https://github.com/rajagurunath/saras-wingman --skill ziyan-retention

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ziyan is the Optimization Layer for SaaS startups, listening to signals from tickets, chats, issues, and analytics to boost retention outcomes by surfacing content improvements, chatbot prompts, and product tool coverage.

Core Features & Use Cases

  • Proactively identify at-risk customers and draft retention interventions.
  • Generate help articles, chatbot prompts, and MCPs based on top signal clusters.
  • Maintain llms.txt and product context to improve customer experience across docs and support workflows.

Quick Start

Identify churn signals and trigger Ziyan to draft a proactive retention intervention.

Frequently Asked Questions about ziyan-retention

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

FAQPage Schema
How do I identify customer churn risks using Freshservice tickets and Amplitude analytics?

To identify customer churn risks, this Skill analyzes signals from Freshservice tickets, Amplitude analytics, and GitHub issues to detect at-risk customers and surface actionable retention interventions.

How do I automatically generate help articles and chatbot prompts from customer support tickets?

Automatically generate help articles and chatbot prompts by clustering top support signals from tickets and chat logs, then converting those clusters into targeted retention content and documentation.

Can I analyze retention risks for my SaaS startup without live data integrations?

Yes, you can analyze retention risks without live data because the Skill includes simulator support to generate proactive outreach interventions and test guardrails when live data is unavailable.

What is the best way to maintain llms.txt and product context for SaaS customer support workflows?

The best way to maintain llms.txt and product context is to continuously update them based on analyzed customer signals, ensuring support workflows and documentation reflect current retention optimizations.

Does this proactive retention optimizer work with GitHub issues and database chat logs?

Yes, the proactive retention optimizer works with GitHub issues and database chat logs, applying guardrails across these signals to trigger proactive outreach and generate retention interventions.