event-content-repurposing

Plans derivative content, release cadence, rights review, and licensing from published conference recordings.

1|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-content-repurposing-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-content-repurposing
Source: https://github.com/samber/dev-event-organizer-skills/tree/main/skills/event-content-repurposing
Command: npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-content-repurposing-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After a conference, teams often let published talk recordings sit unused, or they publish derivative clips and photos without checking consent records, third-party material, or licensing. This Skill turns an edition's already-captured material into a dated, owned plan of derivative artifacts that respects speaker consent and attendee photo opt-outs. ## Core Features & Use Cases - Derivative mix and release planning: Choose among write-ups, short clips, social threads, transcript pages, and audio cuts, then schedule them as a dump, batched release, drip, or evergreen re-surfacing based on who actually owns publishing after the event. - Rights and licence gate: Mark every session usable, restricted, or off-limits against the consent record, screen clips for third-party material and identifiable attendees, and decide an explicit licence per artifact. - Speaker amplification and handover: Build a scoped post-event ask for speakers, hand scheduled pieces to the channel owner with dates and licence lines, and pass a content inventory to the next edition's marketing plan. - Use Case: Your conference videos just went live and the team is exhausted. Use this Skill to produce a realistic batched release plan with a write-up first, clips only for the sessions people asked about, and every line carrying a date and a named owner. ## Quick Start Ask the assistant to plan what derivative content to make from your published conference recordings, including release dates, rights checks, and licensing.

Frequently Asked Questions about event-content-repurposing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What should we do with conference talk recordings after the event?

Start from the published masters and pick a derivative mix: a written write-up first, short clips for the sessions attendees asked about, and optionally transcript pages or audio cuts. Schedule them as a batched release with a date and named owner on every piece.

Should we release conference content all at once or drip it weekly?

A drip only works when the event recurs and a named owner has a standing slot through a stated end date. Without both, choose a batched release or a dated dump, since the later half of a drip is what an exhausted post-event team drops.

Can we cut clips if the speaker release only covers recording and publication?

A release covering recording and publication does not license re-cuts or derivative works, so treat those sessions as restricted and link to the master instead of cutting. Route the gap to whoever owns consent collection so the next edition's release covers derivatives.

Can we publish a clip that has background music or third-party slides?

Run a rights check before cutting: clear the material with the rights holder, cut those frames, or drop the clip. A clip where licensed music runs through the key moment has no partial version and should be dropped unless cleared.

Which conference photos are safe to post when badges had no-photo stickers?

If the opt-out signal is not retrievable per photo, restrict the whole set to wide shots where nobody is identifiable, or do not use it. Silence after the event is not consent, and the code of conduct carries no photo-consent mechanism.

Should conference talk recordings carry a Creative Commons licence?

There is no shared convention, so decide explicitly and record who decided. You cannot grant more than the consent record gave, and a licence on a derivative containing third-party material licenses someone else's work, so publish those without an open licence and say so.