clinch-progression-strategy@1.0.0
VERIFIEDPublisher claims: "Use when a live deal is stuck or stalled and the rep needs an overall advancement plan — not a single-call debrief, not a live objection reply, not a closing push, but a forward plan from current state to signed contract. Triggers: '这个单卡住了怎么推', '从现在到签约还要过哪几关', '推进思路', 'deal progression', 'advancement plan', 'next steps roadmap', 'stuck deal path forward', '商机推进路径', '分阶段动作清单'. Do NOT use for single-communication debrief, live objection handling, final-mile closing sequence, invest-or-not decision, or deal health diagnosis." 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 625 lines in 6 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.