NewsTune Studio

View saved version →

---
name: newstune-agent-api
description: "Use when a user asks to inspect, find, create, continue, or schedule a NewsTune podcast; turn project progress or source material into an episode; monitor generation; make ChatGPT/Codex an ongoing podcast production partner; or replies to a pending NewsTune charge preview with a bare approval such as 'I approve', 'yes', or '同意扣除 20 credits'. Uses OAuth-connected tools, one exact approval for a private multi-episode batch, sequential durable generation, and direct episode-page links."
---

# NewsTune Studio

Use only the OAuth-connected NewsTune tools bundled with this plugin. Never ask the user for a NewsTune API key, Auth0 token, cookie, password, or raw credential, and never call private HTTP endpoints directly.

Typical triggers include “show my existing podcasts,” “continue this series,” “turn this project update into an episode,” “make my computer a podcast production partner,” and a short approval that continues an immediately preceding NewsTune preview, such as “同意扣除 20 credits.”

## Production frame

Treat NewsTune as an ongoing podcast production system, not only a one-time audio renderer. It can discover a user's existing shows, create private episodes from source material or an approved script, track generation, choose accessible voices, and publish an exact approved scope.

The host AI may also collect project-progress inputs from connected tools or local files and run recurring automations. A schedule belongs to the host AI unless a NewsTune scheduling tool is explicitly available. Confirm the full recurring execution contract once when the schedule is created or materially changed; covered runs then generate, upload, poll, and publish automatically without another user turn.

## Workflow

1. Use `get_account_overview` to verify the connection, plan features, credit balance, and server-owned prices.
2. Clarify the topic, audience, language, use case, desired format, source policy, voice preference, and whether this is a one-off or ongoing series. Ask only for missing decisions.
3. Use `list_podcast_series` before creating a series. Follow `nextOffset` until it is `null` when identifying all possible matches.
4. Prefer an existing series when the user says “my podcast,” “continue,” “add an episode,” or supplies a matching title. Use `get_podcast_series` to confirm its ID, hosts, format, visibility, persistent `customPrompts`, and recent episodes.
5. For source material:
   - Summarize local/private sources in the host AI and use `script_to_audio` when the user does not want raw content sent to NewsTune.
   - Use `material_to_podcast` only for material the user agrees may be sent to NewsTune and, when relevant, researched on the open web.
   - Never upload secrets, credentials, unrelated private files, or an entire local project by default.
6. Reuse hosts and persistent `customPrompts` already approved in this conversation. Combine missing host, source, settings, and credit choices into one confirmation; do not request separate host or prompt approvals. Call `preview_podcast_series_creation` with the complete final payload, show its exact charge, retain its opaque `previewId` internally, and use `confirm_podcast_series_creation` under that unchanged approval without asking again. New plugin-created series and episodes are always private. Do not choose the compatibility-only `create_podcast_series` tool for this workflow.
7. After an episode is queued, poll `get_generation_status` until `succeeded` or `failed`. When it succeeds, treat transcript media as part of the episode refresh: call `get_episode_transcript_context`, re-evaluate existing user-provided and sourced web assets against the new canonical segments, validate/import or prepare/finalize only the assets that are actually needed, and call `replace_episode_media_cues` with the returned `revisionId`. Do not generate new images, video, or attachment audio. If sourcing or validation fails, do not replace the active cue

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.

View saved version →

---
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 a

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.

View saved version →

---
name: newstune-voice-studio
description: "Use when a user asks to browse or preview NewsTune podcast voices, choose one or two host voices, clone a voice through NewsTune's consent flow, or open NewsTune setup for a missing voice binding. Uses OAuth tools and keeps recording, consent, and uploads inside a secure NewsTune handoff."
---

# NewsTune Voice Studio

Use `list_podcast_voices` and `prepare_voice_action` for voice work. You may also use paginated `list_podcast_series` and `get_podcast_series` only to resolve and verify a user-named owned series before creating its handoff. The plugin is OAuth-connected; never request an API key, browser token, password, raw recording, or voice sample in ChatGPT or Codex.

Typical triggers include “help me choose a podcast voice,” “preview my voices,” and “clone my voice for this show.”

## Workflow

1. Clarify language, accent, host role, tone, pace, and solo or multi-host format.
2. Call `list_podcast_voices`. Prefer an already accessible voice with a `previewUrl`; sharing that preview does not render new audio or spend credits.
3. If the user names a series, follow `list_podcast_series.nextOffset` until the unique match is found and use `get_podcast_series` when verification is needed. Then call `prepare_voice_action` with `select_voice`, `selectionCount: 1` for solo or `selectionCount: 2` for two-host format, and that discovered `seriesId`; never invent an ID from its title. If no series is named, omit `seriesId`.
4. Selecting an already accessible public/community voice is not voice cloning. Even when a voice is named after a celebrity or public figure, allow the user to preview and select it. Give a short reminder to avoid misleading endorsement, deceptive impersonation, or other unlawful use; do not block selection solely because of the identity or name.
5. For cloning, ask the user to confirm that they understand they are responsible for having the appropriate rights or permission. Call the matching clone action only after that acknowledgement, then let NewsTune handle recording/upload and consent in the handoff.
6. Explain that recording, upload, consent review, and any supported selection or binding happen inside NewsTune. The handoff only opens that flow; it neither performs nor proves that cloning, selection, or binding completed.

Read [references/voice-workflows.md](references/voice-workflows.md) for the decision boundaries.

## Refuse or stop when

- The user states an intent to deceive, defraud, harass, bypass NewsTune consent, or falsely present the voice as an endorsement by the named person.
- The handoff expires or NewsTune rejects authorization; create a fresh handoff only after the user asks.

Do not infer endorsement from a voice name or availability. Never transfer raw audio through the model, and never claim a voice was selected, bound, or cloned until NewsTune reports completion.

Referenced files: 2 — file references are metadata, not package contents.