Skill detail

tech-podcast-youtube-channel

Runs an organizer's own standing podcast or YouTube channel as a cross-edition media property, covering cadence, guest sourcing, and handover.

MatchPossibleRecommended for YouTube Videos
Sourcesamber/​dev-event-organizer-skillsExternal source
Reported installs1,602Popularity signal only

Inspect before use

Read the source instructions and check the requirements before you install this skill.

Saved source preview

SKILL.md

The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.

---
name: tech-podcast-youtube-channel
description: Run an organizer's own standing podcast or video channel as a cross-edition media property - whether to sustain a channel at all, the cadence commitment and its named owner in the quiet months, guest sourcing from the speaker pool outward, the two-way feed with the event cycle, and the wind-down or handover when organizers change. Use whenever the user mentions starting a conference podcast or YouTube channel, publishing between editions, where episode guests come from, who owns the show when an organizer leaves, or closing one down - even if they never say "podcast". Do NOT use for cutting one edition's talk recordings into clips - use samber/dev-event-organizer-skills@event-content-repurposing instead.
license: MIT
metadata:
  author: Samuel Berthe
  version: "1.0.1"
---

# Tech Podcast and Video Channel

You run one organizing team's own standing media property: a podcast or video channel that publishes on its own cadence, keeps its own back-catalogue, and outlives any single edition of the event.

Treat the object as a **property**, not an artifact. The outcome is "this show is still publishing next year, and the people it reaches are people the room could not hold."

Inherit the decision to have one. `samber/dev-event-organizer-skills@event-portfolio-strategy` decides whether a recurring media property belongs in the team's set of properties at all; run it once that answer is yes. Never recommend adding or retiring the property itself: that recommendation routes back there.

Produce four outputs:

- an existence posture with a named owner for the months when no edition is imminent
- a guest pipeline scoped to what the team can actually vet
- a written feed relationship in both directions with the event cycle
- a handover that survives the current organizers leaving

## Where the line is

**A recording has three owners in sequence, and you are the third.**

- Capture - signal path, microphone count, redundancy, capture-time consent: `samber/dev-event-organizer-skills@event-production`. Consume a finished recording as episode input; never signal path, mixing, redundancy or editing execution.
- Binding rule: never publish a recording the consent record does not cover.
- Remote capture: `samber/dev-event-organizer-skills@virtual-event-production`.
- The dual-audience case: `samber/dev-event-organizer-skills@hybrid-event-design`.

**One-edition derivatives are `samber/dev-event-organizer-skills@event-content-repurposing`.** That skill states the line from its own side - _"A standing owned-media property is not yours."_ - and its audio-cut rung _"stops being dominated the moment Q8 says a standing audio property already exists"_.

It asks this side to _"state the line plainly from here, and flag that it must be restated from there"_. Plainly, then: **a one-off derivative tied to one edition's captured output is that skill; a standing property with its own format, guest sourcing and cross-edition cadence is this one.** Two-sided and settled.

**The interactive member space is `samber/dev-event-organizer-skills@event-community-building`, and this is the sharpest seam.** Both live between editions and both keep an audience warm. The test is the object:

- that skill animates a space members belong to and can post into, with a membership list and a retention duty on that list
- this skill runs a published content property with a subscriber base that may never overlap the attendee list

Its opening - _"You inherit a space rather than choosing one."_ - is the sentence this skill mirrors for the property. Its interview treats a channel as pre-existing input, listing what already carries the audience as _"an announcement list, an archive, a podcast, nothing"_. Its heaviest rung routes its ceiling to a standing meetup series: it names what it is _"one step from becoming"_ in the event direction and names nothing in the broadcast direction. That silence is this seam.

Across that seam, 
Read the full source on GitHub (opens external page)
Context

Related work