Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Byted Las Audio Extract And Split
v1.0.1Extracts audio tracks from video files and splits long audio into timed segments using Volcengine LAS. Audio extraction and separation from video — pull audi...
⭐ 0· 79·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
high confidencePurpose & Capability
The skill claims to be an audio-extraction/splitting wrapper for Volcengine LAS, which is plausible, but the package metadata lists no required environment variables or binaries while the SKILL.md and scripts clearly require LAS_API_KEY (and potentially VOLCENGINE_ACCESS_KEY/VOLCENGINE_SECRET_KEY), ffprobe, and the lasutil CLI. Those missing declarations are an incoherence: a genuine integration should declare the required credentials and required binaries.
Instruction Scope
Runtime instructions tell the agent to source scripts/env_init.sh (which fetches a remote manifest and may install a wheel), run ffprobe locally to inspect files, upload local files to TOS via lasutil, and to prompt the user for API keys. The SKILL.md also instructs the user to create an env.sh file containing export LAS_API_KEY — encouraging placement of secrets in the working directory. The instructions access environment variables and external endpoints that were not declared in the skill metadata, and grant the agent broad runtime discretion to perform network installs and uploads.
Install Mechanism
Although there is no declared install spec in the registry, scripts/env_init.sh fetches a manifest from https://las-ai-cn-beijing-online.tos-cn-beijing.volces.com and will pip-install a wheel from that URL at runtime. This runtime network fetch + pip install is effectively installing arbitrary remote code without being declared in the registry metadata. Even if the host is Volcengine-related, an undeclared runtime install is higher-risk and should be explicit and audited.
Credentials
The SKILL.md requires LAS_API_KEY and may require VOLCENGINE_ACCESS_KEY/VOLCENGINE_SECRET_KEY and LAS_REGION, but the skill metadata lists no required env vars. The instructions also tell the user to place API keys in a local env.sh file for automatic reading, which increases the chance of accidental credential leakage. Requesting cloud credentials is reasonable for this integration, but omitting them from the declared requirements and instructing ad-hoc secret placement is disproportionate and confusing.
Persistence & Privilege
always:false (good). The skill creates or reuses a virtualenv (.las_venv) in the project root and creates a temp working directory (LAS_WORKDIR). Creating or reusing a project-level virtualenv is persistent filesystem activity that can affect the host environment; this is expected behavior for runtime setup but should be called out to users (and ideally run in an isolated environment).
What to consider before installing
This skill is plausible for LAS audio splitting but has several inconsistencies and runtime behaviors you should be comfortable with before installing. Things to consider: 1) The SKILL.md and scripts require LAS_API_KEY (and possibly VOLCENGINE access keys and LAS_REGION) and CLI tools (ffprobe, lasutil), yet the registry metadata lists none — ask the author to declare these explicitly. 2) The env_init.sh script downloads a manifest and pip-installs a wheel from a remote URL at runtime; verify that URL and the wheel's integrity (and prefer running this in an isolated VM/container). 3) Do not paste long-lived secrets into chat; avoid committing env.sh with exports into a repo — use short-lived keys and rotate them. 4) If you plan to run this, ensure ffprobe/lasutil are available or the environment can safely install needed binaries, and run the skill in a disposable environment (container) so the pip-installed code and created .las_venv cannot affect other projects. 5) If the publisher cannot explain why metadata omits required env vars and binaries, treat this as an additional red flag and avoid using it with real production credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk976wvr996fds9wqybj0xk2ttx850m20
License
MIT-0
Free to use, modify, and redistribute. No attribution required.