Dwnldr
WarnAudited by ClawScan on May 10, 2026.
Overview
This downloader is mostly purpose-aligned, but it tells the agent to auto-download links and may use your Chrome browser cookies for restricted videos without clear approval or scope.
Only install this if you are comfortable with an agent downloading supported links automatically and sending media through Telegram or LocalSend. Do not allow the Chrome cookie fallback unless you explicitly want the agent to use your logged-in browser sessions, and understand that metadata stripping does not mean there are no records or traces.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A casually shared link could trigger a download, local file write, metadata rewrite, and message send without the user clearly asking for that action.
The skill explicitly tells the agent to treat the presence of many common social/video URLs as consent to download, even if the user's message may have another purpose.
**CRITICAL:** When the user sends a message that contains a URL from any of these domains, AUTOMATICALLY treat it as a download request. Do NOT ask "what do you want me to do with this?" — just download it.
Limit automatic behavior to explicit /dl invocation or ask for confirmation before downloading and sending files, especially outside a clear download request.
The agent could use local browser login cookies to access restricted content under the user's accounts without a clearly scoped permission prompt.
The yt-dlp option reads local Chrome browser cookies, which can use the user's authenticated sessions. The registry declares no primary credential, env vars, or config paths for this access.
| "Sign in to confirm" | Age-restricted — try with `--cookies-from-browser chrome` |
Require explicit user approval before using browser cookies, disclose this credential/session access in metadata, and preferably use a dedicated limited browser profile or cookie file.
Users may incorrectly believe the workflow leaves no records or evidence when it only attempts to remove metadata from the media file.
The wording overstates privacy. The later ffmpeg step strips media metadata, but downloads, local files, source-site requests, Telegram delivery, and logs may still leave records.
metadata scrubbed clean. No traces, no evidence, just pure content booty delivered straight to yer Telegram.
Replace “No traces, no evidence” with a precise disclosure that only embedded media metadata is removed and that providers or local systems may retain logs.
Downloaded media may be uploaded or transmitted through Telegram, and large files may be sent to a LocalSend device.
Sending the downloaded file back through Telegram is disclosed and aligned with the skill's purpose, but it moves the file through an external messaging channel.
openclaw message send \ --channel telegram \ --target <user_id> \ --message "🎬 Downloaded: <title>" \ --media /home/rami/.openclaw/workspace/_incoming/<filename>
Confirm the intended recipient or device before sending, and avoid using this for files the user does not want shared through those channels.
The skill may fail or behave differently depending on undeclared local tools and versions.
The declared requirements list yt-dlp and ffmpeg, but the instructions also rely on nodejs behavior and localsend-cli without declaring those binaries in the requirements.
yt-dlp --js-runtimes nodejs ... localsend-cli send --to "<user_device>" /home/rami/.openclaw/workspace/_incoming/<filename>
Declare all required helper binaries and clarify optional tools such as LocalSend and nodejs.