Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Videoinu
v1.0.1Videoinu platform skill — manage projects via Graphs (canvases), upload/download files, chat with AI Agents, and run Workflows. Use when: user mentions Video...
⭐ 0· 33·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's name/description and included Python scripts consistently implement a Videoinu client (graph management, uploads, agent chat, workflows). However the registry metadata for the skill claims no required environment variables or primary credential, while SKILL.md and the code clearly require an access key (VIDEOINU_ACCESS_KEY) and read ~/.videoinu/credentials.json. That metadata omission is an incoherence that affects trust and permission review.
Instruction Scope
The SKILL.md instructs the agent/user to use the bundled Python scripts and not to call the API directly; the scripts do exactly what is described (HTTP calls to BASE_URL, WebSocket chat, upload/download files). The scripts read an access key from an env var or ~/.videoinu/credentials.json and use it as a Cookie header to call the Videoinu API. They access only the user's home (~/.videoinu) for credentials and standard local files for upload/download. There are no unexpected remote endpoints embedded in the code; the API base is configurable via VIDEOINU_API_BASE (defaults to https://videoinu.com).
Install Mechanism
There is no install specification that downloads or executes remote artifacts; the skill is delivered as code files (Python scripts) and SKILL.md. The scripts only use the Python standard library. No external package downloads or third-party install URLs are present in the bundle.
Credentials
The code requires a sensitive credential (VIDEOINU_ACCESS_KEY) and will persist it to ~/.videoinu/credentials.json if the provided auth helper is used. The registry metadata did not declare this required env var/primary credential, which is a mismatch. The credential is treated as a JWT and used as a Cookie token for API requests — leaking it would enable account access. Aside from the access key and optional VIDEOINU_API_BASE, no other credentials are requested.
Persistence & Privilege
The skill does not request 'always: true' and will not force-install itself. It writes a credentials file to ~/.videoinu when you run auth.py save; auth.py sets file permissions to owner read/write only. The skill does not modify other skills' configs or system-wide settings. Agent autonomous invocation is allowed (default) but not uniquely risky here.
What to consider before installing
This package appears to be a real Videoinu CLI implemented in Python and performs the operations described, but there are a few actionable concerns to consider before installing:
- Metadata mismatch: The skill registry entry claims no required credentials, but SKILL.md and the code require VIDEOINU_ACCESS_KEY and read/write ~/.videoinu/credentials.json. Treat this as a red flag in the publisher hygiene (ask publisher to correct metadata).
- Sensitive token handling: The access key is effectively an account token (JWT). Prefer exporting VIDEOINU_ACCESS_KEY in a secure environment rather than saving it with auth.py unless you trust the machine and the skill. If you do save it, auth.py sets restrictive permissions, which is good.
- BASE_URL is configurable: The code respects VIDEOINU_API_BASE, which if set to a malicious host would cause credentials and data to be sent there. Do not set VIDEOINU_API_BASE to an untrusted URL.
- Code review: The included scripts are readable and use only the standard library (no obfuscated or downloader logic). If you do not trust the publisher or the unknown source, consider running the scripts in an isolated environment (VM/container) or manually inspecting the files (they are provided) before use.
- Verification steps: Run `python3 auth.py status` and `python3 auth.py verify` (the latter will call the API) to confirm expected behavior. If you want stronger guarantees, ask the publisher to: (1) publish a homepage/source link, (2) correct the registry metadata to declare VIDEOINU_ACCESS_KEY as the primary credential, and (3) sign/release the package from a known source.
Given the metadata omission and the sensitivity of the access token, I rate this as suspicious (medium confidence) rather than clearly benign. If you trust the skill's origin and videoinu.com, the code appears consistent with its stated purpose.Like a lobster shell, security has layers — review code before you run it.
latestvk97f5th13treznw87g8pdh6dss8459fe
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎬 Clawdis
Binspython3
