Skills/ClawHub/reviewcourt

reviewcourt@1.0.1

CAUTION· static only

Publisher claims: "基于腾讯会议官方 tmeet CLI 的会后需求评审裁决 Skill。当用户需要复盘需求评审、PRD 评审或技术方案评审会议，判断需求是通过、有条件通过、驳回还是信息不足，并从智能纪要和逐段转写中提取质疑、答复、阻塞条件、原话证据与验收标准时使用；也用于用户同时提供 PRD、需求文档或方案文档，要求核对会议结论与..." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher chris1wang3 · publishing for 116 daysInstalls 581Last detonated 3d ago
What would fix thisWatchDispute verdict

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-11 and scored it 69/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

LOW
Unpinned dependencySKILL.md:74 · Unpinned dependencynpm install -g @tencentcloud/tmeet@latestFix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
AST06

No other findings across 671 lines in 4 files.

Cost to the agent

Instructions loaded
≈1,269 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

11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim chris1wang3: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Unpinned dependencies≈ +1 on the totalPin exact versions (and ideally hashes) in package.json, requirements or the install script so the bundle cannot change under you.
  3. Unpinned dependency≈ +1 on the totalPin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim chris1wang3Propose a patch to the maintainer