Download Anything
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a coherent download-helper skill, but it includes unsafe automation guidance and automatic browser-cookie use that should be reviewed before installation.
Install only if you are comfortable with command-line download tools changing your environment. Run setup manually, avoid the unsafe aria2 RPC example unless locked down, approve any browser-cookie use explicitly, and verify downloads from trusted and authorized sources before opening or installing them.
Findings (3)
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.
If a user follows this example as written, other local or network actors may be able to control downloads or cause files to be written under the user's account.
The documentation presents an agent automation pattern for a JSON-RPC download daemon that can listen beyond localhost and allow all origins, without showing an RPC secret or other access control.
aria2c --daemon --enable-rpc --rpc-listen-port=6800 ... aria2c --enable-rpc --rpc-listen-all=true --rpc-allow-origin-all=true
Do not run the listen-all/allow-origin-all RPC example as-is. Bind RPC to localhost, set an RPC secret, restrict CORS/firewall access, and stop the daemon when finished.
Downloads may run using the user's logged-in browser session, including access to account-gated content, without a separate confirmation at the moment cookies are used.
For Bilibili URLs, the script automatically reads browser session cookies from Chrome, Firefox, or Edge and reuses them for the download. That is delegated account/session access.
if [[ "$URL" =~ bilibili\.com|b23\.tv ]]; then ... yt-dlp --cookies-from-browser "$browser" -j "$URL" ... EXTRA_ARGS+=(--cookies-from-browser "$browser")
Require explicit user approval before using browser cookies, document exactly which browser/account is used, and prefer scoped exported cookie files when possible.
Installing the toolkit changes the local environment and depends on the trustworthiness of package-manager sources at install time.
The installer uses package managers to install unpinned global/system tools. This is expected for a download toolkit, but package versions and provenance are not locked by the skill.
pip3 install "$pkg" ... npm install -g "$pkg" ... sudo apt-get install -y aria2 wget ffmpeg jq 2>/dev/null || true
Run the installer only when you trust the package sources, review what will be installed, and consider installing tools manually or pinning versions in controlled environments.