openclaw-bottle-drift-skill
v1.0.0面向 OpenClaw 节点的互动式漂流瓶 Skill。支持网页控制台、在线用户心跳、随机投递、专属回复链接与回信收取。
⭐ 0· 121·0 current·0 all-time
byvx：17605205782@52yuanchangxing
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (a relay + web dashboard for sending/receiving 'drift bottles') align with the included scripts and web resources. Required binary (python3) is appropriate. No unrelated credentials, unusual binaries, or config paths are requested.
Instruction Scope
SKILL.md instructs running the local relay and using the built‑in web console or CLI. That scope matches the code. Note: the system supports optional callback_url/webhook fields and exposes per‑delivery reply URLs; those are legitimate features but increase the attack surface when the relay is exposed publicly (the README and SELF_CHECK acknowledge this).
Install Mechanism
No install script or external download is declared; bundle contains pure Python standard‑library code and static web assets. This is low risk from an install mechanism perspective.
Credentials
The skill declares no required environment variables or credentials. The code stores identities in browser localStorage and uses a local SQLite DB — both are proportional to the described purpose. There are no unexplained secret requests.
Persistence & Privilege
The skill is not always‑on and does not request elevated privileges. It persists to a local SQLite database in the bundle directory (expected for this use). It does not modify other skills or global agent settings.
Assessment
This bundle appears coherent for running a local Bottle‑Drift relay/dashboard. Before installing or exposing it publicly: 1) Inspect relay_server.py for any outbound webhook/callback behavior (the code accepts callback_url values and may invoke them in some deployments) and decide whether that is acceptable. 2) Run it on localhost first and verify behavior; the README and SELF_CHECK recommend HTTPS/reverse proxy/rate limits before public exposure. 3) Treat generated reply_url tokens as sensitive — anyone with a token can submit the one allowed reply. 4) Browser identity is stored in localStorage (not secure authentication). 5) If you must expose it to the Internet, put it behind TLS, a reverse proxy, IP/connection limits and/or an authentication layer, and review the DB path and file permissions. If you want higher assurance, request the full, untruncated relay_server.py and confirm whether the service performs any outbound HTTP requests (webhooks) or executes external programs.Like a lobster shell, security has layers — review code before you run it.
latestvk974dtn9ppme8jpjsdqca6pa0s8331zy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🍾 Clawdis
Any binpython3