Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Douyin Transcribe
v1.0.1全自动抖音视频下载 + 语音转文字管道。当用户发送抖音链接并要求转写文字、提取字幕、语音转文本时使用。触发词包括"抖音转写"、"抖音文字"、"抖音转文本"、"抖音字幕"、"douyin transcribe"。
⭐ 0· 61·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 name/description (Douyin download + local transcription) matches the code: Node script to obtain a CDN video URL, curl to download, ffmpeg to extract audio, and a local ASR (coli/faster-whisper). However the Node script imports puppeteer-core from a hardcoded /tmp path and launches Chrome at /usr/bin/google-chrome — these hardcoded paths are unusual and not explained in the SKILL.md.
Instruction Scope
SKILL.md instructs installing coli, the sensevoice model, Node/ffmpeg — consistent with purpose — but the code (feishu_upload.py) reads FEISHU_APP_TOKEN and FEISHU_TOKEN from the environment in a subprocess (even though the README doesn't declare these env vars). The Node script navigates to an external parsing site (hellotik.app) and intercepts network requests; that is expected for extracting CDN links but means the skill will load external web content and rely on it. Overall the runtime instructions and code reference environment variables and behaviors not clearly documented.
Install Mechanism
There is no install spec in the registry (instruction-only), which is lower risk, but SKILL.md asks the operator to globally install npm packages and download a ~60MB model from GitHub. The Node script expects puppeteer-core to be available at /tmp/puppeteer_test/node_modules/puppeteer-core and expects a local Chrome binary at /usr/bin/google-chrome; those implicit / non-standard install expectations are fragile and surprising.
Credentials
The registry declares no required env vars, but feishu_upload.py attempts to read FEISHU_APP_TOKEN and FEISHU_TOKEN (via a python -c stub) and the Node script can read DOUYIN_URL from the environment (transcribe.py sets this when invoking). The skill's docs do not declare FEISHU_APP_TOKEN/FEISHU_TOKEN as required; that mismatch could surprise users. Otherwise the skill does not demand broad credentials.
Persistence & Privilege
always is false and the skill does not attempt to modify other skills or system-wide agent settings. It writes temporary files to the specified output dir only and has an optional cleanup flag.
Scan Findings in Context
[pre-scan-injection-none] expected: No static injection signals were detected. That is consistent with the skill being primarily a script-driven pipeline rather than containing obvious obfuscated payloads.
What to consider before installing
This skill appears to implement the stated Douyin→audio→local-ASR pipeline, but there are several things to check before installing or running it: 1) The Node script uses a non-standard import path (/tmp/puppeteer_test/node_modules/puppeteer-core) and expects Chrome at /usr/bin/google-chrome; verify these paths or adjust the script to use your system's Node/pupeteer and Chrome. 2) The script navigates to an external parser site (hellotik.app) and intercepts network traffic to find CDN URLs — this is necessary for the task but means the code loads third-party web content during execution. 3) feishu_upload.py references FEISHU_APP_TOKEN and FEISHU_TOKEN (environment variables) in a placeholder; the SKILL metadata does not declare these. If you plan to use Feishu upload, confirm what credentials are actually required and do not expose broad tokens to untrusted code. 4) The skill instructs installing a global npm ASR CLI and downloading a model from GitHub — these network downloads and global installs should be performed in a controlled environment (container or VM) if you are concerned about supply-chain or permission issues. 5) The Node launch uses Chrome flags like --no-sandbox; running headless Chrome without a sandbox has security implications — prefer running in a sandboxed container. If these oddities (hardcoded paths, undeclared env vars, external site dependency) are acceptable and you review the scripts locally before running, the risk is moderate; otherwise treat the skill as untrusted and run it in isolation or decline to install.Like a lobster shell, security has layers — review code before you run it.
latestvk97cw29scrnnrwvds667w4fkp583vph1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
