reference-batch@1.0.0
CAUTIONPublisher claims: "输入论文标题 / DOI / 作者信息，一键批量生成 GB/T 7714、APA、MLA 等多格式参考文献条目，自动识别文献类型（期刊 / 学位论文 / 会议 / 图书 / 网络资源），输出可直接复制的参考文献列表。批量粘贴多篇文献标题、作者或 DOI 链接，自动识别类型并输出多种引用格式的完整清单，无格式错乱，可直接粘贴论文末尾。Use when the user asks for 参考文献批量生成、文献格式转换、GB/T7714、APA、MLA、DOI转引用、论文标题转引用、批量整理参考文献、文献类型识别、参考文献列表，或粘贴多篇文献标题/作者/DOI要求批量处理引用条目。" Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-06 and scored it 67/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 405 lines in 3 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
13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim cryptocxf: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.