Skills/ClawHub/coze-image-2

coze-image-2@0.1.0

CAUTION· static only

Publisher claims: "扣子(Coze) Seedream 4.5 图片生成工具。通过 Coze API 调用图片生成工作流,支持文本生成图片。 当用户要求"生成图片"、"AI画图"、"用Coze生成图片"时触发。" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher rookiebug1216 · publishing for 198 daysInstalls 795Last detonated 29 min 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-22 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 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 312 lines in 4 files.

Cost to the agent

Instructions loaded
≈225 tok
1 file · 4 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

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