← Files NewsTune StudioARCHIVED FILE

SKILL.md

4.68 KB · Sep 30, 2026 · 23:02 UTC

↓ Download file

---
name: newstune-podcast-publisher
description: "Use when a user asks to publish NewsTune content, preserve/enable/disable RSS, get a feed URL, prepare a show for Spotify/Apple Podcasts/YouTube, review exactly which episodes will become public, or complete a pre-authorized scheduled release. Uses OAuth tools and exact-scope previews."
---

# NewsTune Podcast Publisher

Treat NewsTune publishing and third-party directory submission as separate stages. Use only the OAuth-connected plugin tools; never request an API key or call private endpoints directly.

Typical triggers include “publish these episodes,” “enable my RSS feed,” and “prepare this show for Spotify.”

## Preflight

1. Discover the exact series by paging through `list_podcast_series`; never publish from a title guess.
2. Use `get_podcast_series` to show the series ID/title, existing public state, public slug, RSS state, and relevant episodes.
3. Ask which audio-ready episode numbers should be public. Do not silently select every episode.
4. Ask for one explicit RSS action: `preserve` (safe default), `enable`, or `disable`. Only when enabling or updating RSS, confirm the requested language, author, category, and explicit-content value. Do not solicit or expose an owner email through the plugin.
5. Read [references/distribution.md](references/distribution.md) before guiding an external directory submission.

## Exact-scope publishing

Call `publish_podcast_series` without confirmation first. The preview is authoritative. Show the user:

- series ID, title, and final public slug;
- selected episode numbers and titles;
- already-public episodes that will remain public;
- the full public episode scope after the action;
- `futurePublicEpisodeNumbersAfterAction` and every titled/status-bearing item in `futurePublicEpisodesAfterAction`; explain that these episodes are still generating and not readable now, but may become public automatically when generation finishes;
- current and resulting RSS state;
- any masked owner contact that NewsTune reports will become public in RSS; and
- that public pages—and an enabled RSS feed—are visible on the open web.

Send `rssAction: "preserve"` unless the user explicitly asked to enable or disable RSS. Do not translate an omitted preference into `disable`; preserving the current state prevents an unrelated publish action from taking down an existing feed.

For interactive work, wait for explicit approval of both the immediate public scope and the future-public scope in that exact preview. If `futurePublicEpisodesAfterAction` is non-empty, enumerate those episodes and obtain an explicit acknowledgement that each may become public after generation without another publish action. Execute with identical inputs, the returned confirmation token and idempotency key, and `confirmed: true`. If NewsTune reports stale state, preview again and request fresh approval. Never work around a stale preview by publishing episodes one at a time.

### Scheduled release exception

When the current call is a headless occurrence of a user-approved recurring automation, do not request another approval. Preview, then execute automatically with `confirmed: true` only when the preview selects exactly the newly generated episode, leaves every other public episode unchanged, uses the already-approved series slug/SEO, and preserves the approved RSS state. The schedule-setup confirmation is the authorization basis for that exact recurring effect.

If the preview adds another episode, changes RSS enablement/metadata, changes slug/SEO, exposes a new owner contact, exceeds the contract, or otherwise differs from the stored schedule prompt, do not publish and do not ask during the headless run. Pause/skip and report the mismatch so the user can approve a revised schedule later.

After success, return the public series/episode links and the absolute feed URL when RSS is enabled. State precisely what was published.

## External distribution

NewsTune prepares public pages and an RSS feed. Spotify for Creators, Apple Podcasts Connect, and YouTube Studio require the account owner to sign in, verify ownership, review platform-specific choices, and accept legal terms. You may open or explain the official flow, but do not claim submission or acceptance unless the user completed it and the platform confirmed it.

## Safety

- Never expose private or non-audio-ready episodes.
- Never change a previously assigned public slug silently.
- Never publish beyond the previewed immediate or future-public scope, and never omit still-generating public-designated episodes from the approval summary.
- Never say “published to Spotify/Apple/YouTube” when only NewsTune RSS is enabled.
- Never accept directory terms or ownership declarations for the user.

SHA-256: b7a83545552eecbc552ea8e9de6474f80dd0c5c44cfdf8a3291930bb4bbfa128