success-churn-recovery@1.0.0
VERIFIEDPublisher claims: "Use when 已成交客户已流失（不续约/停用/被竞品替换/公司解散/合同到期未续/战略转型）——帮销售/CS 判定求救方 vs 借刀方、识别 Champion 政治处境、设计 D-X 倒排计划、内置 30 天联合验证期 Plan B、设 3 个停手信号，把可能赢回的客户救回来。Triggers: '流失挽回', '客户流失', '客户挽留', '赢回', '把客户赢回来', '客户不续约', '被竞品替换', '合同到期未续', '客户停用', '国产化替换', 'churn recovery', 'win-back', 'customer reactivation', 'lost customer recovery'. Do NOT use for churn prediction, renewal prevention (success-renewal-management), or pre-deal lost leads." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario) on 2026-11-06 and scored it 93/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
No findings across 1,548 lines in 9 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.