chatbot-designer@1.1.0
CAUTION· static onlyPublisher claims: "Design customer service chatbot conversation flows for ecommerce — order status, returns, product recommendations, and escalation rules — that reduce ticket..." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-14 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Refusal suppression. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
4. **Copy-pasting canned responses** — Bot responses that sound like they came from a 2005 helpdesk FAQ kill the experience. Write for conversation, not documentation.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.6. **Ignoring mobile UX** — Most customer service chatbot interactions happen on mobile. Long menus, small tap targets, and text-heavy responses that require scrolling kill completion rates.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.1. Never apologize for failing — transition warmly: "Let me get someone on our team to help with this."Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.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.
What would make this Verified
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim leooooooow: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.