Token导航 LogoToken导航

Agent Skill · 研究检索

win-back(赢回来)

win-back 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

win-back 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 46,073。

总安装 808周安装 34GitHub Stars 37下载 283核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill win-back

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息。适合根据关键词或任务场景快速定位候选结果。可结合来源仓库和原始 README 核验具体用法。

安装命令:npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill win-back 安装前建议确认权限范围和是否会触发联网。

来源仓库内路径:skills/win-back

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

win-back 怎么安装?

在终端执行 npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill win-back。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

win-back 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

win-back 需要什么权限?

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

win-back 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

win-back 用的人多吗?

公开数据是累计安装 808 次,近一周安装 34 次,下载 283 次,GitHub 37 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

win-back 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
win-back

赢回来 · 本页

80837只读未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Win-Back Campaign Designer

Conversation Starter

Use AskUserQuestion to gather initial context. Begin by asking:

"I'll help you design win-back campaigns to recover churned and dormant customers.

Please provide:

  1. Business Type: What do you sell? (SaaS, e-commerce, subscription, service)
  2. Churn Definition: How do you define 'churned' vs 'dormant'?
  3. Churn Reasons: Why do customers typically leave? (if known)
  4. Customer Value: What's the average customer lifetime value?
  5. Past Attempts: Have you tried win-back campaigns before? Results?
  6. Available Data: What data do you have on churned customers?

I'll research win-back benchmarks and design campaigns tailored to your churn reasons."

Research Methodology

Use WebSearch extensively to find:

  • Win-back email benchmarks (open rates, recovery rates)
  • Optimal timing for win-back campaigns by industry
  • Exit survey best practices and question templates
  • Re-engagement offer effectiveness studies

Required Deliverables

1. Churn Segmentation Framework

By Churn Reason:

SegmentWin-Back DifficultyApproach
Price-sensitiveMediumValue + discount
CompetitionHardFeature comparison
Non-usageEasyRe-education
Poor experienceMediumApology + fix proof
Changed needsVery hardFuture trigger
Payment failureEasyUpdate prompt

By Recency:

SegmentTime Since ChurnRecovery RatePriority
Fresh0-30 days15-25%Highest
Recent31-90 days8-15%High
Aged91-180 days3-8%Medium
Stale180+ days1-3%Low

Prioritization Matrix: Cross LTV tier with recency to determine approach (personal outreach vs automated).

2. Win-Back Email Sequence (5 emails)

EmailDayPurpose
Check-In7Acknowledge absence, open dialogue
Value Reminder14Show what they're missing
The Offer21Incentive to return
Last Chance30Final push with urgency
Goodbye45Close loop, leave door open

Full email copy: assets/email-sequence.yaml

3. Win-Back Offer Framework

Churn ReasonRecommended Offer
Price-sensitiveDiscount 25-50%, downgrade option
CompetitionFeature match, switching assistance
Non-usageFree training, onboarding call
Poor experienceApology + credit, priority support

Discount tiers by customer value and non-discount alternatives: assets/offers-feedback.yaml

4. Exit Survey & Feedback Collection

  • Exit survey questions (at cancellation)
  • Churned customer interview script
  • Post-loss referral email template
  • Feedback analysis template

Full templates: assets/offers-feedback.yaml

5. Automation Triggers

TriggerDefinitionSequence
Soft churnNo login 30 days (active sub)Re-engagement
Hard churnCancelled subscriptionWin-back
Payment churnFailed payment, no updateDunning then Win-back
DormantNo activity 60 daysRe-activation

Suppression Rules:

  • Opted out of marketing
  • Already in win-back sequence
  • Won back in last 90 days
  • Churned 3+ times

6. Success Metrics

MetricBenchmark
Win-back rate5-15%
Win-back CAC< Original CAC
Second-churn rate<50% in 6 months

Email Metrics by Stage:

EmailOpen RateClick RateConversion
Check-in30-40%5-10%N/A (replies)
Value reminder25-35%8-15%2-5%
Offer35-45%15-25%5-10%
Last chance40-50%20-30%5-10%

ROI Calculation:

Win-back ROI = (Revenue Recovered - Campaign Cost) / Campaign Cost × 100

Example: 1,000 contacted × 10% win-back × $50 MRR × 12 mo = $60K recovered
Campaign cost: $2K → ROI: 2,900%

Output Format

# WIN-BACK CAMPAIGN BLUEPRINT: [Business Name]

## Executive Summary
[Churn situation and recovery strategy]

## Churn Segmentation
[Customer segments with prioritization]

## Win-Back Email Sequence
[5 emails with complete copy]

## Offer Framework
[Offers by segment and churn reason]

## Exit Feedback System
[Survey, interview script, analysis template]

## Automation Triggers
[Technical trigger logic]

## Success Metrics
[KPIs and tracking setup]

## Implementation Checklist
[ ] Set up churn segmentation
[ ] Build exit survey
[ ] Create email sequence
[ ] Configure automation triggers
[ ] Define offers by segment
[ ] Launch to fresh churn first
[ ] Monitor and optimize weekly

Quality Standards

  • Segment-specific: Different approaches for different churn reasons
  • Empathy-first: Acknowledge the relationship, not just the transaction
  • Data-driven offers: Base discounts on economics, not desperation
  • Feedback loop: Always collect data to prevent future churn
  • Measurable outcomes: Clear metrics for success

Tone

Empathetic but direct. Write like a customer success leader who genuinely wants customers back—but respects their decision if they've moved on. No desperation, no manipulation—just honest outreach.

平台分布

Codex

33.48%
按下载量换算95

Claude

32.47%
按下载量换算92

Cursor

17.28%
按下载量换算49

Gemini CLI

9.54%
按下载量换算27

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills