ljh-koc@1.0.0
CAUTION· static onlyPublisher claims: "KOC 验证方案设计与验证报告生成。还没铺就帮你设计验证方案，跑完了就帮你判定结果并出报告。 触发方式：/ljh-koc、「帮我设计一个 KOC 验证方案」「KOC 数据跑完了帮我出个报告」「这个卖点该怎么验」 KOC validation plan design and validation report generation. Design a plan before launch, judge results and write a report after data comes in. Trigger: /ljh-koc, "help me design a KOC validation plan", "help me write a validation report from this data" 明星代言合作方案、品牌公关声明这类非KOC小范围验证场景，不要自动触发。" 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-09 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 342 lines in 2 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 handsomeng: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.