Skills/ClawHub/hokkaido-travel-companion

hokkaido-travel-companion@1.0.0

CAUTION· static only

Publisher claims: "Hokkaido/Sapporo/Otaru/Yoichi travel companion protocol. Specifies how to collect, verify, store, and reuse travel knowledge with a local vault plus live sea..." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher ico1036 · publishing for 164 daysInstalls 662Last detonated 9 h 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-14 and scored it 66/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Auto-update or dynamic fetch configuration. 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

HIGH
Auto-update or dynamic fetch configurationSKILL.md:93 · Auto-update or dynamic fetch configuration — agent may load new code at runtime- **Auto-update**: any field >3 months old → re-search before answeringFix: Pin versions and sources; vendor anything fetched at install time.
AST06

No other findings across 235 lines in 4 files.

Cost to the agent

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

14 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim ico1036: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim ico1036Propose a patch to the maintainer