Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
MeowMusic YouTube MP3
v0.1.0Package and reuse the MeowMusicServer-patched YouTube fallback workflow: Windows Chrome cookie export/sync to server, server-side yt-dlp/yt-dlp-ejs/ffmpeg se...
⭐ 0· 51·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 files (install script and cookie-sync script) align with the described goal of syncing Windows Chrome cookies to a server and enabling yt-dlp/ffmpeg downloads. However, the SKILL.md references additional helper Windows scripts that are not present in the file manifest and the skill metadata declares no required env vars even though the workflow expects MEOW_SERVER_URL and MEOW_BEARER_TOKEN.
Instruction Scope
Runtime instructions explicitly tell an operator/agent to export local browser cookies and POST them to a remote server endpoint. That behavior is consistent with the intended purpose but is inherently sensitive: it reads local browser cookie material and transmits it to an external server. The instructions do not attempt to read unrelated system files, but they do assume permission to modify repos and server code (patching an existing service) which can have broad impact if done automatically.
Install Mechanism
There is no opaque or remote install step embedded in the skill bundle itself. The provided install_server_env.sh bootstraps a Debian/Ubuntu host using official NodeSource, apt, pip, and npm sources (nodesource.com, pip, npm). These are standard and proportionate to installing yt-dlp, yt-dlp-ejs and ffmpeg.
Credentials
The package metadata declares no required environment variables, but both documentation and scripts rely on MEOW_SERVER_URL and MEOW_BEARER_TOKEN (the python script will exit if token is missing). Requesting a bearer token and a server URL is reasonable for the cookie-upload workflow, but the omission from declared requirements is an inconsistency and reduces transparency. The skill does not request unrelated cloud credentials or wide-ranging secrets.
Persistence & Privilege
The skill is instruction-only with no 'always' privilege. It does not request persistent, system-wide configuration changes beyond advising edits to the target repo and writing a youtube-cookies.txt file on the server (server-side handler in docs writes to ./youtube-cookies.txt). There is no indication it would modify other skills or agent configs.
What to consider before installing
This skill appears to do what it says (enable Windows->server cookie sync and a yt-dlp+ffmpeg fallback), but take these precautions before installing or running it:
- Understand the sensitive action: youtube_cookie_sync.py exports local browser cookies and uploads them to a server. Only run this on machines and profiles you trust and with explicit user consent. Do not use production browser profiles unless you fully trust the receiving server.
- Verify and restrict the server endpoint: review and, if you implement the server handler, ensure it authenticates correctly, writes cookie files atomically with restrictive permissions (0600), and that the bearer token has minimal scope and expiration. Prefer short-lived or limited-scope tokens.
- Metadata mismatch: the skill metadata does not list MEOW_SERVER_URL or MEOW_BEARER_TOKEN as required env vars even though the scripts use them. Expect to provide those values; verify where you store them.
- Missing referenced files: SKILL.md mentions Windows helper .bat scripts that are not in the package. Confirm whether those helpers are required and obtain or reimplement them from trusted sources.
- Test in a sandbox: run the install script and cookie-sync flow in an isolated test VM/server first (not on production), and inspect produced files and network requests (use a local intercepting proxy if needed).
- Review code and server-side implementation: inspect the server endpoint that receives cookies before sending anything. Confirm logging policies so cookies are not written to logs.
- If you want tighter safety: avoid uploading real cookies; instead create a disposable test account/profile or a restricted token. Rotate any tokens used after testing.
Given the inconsistencies (undeclared env vars, missing helper files) and the sensitive nature of cookie export/upload, proceed only after manual review and with mitigations in place.Like a lobster shell, security has layers — review code before you run it.
latestvk97bkpqqn74bdpnk0bp9ebcwzd83nyct
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
