Skills/ClawHub/upward-reporting

upward-reporting@1.0.1

CAUTION· static only

Publisher claims: "职场汇报文档写作的总入口与路由。当用户说"写汇报"、"写文档"、"帮我写材料"但未明确场景时触发,帮助识别场景并路由到对应子skill。也提供所有汇报场景通用的风格规范和汇报对象适配指南。子skill:report-planning(规划汇报)、report-postmortem(故障复盘)、report-rev..." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher sopaco · publishing for 187 daysInstalls 864Last detonated 25 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 3,389 lines in 18 files.

Cost to the agent

Instructions loaded
≈7,311 tok
6 files · 18 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 sopaco: 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 sopacoPropose a patch to the maintainer