Skills/ClawHub/git-standup

git-standup@1.0.0

CAUTION· static only

Publisher claims: "Generate a daily standup report from git commit history. Groups commits by author, lists what was done yesterday, what's planned today, and highlights any blockers. Use at the start of the workday or before a standup meeting." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher terrycarter1985 · publishing for 187 daysInstalls 155Last detonated 5d 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-09 and scored it 71/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 199 lines in 3 files.

Cost to the agent

Instructions loaded
≈407 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

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