Token导航 LogoToken导航TokenDH.com
开发只读github未标认证来源可访问许可证需确认审计通过

cs-strategist策略师

Agent Skill

cs-strategist 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,608

周安装

67

GitHub Stars

18

下载量

536
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:cs-strategist(策略师)
来源仓库:https://github.com/ncklrs/startup-os-skills
仓库路径:skills/cs-strategist
安装命令:
npx skills add https://github.com/ncklrs/startup-os-skills --skill cs-strategist
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/ncklrs/startup-os-skills --skill cs-strategist

简介

cs-strategist 提供战略客户成功 expertise,涵盖团队建设、分段 playbook 与 metrics 设计。

  • 哲学:CS 不是支持换名,而是驱动可预测收入增长的战略职能。
  • 最佳 CS 组织特征: ruthless segmentation、outcome-based metrics、technology-first scaling。
  • Own the number:CS 拥有 Net Revenue Retention 等核心指标,非仅响应请求。
  • 适用于从初创到规模化阶段的 CS 体系搭建与 scalability 规划。

SKILL.md

CS Strategist

Strategic Customer Success expertise for building and scaling world-class CS organizations — from team structure and segmentation to playbooks, metrics, and technology.

Philosophy

Customer Success is not support with a different name. It's a strategic function that drives predictable revenue growth through proactive customer value delivery.

The best CS organizations:

  1. Segment ruthlessly — One-size-fits-all is no-size-fits-any
  2. Measure outcomes, not activities — Calls made ≠ value delivered
  3. Scale before you hire — Technology enables, humans differentiate
  4. Own the number — CS owns Net Revenue Retention, full stop

How This Skill Works

When invoked, apply the guidelines in rules/ organized by:

  • org-* — CS org design, team structure, roles, hiring
  • segmentation-* — Customer tiering, coverage models, resource allocation
  • metrics-* — KPIs, health scores, forecasting, reporting
  • playbooks-* — Lifecycle playbooks, automation, QBRs
  • executive-* — Stakeholder management, EBRs, C-level relationships
  • technology-* — CS platforms, tool stack, integration
  • value-* — Value realization, ROI frameworks, success plans
  • journey-* — Customer journey mapping, touchpoints, moments of truth

Core Frameworks

The CS Maturity Model

StageCharacteristicsFocus
ReactiveSupport-driven, firefightingBasic retention
ProactiveHealth monitoring, early interventionChurn prevention
StrategicOutcome-focused, expansion-drivenNRR growth
TransformationalCustomer value embedded in productMarket leadership

Customer Segmentation Tiers

┌─────────────────────────────────────────────────────────┐
│                    HIGH TOUCH                           │
│  Enterprise / Strategic accounts ($100k+ ARR)           │
│  Dedicated CSM, EBRs, custom success plans              │
│  Ratio: 1:10-25 accounts                                │
├─────────────────────────────────────────────────────────┤
│                    LOW TOUCH                            │
│  Mid-market accounts ($15k-$100k ARR)                   │
│  Pooled CSMs, scaled programs, office hours             │
│  Ratio: 1:50-100 accounts                               │
├─────────────────────────────────────────────────────────┤
│                    TECH TOUCH                           │
│  SMB / Self-serve accounts (<$15k ARR)                  │
│  Automated journeys, community, self-service            │
│  Ratio: 1:500+ accounts (or no dedicated CSM)           │
└─────────────────────────────────────────────────────────┘

The CS Metrics Hierarchy

CategoryMetricsOwner
Business OutcomesNRR, GRR, Logo RetentionCS Leadership
Leading IndicatorsHealth Score, Adoption, NPSCS Operations
Activity MetricsTouchpoints, QBRs, Time-to-ValueCSMs

Net Revenue Retention Formula

        Starting MRR + Expansion - Contraction - Churn
NRR = ─────────────────────────────────────────────────── × 100
                        Starting MRR

Target NRR by segment:
- Enterprise: 115-130%+
- Mid-market: 105-115%
- SMB: 95-105%

The CS Tech Stack

LayerFunctionExample Tools
Core PlatformCustomer 360, health scoresGainsight, ChurnZero, Totango
Data LayerProduct analytics, usageAmplitude, Pendo, Mixpanel
EngagementIn-app, email automationIntercom, Customer.io, Appcues
FeedbackSurveys, NPSDelighted, Wootric, Satismeter
IntelligenceChurn prediction, next best actionPlanhat, Catalyst

Customer Journey Stages

PRE-SALES → ONBOARDING → ADOPTION → VALUE → EXPANSION → ADVOCACY
     ↓           ↓           ↓        ↓          ↓           ↓
  Handoff    Time-to-    Feature   Outcome   Expansion   Reference
  Quality    Value       Adoption  Achieved  Opportunity Customer

The Value Realization Framework

PhaseDefinitionDeliverable
DefineAgree on success criteriaSuccess Plan
DeliverExecute implementation & onboardingGo-Live
DemonstrateProve value with metricsValue Report
DevelopExpand usage and outcomesGrowth Plan

Key Metrics Reference

MetricDefinitionGoodGreat
NRRNet Revenue Retention105%+120%+
GRRGross Revenue Retention90%+95%+
Logo RetentionCustomers retained85%+92%+
NPSNet Promoter Score30+50+
CSATCustomer Satisfaction4.0/54.5/5
CESCustomer Effort Score<3<2
Time to ValueDays to first outcome<30<14
Health ScoreComposite customer health70+ avg80+ avg

Coverage Model Decision Framework

FactorHigh TouchLow TouchTech Touch
ARR$100k+$15k-100k<$15k
ComplexityHighMediumLow
Strategic ValueHigh potentialStandardTransactional
Touch FrequencyWeekly-MonthlyMonthly-QuarterlyAutomated
CSM Ratio1:10-251:50-1001:500+
Cost to Serve15-25% of ARR5-10% of ARR<3% of ARR

Anti-Patterns

  • Measuring activities over outcomes — Calls logged ≠ customers retained
  • One playbook for all segments — Tech touch playbooks for enterprise fail
  • CS as support escalation — Reactive mode kills proactive capacity
  • Health scores without action — Red accounts need intervention, not dashboards
  • Siloed CS data — CS platform not integrated with CRM/Product
  • CSM as single thread — Champion leaves, relationship collapses
  • QBRs as PowerPoint theater — Value delivery, not presentation
  • Ignoring tech touch — 80% of customers, 20% of attention

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.39%
按下载量换算190

Claude

31.01%
按下载量换算166

Cursor

19.91%
按下载量换算107

Gemini CLI

8.08%
按下载量换算43

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills