YouTube Distiller

Automatically download subtitles from YouTube/Bilibili and generate structured knowledge articles in various summary styles using AI.

This skill mostly does what it claims, but there are several red flags you should address before installing or running it: - Do not trust the embedded API key in the README/dev docs. Treat it as leaked; if you or your org ever used it, rotate/ revoke it immediately. The presence of a literal key in the repo is a security problem. - The skill needs an API key (MINIMAX_API_KEY) though the registry metadata does not declare it — expect to set that env var yourself. Only provide a key you control and are willing to use with this third-party service. - The script expects yt-dlp at a specific Windows path and uses many hardcoded C:\butler_sumo paths. If you run this on a different OS or without those directories the script could fail or create files in unexpected locations. Review and, if needed, change the paths before running. - Review the code (youtube_distiller.py) locally to confirm it only sends subtitle text to the stated API and does not exfiltrate other data. Consider running it in an isolated environment (VM/container) and monitoring outgoing network requests on first run. - If you only want local summaries, consider removing or disabling the API calls and using an offline summarizer (or supply your own provider) so you don't send data to a third-party service. Given these inconsistencies (undeclared env var and binaries, hardcoded file paths, and a leaked-looking API key), treat this skill as suspicious until the repository owner clarifies and removes the exposed credential and documents required dependencies and filesystem behavior.

Type: OpenClaw Skill Name: youtube-distiller Version: 2.1.0 The bundle contains a hardcoded, plaintext MiniMax API key within the development log file (youtube-knowledge-dev.md), which constitutes a significant credential leak vulnerability. While the script's primary function of summarizing YouTube videos via yt-dlp and the MiniMax API is consistent with its documentation, it employs risky practices such as using hardcoded absolute paths on the C: drive (e.g., C:\butler_sumo\...) for file operations and binary execution. These security flaws, particularly the exposed API key, warrant a suspicious classification despite the lack of clear evidence of intentional malice.