playout.video

View saved version →

---
name: best-time-to-go-live
description: Use when the user asks when their viewers watch, which day or hour is best to go live, or when to schedule a show or premiere.
---

# Best Time to Go Live

1. Ask for the user's time zone if you do not know it.
2. insights_get_heatmap (default window 28 days, narrow with playoutId or channelId). Cells are day of week (0 = Sunday) and hour in UTC: convert to the user's zone before answering.
3. Mention the sample count: hours with few samples are a weak signal. Missing data means there is not enough streaming to measure yet, not that nobody watches.
4. insights_list_sessions adds context (peak viewers per session).
5. Answer with the two or three best windows in the user's time zone. Offer to schedule a show there (the weekly-show-schedule skill).

Rules for every playout.video workflow:
- Read ids from the list tools (playout_list, playlist_list, media_list, channel_list). Never invent an id or reuse one from memory.
- Anything that starts, stops or changes a stream is visible to its audience. Say what will happen and let the user confirm before calling the tool.
- If a tool refuses, relay its reason in plain words. When a step needs a different plan, say which plan includes it and that plans are listed on playout.video. Do not quote prices and do not offer to upgrade or buy anything.
- The user's explicit instructions come before this skill's steps.

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

View saved version →

---
name: change-whats-on-air
description: Use when the user wants to skip, reorder, add or remove videos on a stream that is live right now, or play something once and go back to the loop.
---

# Change What's On Air

1. playout_get_state. What is playing is running.playlist.items, not the saved items. running.onAir says whether the loop or a play-once playlist is up.
2. Pick the tool for what the user wants:
   - Skip, reorder, add or remove videos on air: playout_edit_running_playlist with the full new list (copy rows you keep unchanged). Optionally jump to an item. A continuous stream follows its playlist, so this saves the new list to that playlist too.
   - Edit the saved playlist: playlist_get, then playlist_set_items. A running stream that plays it takes the new list within seconds.
   - Change what is on air but leave the saved playlist as it is: playlist_create with the new list, then playout_switch_playlist with switchType "loop".
   - Play another playlist once, then return: playout_switch_playlist with switchType "inline"; playout_cancel_inline ends it early.
   - Random order: playout_toggle_shuffle.
   - A scheduled stream refuses these while a calendar block is on air. Read the block with calendar_get and change it with calendar_update_entry, which takes effect on air straight away.
3. Say what viewers will see and when, and whether the saved playlist changes too. Confirm, then call the tool.
4. Check the result with playout_get_state.

Rules for every playout.video workflow:
- Read ids from the list tools (playout_list, playlist_list, media_list, channel_list). Never invent an id or reuse one from memory.
- Anything that starts, stops or changes a stream is visible to its audience. Say what will happen and let the user confirm before calling the tool.
- If a tool refuses, relay its reason in plain words. When a step needs a different plan, say which plan includes it and that plans are listed on playout.video. Do not quote prices and do not offer to upgrade or buy anything.
- The user's explicit instructions come before this skill's steps.

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

View saved version →

---
name: live-quizzes-and-polls
description: Use when the user asks about interactive live streams on playout.video: live quizzes, polls or games viewers play on their phones or in chat, and the AI host voice.
---

# Live Quizzes and Polls

Quizzes and polls run from the Live Studio in the playout.video app. This skill explains how and helps plan them; it does not start one from ChatGPT.

1. docs_search with the user's topic ("live quiz", "live poll", "phone answers chat", "player limits", "AI host voice"), then docs_get the best match.
2. Explain the steps from the article: setting up the quiz or poll, how viewers join (QR code on their phones or answers in chat), and the limits that apply to their plan.
3. Help write the content if asked: questions, answer options, poll ideas that fit their channel.
4. For an on-air graphic to go with it (Channel plan and up), graphic_guide first, then graphic_write, and graphic_attach to a Live Studio scene after the user confirms.

Do not say a quiz or poll was started: the user starts it in the Live Studio.

Rules for every playout.video workflow:
- Read ids from the list tools (playout_list, playlist_list, media_list, channel_list). Never invent an id or reuse one from memory.
- Anything that starts, stops or changes a stream is visible to its audience. Say what will happen and let the user confirm before calling the tool.
- If a tool refuses, relay its reason in plain words. When a step needs a different plan, say which plan includes it and that plans are listed on playout.video. Do not quote prices and do not offer to upgrade or buy anything.
- The user's explicit instructions come before this skill's steps.

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

View saved version →

---
name: multistream-to-more-platforms
description: Use when the user wants the same stream on more platforms at once: YouTube, Twitch, Facebook, LinkedIn, Kick, Instagram, TikTok, X or another RTMP server.
---

# Multistream to More Platforms

