Skills/ClawHub/feishu-weekly-report

feishu-weekly-report@1.0.1

CAUTION· static only

Publisher claims: "生成飞书周报。通过两种方式收集工作内容:(1) 调用飞书API拉取指定时间范围的聊天记录,(2) 读取本地daily memory日志。 合并两个数据源后,按用户指定的周报模板自动整理输出。 触发词:周报、工作总结、上周总结、本周总结、写周报、weekly report。 Use when: 用户需要生成周报、工..." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher hakityc · publishing for 264 daysInstalls 1,848Last detonated 16 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-20 and scored it 72/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 222 lines in 3 files.

Cost to the agent

Instructions loaded
≈532 tok
1 file · 3 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

8 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim hakityc: 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 hakitycPropose a patch to the maintainer