Writes broadcast-ready closing scripts for news reports, podcasts, or documentaries, matched to show tone and episode content. Useful when a sign-off formula needs refreshing or a special episode demands a stronger closing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/autopunk-media-skills:sign-off-writerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Writes a polished, broadcast-ready closing script for a presenter, reporter, or podcast host — matched to the show's tone and the specific episode content — that ends the programme with authority and purpose.
Writes a polished, broadcast-ready closing script for a presenter, reporter, or podcast host — matched to the show's tone and the specific episode content — that ends the programme with authority and purpose.
Required:
Optional:
[Short — traditional broadcast], [Extended — documentary closing], [Conversational — podcast outro])Format: Podcast episode Host: Solo host, goes by first name only ("Reuben") Show: The Long View — a history podcast for general audiences that finds contemporary relevance in overlooked historical events Episode topic: The 1930s drought that forced the closure of the London docks and what it tells us about infrastructure fragility Episode conclusion: The episode argued that large infrastructure systems are not built to be resilient — they are built to appear resilient, and the difference only becomes visible when they fail Show tone: Thoughtful, unhurried, slightly literary — not academic Standard elements: End with a prompt to subscribe and a line about the next episode (topic: the 1953 North Sea flood and the politics of coastal defences) Variants needed: Three
[Option 1 — Reflective closing, medium length]
The docks did not simply close because the water table dropped. They closed because no one had designed them for the possibility that it might. Resilience, it turns out, is mostly a story infrastructure tells about itself — right up until it can't.
Thank you for listening to The Long View. If you found this episode worth an hour of your time, please subscribe wherever you get your podcasts. Next time, we're moving to 1953 and the North Sea flood — and the political arguments about who gets to decide which coastlines are worth defending. I'm Reuben. See you then.
[Option 2 — Shorter, sharper ending]
The lesson from the docks is a simple one: the difference between infrastructure that works and infrastructure that fails is mostly invisible until it matters. And by then, it is too late to be surprised.
Subscribe to The Long View if you haven't already — and join me next time for the 1953 North Sea flood, and the uncomfortable question of which land is worth protecting. I'm Reuben.
[Option 3 — More literary, dwelling on the episode's central image]
There is something worth sitting with in the image of a working dock going dry — not dramatically, not all at once, but slowly, over weeks, as the water retreats and the boats settle at odd angles in the mud. Infrastructure does not announce its vulnerability. It just keeps working, and working, and then one day it doesn't, and everyone is surprised who probably should not have been.
That's The Long View for this week. Subscribe if you'd like more of this — and next time, we're going to the North Sea in the winter of 1953, when the water came the other way. I'm Reuben. Thanks for listening.
npx claudepluginhub ur-grue/autopunk-media-skills --plugin autopunk-media-skillsWrites episode-specific podcast intro and outro scripts matched to a show's tone, format, and brand, with hook, context, and CTA.
Creates podcast episodes, interviews, dialogues, and audio dramas via interactive prompts, Claude script generation, Gemini TTS multi-speaker voices, Lyria intro/outro music, and FFmpeg assembly.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.