dining@2.1.0

CAUTION· static only

Publisher claims: "Dining OS v2.1——硬核膳食决策引擎。当用户面临"今天吃什么/做什么饭/点什么外卖"的决策困境时立即触发。覆盖场景:为1-N人规划下厨/堂食/外卖菜单、家庭/商务/同学聚餐方案设计、减脂增肌健身餐规划、厨艺展示选菜、露营/火锅/全素等特殊场景。核心能力:约束满足优化(忌口/过敏/健康红线)、快速盲选与..." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher chenchen913 · publishing for 169 daysInstalls 801Last detonated 1 h ago

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 70/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 only
t+CategoryObserved action

This 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,549 lines in 12 files.

Cost to the agent

Instructions loaded
≈1,412 tok
1 file · 12 in bundle

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

10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim chenchen913: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim chenchen913Propose a patch to the maintainer