download
Skill1 starsChanged 3 months agoMITView on GitHub
Download video and audio from URLs using yt-dlp. Use when you need to fetch media from YouTube, Vimeo, or other supported sites before local processing with inspect, audio, or video-transformation skills.
- Installs packages
2 other projects use a version of this.
Adopted by
Most recently taken up by
- jantichy/claudetheir own version, first seen Nov 1, 2026
- jxxsteven7/zotero-librariantheir own version, first seen Oct 11, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- jantichy/claude★ 52same name
- jxxsteven7/zotero-librarian★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- site/AGENTS.mdAGENTS.md
- site/CLAUDE.mdCLAUDE.md
- audioSkill
- captions-complianceSkill
- forced-narrative-exactSkill
- imageSkill
- inspectSkill
- install-media-toolsSkill
- program-masterSkill
- shotsSkill
- speech-captionsSkill
- subtitlesSkill
- timecodeSkill
- video-transformationSkill
- vision-analysisSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 42
If your tools showed a filesystem path when loading this SKILL.md, strip SKILL.md and use that folder.
- Very specific: line 43
If you already ran another mediaskills script (for example .../audio/scripts/extract.py), this skill is a sibling of that folder: same …
- Very specific: line 66
Prefer absolute paths for --input / --output when cwd is uncertain.
- Distinctive: line 71
Before running any script, treat these two failures differently:
- Very specific: line 74
Only escalate sandbox permissions if the error is explicitly a permission denial (e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Download
Fetch remote media with yt-dlp. Use this skill when you have a URL and need a local file for downstream processing.
When to use
- This skill — download from YouTube, Vimeo, Twitter/X, and hundreds of other sites supported by yt-dlp.
inspect— after download, probe the file for duration, codecs, and resolution.audio/video-transformation— trim, transcode, or extract audio from downloaded files.
Gotchas
- Network required — downloads fail offline or behind restrictive firewalls. Corporate proxies may need
HTTP_PROXY/HTTPS_PROXYenv vars. - Rate limits and bot checks — some sites block datacenter IPs or require cookies. Pass cookies via yt-dlp config (
~/.config/yt-dlp/config) if downloads fail with 403/429. - Output location — files land in the workspace root
.mediaskills/downloads/(not inside this skill folder), or$MEDIASKILLS_DATA_DIR/downloads/when set. Filename pattern:Title [video_id].ext. - Playlists — this script downloads the URL as given; playlist URLs may fetch multiple files. Prefer single-video URLs for predictable output.
- Live streams — live content may produce partial files if recording is interrupted.
- Legal / ToS — only download content you have rights to access. Respect platform terms and copyright.
Running scripts
This skill's scripts live in scripts/ alongside this file. Before running any script, resolve its absolute path from this skill's own directory — do not assume the shell cwd is the skill folder, the repo root, or the workspace. Stay in the workspace (so media paths resolve) and pass the absolute script path to uv run:
uv run <skill_directory>/scripts/url.py --url '<https-url>'<skill_directory> is a placeholder. Never pass those angle brackets to the shell — the command will fail. Replace it with a real absolute directory before invoking uv run.
How to get that directory (do this yourself; do not ask the user first; do not skip the skill):
- If your tools showed a filesystem path when loading this
SKILL.md, stripSKILL.mdand use that folder. - If you already ran another mediaskills script (for example
.../audio/scripts/extract.py), this skill is a sibling of that folder: same parent, directory namedownload. - Otherwise search standard install locations and confirm the script exists:
NAME=download
for d in \
"$HOME/.agents/skills/$NAME" \
"$HOME/.cursor/skills/$NAME" \
"$HOME/.codex/skills/$NAME" \
"$HOME/.claude/skills/$NAME" \
"$PWD/.agents/skills/$NAME" \
"$PWD/.cursor/skills/$NAME" \
"$PWD/skills/$NAME"
do
if [ -f "$d/SKILL.md" ] && [ -e "$d/scripts/url.py" ]; then
SKILL_DIR=$(cd "$d" && pwd)
break
fi
done
[ -n "$SKILL_DIR" ] || { echo "mediaskills: $NAME not found" >&2; exit 1; }
uv run "$SKILL_DIR/scripts/url.py" --url "<https-url>"Prefer absolute paths for --input / --output when cwd is uncertain.
Missing binaries vs permissions
Before running any script, treat these two failures differently:
- If a required binary (
uv,yt-dlp) reportsNo such file or directoryorcommand not found: this is a missing or unreachable binary, not a permissions issue. Escalating sandbox permissions will not fix it. Runcommand -v uvandcommand -v yt-dlpto see whether they resolve at all. If not, install or re-link them (install-media-toolsdoctor/install) rather than retrying with wider permissions. - Only escalate sandbox permissions if the error is explicitly a permission denial (e.g.
Operation not permitted,Permission denied).
Recipes
Download a video
uv run <skill_directory>/scripts/url.py --url 'https://www.youtube.com/watch?v=dQw4w9WgXcQ'Example result:
{"ok": true, "op": "download.url", "data": {"url": "...", "output_path": "/path/.mediaskills/downloads/Title [id].mp4", "output_dir": "/path/.mediaskills/downloads"}, "output_paths": ["..."]}Custom data directory (CI or server)
export MEDIASKILLS_DATA_DIR=/var/mediaskills
uv run <skill_directory>/scripts/url.py --url 'https://example.com/clip.mp4'Downloads go to /var/mediaskills/downloads/.
Chain with inspect
uv run <skill_directory>/scripts/url.py --url 'https://...' | jq -r '.output_paths[0]' | xargs -I{} uv run <inspect_skill_directory>/scripts/probe.py --input {}Troubleshooting
| Error / symptom | Likely cause | Action |
yt-dlp not found | Binary missing | brew install yt-dlp or pip install yt-dlp |
HTTP Error 403 | Geo-block or auth required | Update yt-dlp (yt-dlp -U); try browser cookies |
Video unavailable | Removed or private | Verify URL in a browser while logged in |
| Output file not found | Print hook failed | Check output_dir for newest file; retry with verbose yt-dlp |
| Slow download | Large file or throttling | Normal; progress JSON emitted on stderr |
Available scripts
| Script | Purpose |
scripts/url.py | Download media from a URL |
Acceptance checks (agent must pass before delivery)
- Contract: exit 0,
ok: true, everyoutput_pathsentry exists and is non-empty. - Probe: immediately
inspect.describe/probethe download — duration and codecs present. - Spot-check: file size > 0; URL matches requested source; no truncated download errors in stderr.
- On failure: retry or escalate; do not chain transforms on a failed/partial download.
Do not use for
- Local file processing without a URL
- DRM-protected streams you cannot access with yt-dlp
Related skills
inspect— probe downloaded filesinstall-media-tools— install ffmpeg/ffprobe for post-download workaudio,video-transformation— process downloaded media
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

