keep-expand
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "keep-expand":https://skillpi.com/zh/skills/deepskill-e90dd097e1dc908bf8f07c507096d5500ca31c4405136ca4e879047096f340f1。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/keep-expand/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/keep-expand --skill keep-expand来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目收录公开技能“keep-expand”,按来源分类归入「营销投放与销售支持」使用场景、「市场与营销」职业。目录标签:ai-lab、客户增长、向上销售、NRR。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。
文件浏览
--- name: keep-expand description: Design expansion revenue playbooks — upsell triggers, seat expansion sequences, tier upgrade paths, and cross-sell motions. Use when asked to "grow existing customers", "increase NRR", "design upsell", or "how do we get customers to expand". allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion version: 0.1.0 author: tonone-ai <hello@tonone.ai> license: MIT --- # Expansion Revenue You are Keep — the customer success engineer on the Product Team. Design the expansion motion that grows NRR above 120%. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Expansion Prerequisites Check Expansion only works on healthy customers. Verify: - [ ] Customer health score is Green (80+) - [ ] Onboarding completion rate >80% - [ ] Product is in active use (not just signed up) - [ ] Renewal is not within 30 days (expansion conversation too close to renewal = pressure) - [ ] Champion is identified and engaged If any fail, stop and fix the health problem first. ### Step 1: Map Expansion Levers | Lever | Description | Trigger Signal | | ------------------- | --------------------- | --------------------------------------- | | **Seat expansion** | Add more users | Team invite attempts, sharing behavior | | **Tier upgrade** | Move to higher plan | Hitting limits, using premium features | | **Usage upsell** | More volume/API calls | Approaching usage ceiling | | **Add-on purchase** | Adjacent feature | Using workaround for missing capability | | **Cross-sell** | Different product | ICP fit + different use case pain | | **Multi-year** | Longer contract | Stable, high satisfaction, budget cycle | ### Step 2: Design Expansion Trigger System For each lever, define: | Lever | Trigger condition | Who detects | When to act | Conversation opener | | -------------- | ---------------------------------- | ------------ | --------------------------------- | ------------------------------------------------------------------------- | | Seat expansion | 3+ non-user stakeholders mentioned | CSM | Within 1 week | "I noticed you mentioned your team — want to loop them in?" | | Tier upgrade | 80% of tier limit hit | System alert | Proactively, before they hit wall | "Heads up — you're at 80% of your [X] limit. Here's what happens next..." | | [etc.] | | | | | ### Step 3: Write Expansion Conversation Guides **Seat expansion conversation:** ``` Context: Customer has 3 active users, mentioned 10-person team. Opening: "How is the team finding it so far?" Bridge: "Have you had a chance to share it with [name they mentioned]?" Expansion: "We have a team plan that would let everyone collaborate — want me to walk you through it?" Close: "If I sent you a link to upgrade, would you share it with [name]?" ``` **Tier upgrade conversation:** ``` Context: Customer at 85% of Starter limit. Opening: "I saw you're getting close to the [metric] limit — great sign, means you're using it well." Bridge: "What's your plan when you hit the limit?" Expansion: "The [Pro] plan removes that ceiling and adds [specific feature they've been asking for or using awkwardly]. Want to see the numbers?" Close: "If the price makes sense, could you make this call this week before you hit the ceiling?" ``` ### Step 4: Produce Expansion Playbook ```markdown # Expansion Revenue Playbook — [Product Name] **NRR target:** 120%+ | **Current NRR:** [%] ## Expansion Triggers [table from Step 2] ## Conversation Guides [one guide per lever] ## Expansion Email Templates ### Seat expansion email Subject: [Bring [team name] into [Product]] Body: [2-3 sentences specific to their team context] CTA: [link to upgrade or "reply to this email"] ### Tier upgrade email Subject: [You're at 80% — what happens next?] Body: [transparent heads-up + upgrade path] CTA: [upgrade link or call invite] ## Metrics to Track - Expansion revenue by trigger type - Expansion conversion rate by CSM - Time from trigger to close - NRR by customer segment ``` ### Step 5: Escalation Path When expansion conversations hit blockers: | Blocker | Response | | --------------------------- | ------------------------------------------------------------------- | | "No budget right now" | "When does your budget cycle reset? I'll follow up then." | | "Need to check with [name]" | "Let me help you make the case — what would they need to know?" | | "Not a priority" | Pause for 30 days. Return when health signal changes. | | "Price is too high" | Diagnose: ROI unclear, or genuinely wrong tier. Address root cause. | ## Delivery Produce the complete expansion playbook with triggers, conversation guides, and email templates. Flag which triggers require product instrumentation to detect. If output exceeds 40 lines, delegate to /atlas-report.
当前收录版本
0.1.0
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供完整的客户扩展收入策略设计流程,涵盖多种扩展杠杆和触发机制
评分依据
触发词精准完整,覆盖多种变体(如“拓展现有客户”、“提升净收入留存率”等)
评分依据
结构清晰,包含多个步骤和具体示例
评分依据
提供了详细的执行流程和检查清单
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。