success-renewal-management@1.0.0
VERIFIEDPublisher claims: "Use when 存量客户合同临近到期(180/120/90/60/30 天节点)需要系统化推进续约——判断健康/风险档位、按档位走续约动作、出续约方案、开续约对话、收续约成交。Triggers: '续约','续费','合同到期','续约风险','续约预测','续约方案','续约对话','save 计划','续约健康分','renewal','renewal playbook','churn prevention','续约率','NRR','GRR','多年期续约'. Do NOT use for new-deal pricing (clinch-negotiation-pricing), account expansion (success-expansion; only renews existing contract), or lost-customer win-back (churn-recovery)." 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 574 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.