fee-collection@1.0.0
CAUTION· static onlyPublisher claims: "费用催缴管理技能。基于《C+基础保障服务手册-企服管理工作规程》第十一章，实现规范的费用催缴流程，包括智能分级催缴、个性化话术、能耗欠费合并计算等。触发场景：(1) 定时检查费用收缴状态（每天10:00），(2) 手动触发催缴检查（@企服助手 催缴检查），(3) 企微群关键词触发（@催缴），(4) 逾期分级处理（..." 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-13 and scored it 71/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. 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
No findings across 1,218 lines in 12 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.
What would make this Verified
9 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim perrykono-debug: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.