success-expansion@1.0.0
VERIFIEDPublisher claims: "Use when a customer is already live and producing value, and the rep+CS need to identify account-expansion opportunities (upsell / cross-sell / seat / new-module / new-department) from usage and organizational signals, build a structured expansion case, run the expansion conversation, and hand off to renewal or downstream deal flow. Triggers: '增购', '向上销售', '交叉销售', '加坐席', '升级套餐', '加模块', '账户拓展', 'upsell', 'cross-sell', 'land and expand', 'NRR'. Do NOT use for new-logo acquisition, renewal itself (success-renewal-management), pricing negotiation (clinch-negotiation-pricing), contract signing, or first-value proof (its usage data is INPUT here)." 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 614 lines in 8 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.