Skills/ClawHub/launch-check

launch-check@1.0.2

VERIFIED· install only

Publisher claims: "Launch readiness check and launch checklist for the current GitHub repository. Scores it 0-100 by fixed rules (README clarity, install line, licence, releases, CI, activity), shows the three fixes worth the most, offers to make them locally, and only if the human says yes, lists the project on ScBee. Use when someone asks "is this ready to launch?", "what should I fix before I ship?", "is my open source project ready?", or wants a pre-launch checklist for this repo." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher hmakt99 · publishing for 237 daysInstalls 60Last detonated 7 h ago
$clawhub install launch-check
WatchReport an issue

Coverage

Nothing executable in the bundle ran; the trace covers the install step only.
Tested
every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

What changed since 1.0.1

vet-skills diff launch-check 1.0.1 1.0.2

In the sandbox, this version reached for nothing 1.0.1 did not. Compared from the two recorded runs, not from source.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-19 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 1 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessscript backend runs setup only
0.0sprocessscript backend runs setup only
0.0sprocessno install scripts to re-run

Static findings

MEDIUM
File type combined with upload actionSKILL.md:36 · File type combined with upload action — agent may exfiltrate local data files…here but https://scbee.vercel.app) and a token. Write the token to `scbee-verify.txt` at the repo root; the human commits and pushes it; then `POST https://scbee.vercel.app/api/verify` with `Authorization: Bearer <api_key>`. Th…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07

No other findings across 94 lines in 2 files.

Cost to the agent

Instructions loaded
≈993 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.