1. channel_list shows the connected accounts.
2. YouTube, Twitch, Facebook, LinkedIn and Kick need a sign-in. If one is missing, channel_connect_link gives the user a link to connect it in their own browser. When they say they are done, check channel_list again.
3. For a Facebook Page or LinkedIn page rather than a personal profile, channel_list_targets gives the ids destination_create needs.
4. Platforms that give a stream URL and key (Instagram, TikTok, X, any RTMP server): when the user provides both, channel_create_rtmp (Creator plan and up).
5. destination_create for each platform. The plan sets how many destinations one stream can have; a refusal says so.
6. If the stream is already live, each new destination goes live with destination_start (confirm first). If it is stopped, playout_start takes every destination live.
7. playout_get_state confirms each destination's liveState.

Rules for every playout.video workflow:
- Read ids from the list tools (playout_list, playlist_list, media_list, channel_list). Never invent an id or reuse one from memory.
- Anything that starts, stops or changes a stream is visible to its audience. Say what will happen and let the user confirm before calling the tool.
- If a tool refuses, relay its reason in plain words. When a step needs a different plan, say which plan includes it and that plans are listed on playout.video. Do not quote prices and do not offer to upgrade or buy anything.
- The user's explicit instructions come before this skill's steps.

View saved version →

---
name: playout-get-started
description: Use when the user is new to playout.video in ChatGPT, asks what it can do here, or wants their first stream. Looks at the workspace and walks the user to a stream that loops their own videos.
---

# playout.video Get Started

Goal: show the user what their workspace holds, then get them to a first stream that loops their own videos.

1. Call org_get_capabilities and playout_list. Tell the user which plan the workspace is on, how many streams it has, and whether any is live.
2. Call media_list. If the library has no ready videos, ask for links to videos the user owns or has the rights to stream (YouTube, Vimeo or a direct file link). For a channel or playlist link, call media_discover and let the user pick, then call media_import once per video. Imports take a few minutes; media_list shows status "ready" when a video can be used.
3. When at least one video is ready, offer to create a playlist from it (playlist_create) and a 24/7 stream from that playlist (playout_create).
4. Ask where the stream should go. channel_list shows which accounts are connected. YouTube, Twitch, Facebook, LinkedIn and Kick need a sign-in the user completes in their own browser: channel_connect_link gives them the link, and channel_list confirms it once they say they are done. Add the destination with destination_create. For a platform that gives a stream URL and key, use channel_create_rtmp first (paid plans).
5. Starting goes live publicly. Confirm, call playout_start, then playout_get_state and report whether the stream and each destination are running.

Tell the user before starting on the Free plan: a session runs up to 2 hours and is started by hand each time. Uploading files from a computer is done in the playout.video app.

Rules for every playout.video workflow:
- Read ids from the list tools (playout_list, playlist_list, media_list, channel_list). Never invent an id or reuse one from memory.
- Anything that starts, stops or changes a stream is visible to its audience. Say what will happen and let the user confirm before calling the tool.
- If a tool refuses, relay its reason in plain words. When a step needs a different plan, say which plan includes it and that plans are listed on playout.video. Do not quote prices and do not offer to upgrade or buy anything.
- The user's explicit instructions come before this skill's steps.

View saved version →

---
name: stream-health-check
description: Use when the user asks whether their stream is working, why it went offline, why a platform shows an error, or whether anything went down overnight.
---

# Stream Health Check

1. playout_list, then playout_get_state for each stream the user cares about (all of them if they did not say).
2. For each stream report: is it on air (isRunning and running.status), what is playing (running, not the saved items), and for each destination its liveState with any error text.
3. For "did it go down?", call insights_list_sessions. An "error" end followed by a new session of the same destination minutes later is the push reconnecting by itself, not downtime. Say so.
4. For YouTube destinations, destination_list_archive_parts shows the current part and when the last 11-hour rotation happened.
5. For an error message you cannot explain, docs_search with its key words, then docs_get.

Output: one short block per stream: on air or not, each platform's state, the last error if any, and the next step.
Only fix things the user asks you to fix, after confirming. A destination that stopped while its stream keeps running is restarted with destination_start; a stopped stream is started with playout_start.
Do not guess causes the data does not show.

Rules for every playout.video workflow:
- Read ids from the list tools (playout_list, playlist_list, media_list, channel_list). Never invent an id or reuse one from memory.
- Anything that starts, stops or changes a stream is visible to its audience. Say what will happen and let the user confirm before calling the tool.
- If a tool refuses, relay its reason in plain words. When a step needs a different plan, say which plan includes it and that plans are listed on playout.video. Do not quote prices and do not offer to upgrade or buy anything.
- The user's explicit instructions come before this skill's steps.

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

View saved version →

---
name: weekly-show-schedule
description: Use when the user wants shows at set times, for example a show every Friday at 8 pm, instead of one playlist on a loop.
---

