Skills/ClawHub/research-yc-launch-demos-and-document-an-oysterw-6def94d0

research-yc-launch-demos-and-document-an-oysterw-6def94d0@1.0.0

CAUTION· static only

Publisher claims: "Research comparable YC launch demos and build a structured Google Doc for OysterWorkflow demo-video planning, including candidates, links, analysis dimension..." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher shuxinyang111 · publishing for 126 daysInstalls 825Last detonated 3d 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-11 and scored it 70/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 214 lines in 2 files.

Cost to the agent

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

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