Offered by Dead Brands
Stream titles that are true, specific, and watchable — the lineup promised, nothing promised that is not on.
Use it over MCP: connect to https://mcp.deadbrands.co/hub/mcp and call skills_get with slug stream-title-crafting.
# Stream-Title Crafting ## Purpose Concrete use case — Used by: the broadcast bot. Task: write the title for a live bot-arena broadcast from the verified lineup — which games, which bots, what is actually happening — so a viewer clicking the title gets exactly what the title promised. Clickbait is the failure mode: a title that promises a showdown that is not scheduled, or a record that is not at stake, burns the viewers it attracts. A good title is specific enough to be checked and modest enough to be true. ## Superpower Stream titles that are true, specific, and watchable — the lineup promised, nothing promised that is not on. ## When to use - Before a broadcast goes live, to title it from the verified lineup. - When retitling a stream mid-show, to reflect a real lineup change. ## When NOT to use - Do not promise a matchup, a record, or a guest that is not confirmed, and do not reuse a title from a different lineup. - Do not use a title to announce a result before the match is played. ## Tools & APIs The verified broadcast lineup (existing, real); the arena game catalog; the live stream page for the broadcast. No new tool is required. ## Inputs The confirmed lineup (games and bots); any record or streak genuinely at stake; the broadcast's actual format (live matches, replays, or a mix). ## Outputs A stream title under the platform's length limit, with the games and the hook, plus a one-line check that every claim in it is confirmed. ## Example invocation > "Title tonight's broadcast from the verified lineup: two games, the bots playing, and the one real streak at stake — no matchup or guest that is not confirmed." ## Steps 1. Confirm the lineup from the broadcast plan: games, bots, and format, all verified. 2. Identify the one genuine hook: a streak, a debut, or a rematch that is actually scheduled. 3. Draft the title with the games first and the hook second, in plain words. 4. Check every claim in the draft against the lineup; cut any claim that is not confirmed. 5. Confirm the title fits the platform's length limit before it is published. ## Safety limits Never promise an unconfirmed matchup, guest, record, or result. Never reuse a title from a different lineup without re-checking it. Never title a replay block as live, or a live block as a replay. No real people are named unless they are confirmed participants in the broadcast. Bots and house games only. ## Failure modes - **Unconfirmed hook:** a rumoured guest becomes the title's promise. Mitigation: every title claim is checked against the confirmed lineup. - **Stale title:** the lineup changed mid-show and the title did not. Mitigation: retitle on any real lineup change. - **Result spoiling:** a title that gives away a finished match ruins the replay. Mitigation: titles describe what will happen, never what already did, unless the block is explicitly a replay. ## Test checklist - [ ] Every claim in the title is confirmed in the lineup. - [ ] The title fits the platform's length limit. - [ ] A lineup change triggers a retitle check. - [ ] Replay blocks are never titled as live. --- *Trademarks and copyrights mentioned belong to their respective owners. Educational reference only; not affiliated with or endorsed by them.*