- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add win4r/MuseAI-Skills --skill generate_podcast -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add win4r/MuseAI-Skills --skill generate_podcast -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add win4r/MuseAI-Skills --skill generate_podcast -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add win4r/MuseAI-Skills --skill generate_podcast -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/win4r/MuseAI-Skills/tree/HEAD/opt/hatch/skills/generate_podcastDe l'éditeur
Generate audio content — podcasts, audio briefings, narrated summaries, or any spoken audio. Use this skill for all generated audio, not just podcasts. The podcast-helper script handles synthesis, catalog management, cover art generation, and publishing.
MAI_01 and MAI_03 catalog ids: Warm and Smooth); they are the recommended, production-quality set and the right pick most of the time. Default to Warm (avocado_v2:MAI_01) and Smooth (avocado_v2:MAI_03). When the topic, tone, or user request steers toward a different catalog voice — an accent, a character fit, or more distinct speakers — it's perfectly fine to pick it from the catalog. The full voice catalog is at /opt/hatch/skills/voice-selector/voice_source.json — pick by the entry's display name and pass its id (colon form like avocado_v2:MAI_01 is fine). Any number of speakers is supported. ("MAI" is the internal id prefix only — say "Meta AI voices" or display names to the user, never "MAI".)~/MEMORY.md (e.g. "podcast host Alex = avocado_v2:MAI_01") and, before naming a new host, check there for a name you've already used for that voice. Reuse the same name whenever you use that voice again, so a given voice is always the same character to the user. For a recurring series, reuse the same host names and the same voice assignments in every episode so it sounds like the same show — pin them in the cron task body (see Scheduling).podcast-helper manifest read and look at each recent episode's topics field (a short summary of what that episode already covered). Steer the new episode toward fresh material or a genuinely new angle rather than re-covering ground. This matters most for a recurring series.Write the full dialogue. Label each turn with the speaker name followed by a colon:
Alex: Welcome to the podcast. Today we're diving into async Rust.
Jordan: Great topic. Let's start with why async matters.
Alex: The big advantage is zero-cost abstractions...
Write the script to a file (e.g. /tmp/script.txt).
The script goes directly to a TTS model — write it in spoken form. The text will be read aloud exactly as written. Follow these guidelines:
(pause), sound effects, markup, emoji, citation numbers like [1], math symbols, or visual separators like ---Write complete, conversational sentences — not headlines. Every line a host speaks should be a full grammatical sentence with a subject and a verb, the way people actually talk out loud. Avoid telegraphic, verbless fragments and stat-ticker read-outs; this is a conversation, not a wire report or a scoreboard. An occasional short line for emphasis ("Unbelievable.") is fine, but never string clipped fragments together.
Second assist of the night for Messi. Two one Argentina. Full time. Heartbreak for England.That's Messi's second assist of the night, and it puts Argentina up two to one. When the whistle went, it was heartbreak for England.When you present a stat or a scoreline, fold it into a spoken sentence ("England had just forty-four percent of the ball") rather than dropping it in as a bare fragment ("England, forty-four percent possession").
Write a topics summary for dedup. Before generating, write a short bulleted summary of the major topics and key points this episode covered to a file (e.g. /tmp/topics.md) and pass it with --topics-file. Keep it concise — a handful of bullets naming the subjects and any specific stories, guests, or angles, not a full transcript. It is persisted alongside the episode and read by future generations (via the topics field in manifest read) to avoid repeating material. Example:
- Async Rust fundamentals: futures, executors, zero-cost abstractions
- Tokio vs async-std tradeoffs
- Common pitfalls: blocking in async contexts, .await forgetting
Default: generate only, do not publish. Only add --publish when the user explicitly asked to publish or when the podcast catalog already has an RSS feed — a "feed" object with a non-empty feed_url (meaning they've published to a feed before and want new episodes added). A "feed" object that has only a spotify_show_url (from a personal Save to Spotify) is not an RSS feed and must not trigger --publish; publishing is public and requires explicit consent.
Always pass --cover-prompt with a short description of the episode's theme so podcast-helper can generate cover art automatically.
Do not pass --cover-image. Publishing accepts only generated cover art or the bundled default, so an episode published with --cover-image fails. Use --cover-prompt instead; if the user hands you an image file, generate a cover from a prompt describing it and say you did. The flag still parses and will be reconnected later — it just cannot reach the feed today.
Language: unless the user asks for another language, write the title, description, feed copy, and script in the language of the current conversation. podcast-helper defaults synthesis to the request's JARVIS_PRESENTATION_LOCALE; pass --language only to honor an explicit user choice (e.g. --language es, --language pt, or a locale like pt_BR). Quality varies significantly across languages — English is highest quality; other languages can be rough (mispronunciations, accent), and some voices handle a given language better than others (try a different --speaker voice from voice_source.json if one sounds wrong). Tell the user non-English audio may be imperfect. See the tts skill's Language section for details.
One-off episode:
podcast-helper generate \
--script /tmp/script.txt \
--title "Deep Dive into Async Rust" \
--description "Alex and Jordan explore async patterns in Rust" \
--speaker Alex=avocado_v2:MAI_03 \
--speaker Jordan=avocado_v2:MAI_01 \
--cover-prompt "async Rust programming, gears and lightning bolts" \
--topics-file /tmp/topics.md
Cron/recurring episode — pass --series-id matching the cron job ID so episodes in the same series share cover art:
podcast-helper generate \
--script /tmp/script.txt \
--title "Morning News - June 2, 2026" \
--description "Today's top stories" \
--speaker Alex=avocado_v2:MAI_03 \
--speaker Jordan=avocado_v2:MAI_01 \
--series-id daily-news \
--cover-prompt "morning news briefing, sunrise and newspaper" \
--topics-file /tmp/topics.md
With --series-id, cover art is generated once for the first episode and reused for all subsequent episodes in the series.
If the user asked to publish, or the podcast catalog already has an RSS feed — run podcast-helper manifest read and check for a "feed" object with a non-empty feed_url (a feed with only spotify_show_url does not count):
podcast-helper generate \
--script /tmp/script.txt \
--title "Deep Dive into Async Rust" \
--description "Alex and Jordan explore async patterns in Rust" \
--speaker Alex=avocado_v2:MAI_03 \
--speaker Jordan=avocado_v2:MAI_01 \
--cover-prompt "async Rust programming" \
--topics-file /tmp/topics.md \
--publish --feed-title "Daily with Alex"
Returns JSON with path, duration_secs, slug, cover, and (if published) feed_url, episode_url, and subscription_links.
Always present the title as plain text above the playable link:
{title}
[{title}](sandbox://workspace/podcasts/{slug}/{slug}.mp3)
The first time you mention publishing, a personal feed, or subscription in a conversation, briefly explain what the feed is: a personal RSS podcast feed they can add to a podcast app, and future published episodes will show up there automatically. After that first explanation, use shorter wording.
If the episode was published, mention it was published and that it will appear in their feed. Note that published episodes are public.
After delivering, present applicable follow-ups:
podcast-helper publish \
--slug {slug} \
--feed-title "Daily with Alex" \
--feed-description "Daily news and tech updates"
Returns JSON with feed_url, episode_url, and subscription_links.
Public publishing is content-reviewed. If the output has "blocked": true, the episode was not published: the audio and catalog entry still exist locally, but it cannot go to the public feed. Relay the returned error message to the user plainly and stop — do not retry, reword the script to get around it, or fall back to another publish path. Saving to the user's own Spotify show is unaffected by this review.
Publishing unifies artwork across the show it publishes to — individual episode and series covers for that feed's episodes are replaced with its cover in the podcast catalog. Another feed's episodes keep their own artwork.
After publishing, always re-present the listen link and confirm publication:
{title}
[{title}](sandbox://workspace/podcasts/{slug}/{slug}.mp3)
Published to your personal feed, which is the RSS feed you can subscribe to in your podcast app so future published episodes show up there automatically.
Published episodes are public — anyone with the feed link can listen.
On the first episode published to a feed, present subscription links from the output JSON:
Subscribe to your personal feed:
RSS feed URL (copy and paste into any podcast player):
`{subscription_links.rss}`
Or open directly in a podcast app:
- [Open in Apple Podcasts]({subscription_links.apple_podcasts})
- [Open in Overcast]({subscription_links.overcast})
- [Open in Pocket Casts]({subscription_links.pocket_casts})
This is the RSS feed for your generated episodes, and once you add it to a podcast app, future published episodes will appear there automatically.
Important — how to render the feed URL: The RSS feed URL is for the user to copy and paste, never to click. Always present any published https:// URL (feed URL, episode link) wrapped in backticks as code — either inline `https://…` or inside a fenced code block. Never emit it as a bare URL (a bare https://… auto-linkifies on native clients) and never as a [label](https://…) markdown link; either form may fail to open on native clients and invites a click instead of a copy. Do not offer direct episode download links. The only clickable links should be local sandbox:// listen links and the podcast-app protocol links (podcast://, overcast://, pktc://).
On subsequent episodes to the same feed, skip — the user is already subscribed.
Always use a single feed unless the user explicitly asks for a separate one. Before publishing, run podcast-helper manifest read. feeds lists every feed on this VM and feed is whichever was published to most recently; if either has a non-empty feed_url, reuse that feed's feed_title exactly.
When the user does keep more than one show, the title is what picks the feed: publishing with a --feed-title that matches an existing feed adds to it, and any other title creates a new one. So reuse a title character for character when adding to a show, and never reuse one for a different show.
On the first publish (no feed_url in the podcast catalog yet — a feed object that only carries a spotify_show_url still counts as no RSS feed), choose a personal feed title based on the user's Muse name — e.g. "Today with Alex", "News with Alex".
When the user explicitly asks to put a generated episode on their Spotify, use
podcast-helper save-to-spotify to add it to the user's own Spotify account. This is a personal
save to the user's own Spotify library/show — it is NOT the public/subscribable RSS feed publishing
described above, and does not use podcast-helper --publish. Only do this on an explicit request; do
not offer it proactively.
Run the upload through podcast-helper (not the raw save-to-spotify CLI): the helper uploads via the
bundled save-to-spotify CLI and records the resulting Spotify show link into the podcast catalog so
it shows up on the library podcasts page. See references/save-to-spotify.md for the underlying CLI,
the connect flow, and rules.
save-to-spotify --json shows — it lists existing shows and
confirms Spotify is connected. If it fails with a token / "not connected" error, tell the user to
connect Spotify in Settings → Connections → Spotify (the shared Spotify connection), then retry.
This tool has no auth subcommands or connect link. Ask the user whether to reuse an existing show
or create a new one; don't silently pick.podcast-helper (confirm title, target show, and summary with the user
first — this writes to their account). The helper reads the audio/title/cover from the podcast catalog by
slug; pass a cover only to override (must be JPEG/PNG ≤ 1 MB — convert .webp/other formats first):
podcast-helper save-to-spotify \
--slug {slug} \
[--show-id <id> | --new-show "<show title>"] \
[--title "{title}"] [--summary "{description}"] [--image {cover}]
Returns JSON with episode_id, episode_uri, spotify_show_id, and spotify_show_url.save-to-spotify --json episodes status <episode-id> --wait (use the
episode_id from step 2). Processing is server-side and takes a few minutes; a returned
episode_uri means it was accepted. If it stalls in NOT_READY (Spotify occasionally 503s), it's a
Spotify-side delay — tell the user it's processing and retry later rather than polling indefinitely.spotify:show: / spotify:episode: URIs are internal CLI handles: use them for
subsequent commands, but never include them in a user-facing response.For deletion, use the raw save-to-spotify CLI, not podcast-helper, spotify-api,
podcasters.spotify.com, or creators.spotify.com. Start with save-to-spotify --json shows, resolve
the requested show by title, and inspect it with shows get <show-id>. Use
episodes --show-id <show-id> followed by episodes delete <episode-id> to remove one episode. To
remove the entire show, confirm that all its episodes will be deleted and run shows delete <show-id>;
that command removes the episodes too. Treat {"status":"deleted"} as accepted, then poll the relevant
shows or episodes --show-id inventory for up to 60 seconds. Confirm deletion only after the item is
absent; otherwise tell the user Spotify is still propagating the accepted deletion and do not repeat it.
Deleting the Spotify copy does not delete local audio or an RSS feed. See
references/save-to-spotify.md for the full command flow.
Cover art is handled automatically by podcast-helper during generation. You control it with two flags:
--cover-prompt — a short description of the episode theme (e.g. "morning news briefing, sunrise and cityscape"). podcast-helper shells out to media-generation to create a square icon-style image. Always provide this.--series-id — groups episodes that share the same cover art. Use the cron job ID for recurring episodes. Without this, each episode gets unique art.How artwork flows:
Fallback when no --cover-prompt is provided: the bundled default cover
(/opt/hatch/skills/generate_podcast/default-cover.jpg). The user's avatar is
also tried first, but an avatar cover cannot currently be published — one more
reason to always pass --cover-prompt on an episode headed for a feed.
You do NOT need to call media.generate_image yourself for cover art — podcast-helper handles it internally.
--cover-image is not available right now: publishing takes only generated cover art or the bundled default. The flag is still accepted so it can be reconnected later, but an episode published with it fails, so do not use it.
When a user asks for a recurring podcast, audio briefing, or scheduled audio content:
For recurring podcasts, create a cron job using the cron tool. Always set timeout_secs: 1800.
Example cron tool call:
{
"action": "add",
"file_name": "daily-podcast__daily@13:00:00.md",
"id": "daily-podcast",
"enabled": true,
"mode": "task",
"timeout_secs": 1800,
"schedule": {
"kind": "daily",
"timezone": "UTC",
"time": "13:00:00"
},
"body": "Generate a new podcast episode on <topic>. Follow the generate_podcast skill workflow. Keep the same cast every episode: hosts Alex (--speaker Alex=avocado_v2:MAI_01) and Jordan (--speaker Jordan=avocado_v2:MAI_03). Use --series-id daily-podcast and --cover-prompt '<topic description>' when calling podcast-helper generate. Before choosing today's angle, run podcast-helper manifest read and review each recent episode's topics field to avoid repeating what was already covered. Write a short topics summary to /tmp/topics.md and pass it with --topics-file so future episodes can dedup against it. Publish to the feed after generating."
}
Keep cron task descriptions concrete — include the topic angle, the fixed cast (host names and their voice ids, so every episode uses the same hosts and voices), --series-id matching the cron ID, and explicit instructions to research live results at generation time.
For edge cases and manual operations, podcast-helper exposes sub-commands:
podcast-helper manifest read — print the current podcast catalogpodcast-helper manifest add-episode --slug ... --title ... --duration-secs ... --path ... --chunk-count ... — add episodepodcast-helper manifest update-episode --slug ... [--episode-url ...] [--feed-url ...] — update episodepodcast-helper generate-slug --title "..." — generate a kebab-case slug with today's dateIf the user asks to listen to a podcast, hear their podcast, or asks about their episodes, read the podcast catalog with podcast-helper manifest read and present listen links for the relevant episodes:
[{title}](sandbox://workspace/podcasts/{slug}/{slug}.mp3)
If the feed is published, also include the subscription links (see section 6 format).
/opt/hatch/skills/voice-selector/voice_source.json, referenced by their catalog id. Default to the Meta AI voices (catalog ids MAI_01 and MAI_03) most of the time, but pick another catalog voice when the topic, tone, or user request steers that way. Never say "MAI" to the user — call them the Meta AI voices or use display names.tts synthesize-script stops — do not deliver a partial episode. Most failures are transient backend issues: retry the same generation later on a bounded backoff (~5m, ~10m, ~30m, ~1h), keeping the same speaker voices. Never swap in a different voice or a different TTS engine to work around a failure. Schedule the retry (a delayed wakeup or short cron) rather than blocking, and tell the user you'll deliver the episode once synthesis recovers. If it still fails after the ~1h retry, stop — cancel the scheduled retry, report the error, and suggest they try again later. (A ... not allowed to use voiceID ... error won't clear on retry — that voice id isn't permitted for this client; pick another from voice_source.json and regenerate. Auth or clear request errors likewise need a fix, not a retry.)https:// feed or episode URL as a bare or clickable link — always as copyable code (wrapped in backticks). Only sandbox:// listen links and podcast-app protocol links (podcast://, overcast://, pktc://) may be clickable.Compose and deliver audio content: a podcast episode, briefing, or narrated summary, with one or more voices, as an MP3. For reading supplied text aloud verbatim, use tts.
---name: generate_podcastdescription: Compose and deliver audio content: a podcast episode, briefing, or narrated summary, with one or more voices…---# opt/hatch/skills/generate_podcast/SKILL.mdFAQ
Téléchargez opt/hatch/skills/generate_podcast/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/win4r/MuseAI-Skills.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.