# Weekly Show Schedule

1. Confirm the time zone the user plans in.
2. Find a calendar stream with playout_list, or create one with playout_create_scheduled.
3. Call calendar_get before any change, and again whenever its result is no longer in front of you. Never write entries from memory.
4. Add each show with calendar_add_entry: the videos (ids and lengths from media_list), the start and end as instants in the calendar's time zone, and daysOfWeek for a repeating show.
5. Read the schedule back in the user's words ("every Friday 20:00 to 21:00, Madrid time").
6. Starting and stopping the stream around the shows by itself (lifecycle AUTO) needs the scheduling feature, which comes with the Channel plan and up; without it the user starts the stream by hand.

Change one show with calendar_update_entry, remove one with calendar_delete_entry. Shows that already aired are a read-only record.

Rules for every playout.video workflow:
- Read ids from the list tools (playout_list, playlist_list, media_list, channel_list). Never invent an id or reuse one from memory.
- Anything that starts, stops or changes a stream is visible to its audience. Say what will happen and let the user confirm before calling the tool.
- If a tool refuses, relay its reason in plain words. When a step needs a different plan, say which plan includes it and that plans are listed on playout.video. Do not quote prices and do not offer to upgrade or buy anything.
- The user's explicit instructions come before this skill's steps.

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

View saved version →

---
name: youtube-24-7-stream
description: Use when the user wants a live stream that runs around the clock on YouTube from their own videos, or asks how to keep a looping YouTube stream going with every part of it saved.
---

# 24/7 YouTube Stream Setup

Input: a stream (or videos to build one) and a connected YouTube channel.

1. Find the stream with playout_list, or build one as in the get-started skill (media_import, playlist_create, playout_create).
2. Call channel_list. If no YouTube channel is connected, call channel_connect_link with platform YOUTUBE and give the user the link. They sign in to YouTube in their own browser. When they say they are done, check channel_list again, then continue.
3. Add the YouTube destination with destination_create. Without a broadcast id it creates a new public broadcast.
4. Explain what the plan allows, from org_get_capabilities:
   - Free: each session stops after 2 hours and its broadcast ends, so YouTube saves every session as its own video.
   - Paid plans: the stream can run continuously. YouTube may not save a broadcast longer than about 12 hours, so offer destination_set_archive_rotation, which starts a new broadcast every 11 hours. Each part gets its own watch link and live chat starts fresh.
5. If the user wants watch hours to count, check the broadcast is public with broadcast_get_details.
6. Only if the user says the videos show realistic AI-generated or altered people, voices or scenes, turn on destination_set_altered_content.
7. Confirm, then playout_start. Check with playout_get_state that the YouTube destination's liveState is running.

Do not promise monetization or Partner Program approval; YouTube decides. Do not add "LIVE" wording to titles for recorded content unless the user asks for it.

Rules for every playout.video workflow:
- Read ids from the list tools (playout_list, playlist_list, media_list, channel_list). Never invent an id or reuse one from memory.
- Anything that starts, stops or changes a stream is visible to its audience. Say what will happen and let the user confirm before calling the tool.
- If a tool refuses, relay its reason in plain words. When a step needs a different plan, say which plan includes it and that plans are listed on playout.video. Do not quote prices and do not offer to upgrade or buy anything.
- The user's explicit instructions come before this skill's steps.

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

View saved version →

---
name: youtube-watch-hours-planner
description: Use when the user wants to reach YouTube Partner Program watch hours with their streams, or asks why live stream watch time is not counting.
---

# YouTube Watch Hours Planner

1. channel_list to find the YouTube channel, then channel_list_videos. Count the uploads flagged qualifyingLongForm (public and not short): these are what the watch-hour rules count.
2. For each stream with a YouTube destination, playout_get_state: is archive rotation on? Then broadcast_get_details on its broadcast: is it public?
3. Explain from the help center (docs_search "watch hours archive rotation", then docs_get): only saved, public archives keep counting; YouTube may not save a broadcast longer than about 12 hours; the 11-hour rotation keeps every part saved.
4. insights_get_overview shows viewer hours over a period.
5. Give the user a checklist of what is in place and what is missing.

Never promise approval: YouTube reviews channels and decides. Do not suggest presenting recorded videos as live events.

Rules for every playout.video workflow:
- Read ids from the list tools (playout_list, playlist_list, media_list, channel_list). Never invent an id or reuse one from memory.
- Anything that starts, stops or changes a stream is visible to its audience. Say what will happen and let the user confirm before calling the tool.
- If a tool refuses, relay its reason in plain words. When a step needs a different plan, say which plan includes it and that plans are listed on playout.video. Do not quote prices and do not offer to upgrade or buy anything.
- The user's explicit instructions come before this skill's steps.