Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Line Client
v1.0.0LINE messaging integration via Chrome extension gateway. Send/read LINE messages, manage contacts, groups, profile, and reactions. Authenticate with QR code...
⭐ 3· 520·0 current·0 all-time
byKenk@2manslkh
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The description says it's a LINE client using a Chrome-extension gateway, which could legitimately need to talk to that gateway. However the SKILL.md expects a Node HMAC signer (auto-starting on port 18944), Python QR login scripts, and WASM files in a repo path — none of these runtime dependencies, binaries, or config paths are declared. The skill also expects a local token store (~/.line-client/tokens.json). Requiring local services, runtime artifacts, and persistent token files is disproportionate to what the registry metadata claims (no binaries, no env, no config paths).
Instruction Scope
Runtime instructions tell the agent to read tokens from the user's home (~/.line-client/tokens.json), run Python scripts (scripts/qr_login_server.py), start a Node.js signer, and handle time-sensitive PINs for login. These instructions direct access to sensitive local files and to start network services and polling loops. The SKILL.md gives the agent broad authority to read/write local credential files and to transmit PINs/QR URLs, but the skill metadata did not disclose these file accesses or runtime actions.
Install Mechanism
There is no install spec and no code files bundled in the skill registry entry, yet the instructions reference a repository path (/data/workspace/line-client), source files (Python/JS/WASM), and an auto-starting Node signer. That mismatch means the agent would either need to fetch/checkout external code (not described) or expect the host to already contain those files — both are risky and undocumented.
Credentials
The skill declares no required environment variables or credentials, yet the instructions rely on persistent auth tokens stored in ~/.line-client and imply the need for Node/Python runtimes and networking to the Chrome gateway. Sensitive artifacts (auth_token, refresh_token, certificate cache) are used and written but not declared. This under-reporting of required secrets/config paths is a red flag.
Persistence & Privilege
always:false (good), but the skill instructs storing tokens and certificates under ~/.line-client and to run long-running local services (HMAC signer). Autonomous invocation is allowed by default; combined with the undisclosed persistent credential storage and service startup, this increases the blast radius if the skill is later invoked without explicit user consent.
What to consider before installing
Do not install or run this skill until the author clarifies and fixes these mismatches. Ask for: (1) the complete source code or a trustworthy package/release (GitHub release or official domain), (2) a clear install spec that lists required runtimes (node, python), dependencies, and any commands the agent will execute, (3) explicit declaration of config paths it will read/write (e.g., ~/.line-client/tokens.json, certificate cache), and (4) justification for why a local HMAC signer and WASM are needed. If you must test, run it in an isolated VM/container and never expose real LINE credentials — inspect the signer and QR-login code for network calls and token handling before trusting it. If the publisher cannot provide an official repo/release or explain why no binaries/env are declared, treat the skill as untrusted.Like a lobster shell, security has layers — review code before you run it.
latestvk978h0a1srdsxcdd3dqmfkmwgn81th3f
License
MIT-0
Free to use, modify, and redistribute. No attribution required.