Apple Podcasts Fetch
This skill should be used when the user asks to "download an Apple Podcast episode", "get podcast audio from Apple Podcasts", "fetch podcast MP3", "extract audio URL from Apple Podcasts link", provides an Apple Podcasts URL (podcasts.apple.com), or mentions downloading or extracting audio from Apple Podcasts. Provides the complete iTunes API + RSS feed workflow to resolve episode audio download URLs without a browser.
What this skill does
# Apple Podcasts Episode Audio Fetch
Fetch audio download URLs from Apple Podcasts episodes using only HTTP APIs. No browser, no scraping — just iTunes Lookup API and RSS feed parsing.
## Overview
Apple Podcasts does not expose direct audio URLs on its web pages. To obtain the audio file URL for a specific episode, follow a three-step API pipeline:
1. **Parse the Apple Podcasts URL** to extract `show_id` and `track_id`
2. **Call iTunes Lookup API** to get the podcast's RSS feed URL
3. **Call iTunes Episode Lookup** to get the `episodeGuid`, then **fetch the RSS feed** and match the guid to extract the audio `<enclosure>` URL
## Step 1: Parse the Apple Podcasts URL
Apple Podcasts episode URLs follow this structure:
```
https://podcasts.apple.com/{region}/podcast/{slug}/id{show_id}?i={track_id}
```
Example:
```
https://podcasts.apple.com/tw/podcast/ep640/id1500839292?i=1000752065662
^^^^^^^^^^ ^^^^^^^^^^^^^
show_id track_id
```
Extract two values:
- **`show_id`**: The numeric ID after `id` in the URL path (e.g., `1500839292`)
- **`track_id`**: The value of the `?i=` query parameter (e.g., `1000752065662`)
Both values are required. If the URL lacks `?i=`, prompt the user to provide a URL that includes the episode-specific `?i=` parameter, or use the iTunes Episode Lookup (Step 3a) to list recent episodes for the user to choose from.
## Step 2: Get RSS Feed URL via iTunes Lookup API
Make a GET request:
```
GET https://itunes.apple.com/lookup?id={show_id}
```
The response JSON contains a `results` array. The first result includes:
| Field | Description |
|-------|-------------|
| `feedUrl` | The podcast's RSS feed URL |
| `collectionName` | Podcast title |
| `trackCount` | Total episode count |
Extract the `feedUrl` value for Step 3.
**Example using curl:**
```bash
curl -s "https://itunes.apple.com/lookup?id=1500839292" | jq '.results[0].feedUrl'
```
## Step 3: Get Episode Audio URL
This step has two sub-steps: first get the `episodeGuid` from iTunes, then match it in the RSS feed.
### 3a: Get episodeGuid via iTunes Episode Lookup
Make a GET request:
```
GET https://itunes.apple.com/lookup?id={show_id}&entity=podcastEpisode&limit=200
```
The response `results` array contains the podcast info (index 0) followed by episode objects. Each episode includes:
| Field | Description |
|-------|-------------|
| `trackId` | iTunes track ID — match this against `track_id` from the URL |
| `episodeGuid` | The RSS `<guid>` value for this episode |
| `trackName` | Episode title |
| `episodeUrl` | Audio file URL (try this first; fall back to RSS if missing or broken) |
Find the episode where `trackId` equals the `track_id` from Step 1. Extract its `episodeGuid`.
**Example using curl + jq:**
```bash
curl -s "https://itunes.apple.com/lookup?id=1500839292&entity=podcastEpisode&limit=200" \
| jq '.results[] | select(.trackId == 1000752065662) | .episodeGuid'
```
### 3b: Fetch RSS Feed and Match guid
Fetch the RSS feed URL obtained in Step 2. Parse the XML to find the `<item>` whose `<guid>` matches the `episodeGuid` from Step 3a.
From the matching `<item>`, extract:
| XML Element | Data |
|-------------|------|
| `<title>` | Episode title |
| `<pubDate>` | Publication date |
| `<enclosure url="...">` | **Audio file download URL** |
| `<guid>` | Episode unique identifier |
**Example using curl + xmllint:**
```bash
FEED_URL="https://feeds.soundon.fm/podcasts/..."
GUID="360acf81-2bca-4f2f-b2b7-11647b8f10d4"
curl -s "$FEED_URL" | xmllint --xpath \
"//item[guid='$GUID']/enclosure/@url" - 2>/dev/null
```
Alternatively, use Python with `xml.etree.ElementTree` or a simple `grep`/`sed` approach on the raw XML, since RSS feeds are well-structured.
## Complete Workflow Summary
```
Apple Podcasts URL
│
├── Extract show_id (from path: id{show_id})
└── Extract track_id (from query: ?i={track_id})
│
▼
iTunes Lookup API: /lookup?id={show_id}
→ feedUrl (RSS feed URL)
│
▼
iTunes Episode Lookup: /lookup?id={show_id}&entity=podcastEpisode&limit=200
→ Match trackId == track_id
→ episodeGuid
│
▼
Fetch RSS Feed (feedUrl)
→ Match <guid> == episodeGuid
→ <enclosure url="..."> = audio download URL
```
## Limitations and Edge Cases
- **`limit` parameter**: iTunes Episode Lookup returns at most ~50 recent episodes. Older episodes may not appear. Increase `limit` up to `200` if needed, but very old episodes may still be unreachable via this API.
- **No direct episode lookup**: iTunes API does not support `/lookup?id={track_id}` for individual episodes — it returns empty results.
- **Missing `?i=` parameter**: Without the `track_id` query parameter, a specific episode cannot be identified. The URL must include `?i=`.
- **`episodeUrl` shortcut**: The iTunes Episode Lookup response includes an `episodeUrl` field that often contains the direct audio URL. Try this first as a shortcut before fetching the full RSS feed. Fall back to RSS if the URL is missing or returns an error.
- **Large RSS feeds**: Some podcasts have hundreds of episodes. The RSS feed may be several MB. Consider streaming or partial parsing for efficiency.
## Tool Selection
When executing this workflow in Claude Code:
- Use **WebFetch** to call the iTunes API endpoints and parse the JSON responses
- Use **Bash** with `curl` for RSS feed fetching (RSS/XML is too large for WebFetch in many cases)
- Use **Bash** with `xmllint`, `grep`, or Python for XML parsing of the RSS feed
Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.