ericrisco/rsc-harness / skills/podcast
podcast
VerifiedUse when planning, recording, editing or publishing one podcast episode end to end — the run-of-show and guest brief, recording settings, the loudness master, the Podcasting 2.0 sidecars for chapters and transcripts, the RSS item, and timestamped SEO show notes. Covers audio that is quiet on one platform and loud on another, feeds rejected for bad artwork, and chapters that will not appear in the app. NOT clipping the episode into social posts (that is `social-publisher`), NOT cutting the vertical short (that is `video-shorts`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.7 KB |
| evals/README.md | markdown | 1.3 KB |
| evals/cases.yaml | config | 4.1 KB |
| references/rss-and-namespace.md | markdown | 6.0 KB |
| scripts/verify.shexecutable | script | 8.8 KB |
evals/README.md
View on GitHub# Evals — podcast
These cases are routing + capability checks for a human or an LLM judge; there is no
automated test runner beyond `scripts/verify.sh` (which lints emitted artifacts — a
`chapters.json`, an RSS feed/`<item>`, or a `transcript.vtt` — not these prompts). To
run them: read `cases.yaml` and confirm the skill's `description` would fire on every
`should_trigger` prompt (including the jargon-only "chapters.json + double-ender + -16
master" case that never says "podcast" and the Catalan "masteritzar l'àudio" phrasing),
that each `should_not_trigger` prompt routes to the named sibling instead
(`video-shorts`, `social-publisher`, `brand-voice`, `newsletter`, `content-engine`), and
that an end-to-end answer to the `capability` scenario satisfies every line of its
`must_include` rubric — the -16 LUFS / -1 dBTP master-once rule with Spotify's -14
normalization, 48 kHz WAV master + MP3 enclosure, a monotonic `chapters.json` wired via
`podcast:chapters`, a `podcast:transcript` carrying a `type`, an `<item>` with the
required enclosure/guid/duration/artwork fields, blog-shaped timestamped show notes, and
the one-episode-first + 72h-Apple submission note. To check an actual emitted artifact,
point `scripts/verify.sh` at the file or directory it produced.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |