Webinar Follow-Up Writer

What it does

Using the webinar's outline, slides, or a transcript, writes a follow-up email to attendees with the recording link, key takeaways, and any promised resources, plus a separate public-facing recap blog post for people who didn't attend. Pulls the actual questions asked during Q&A to answer them explicitly rather than sending a generic thank-you note.

Install

This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:

Use it in your AI assistant

Claude Code

.claude/skills/webinar-followup-writer/ (or ~/.claude/skills/webinar-followup-writer/ for all projects)

GitHub Copilot (VS Code)

.github/skills/webinar-followup-writer/

OpenAI Codex

.codex/skills/webinar-followup-writer/

Cursor

.cursor/skills/webinar-followup-writer/ (or ~/.cursor/skills/webinar-followup-writer/ globally)

Compatibility

Any WordPress site; works from a webinar transcript, slide deck, or outline, no specific webinar platform integration required.

The complete SKILL.md for this skill:

---
name: webinar-followup-writer
description: Use when a user wants a post-webinar follow-up email and recap post drafted, or asks for a "webinar recap" or "attendee follow-up".
---

# Webinar Follow-Up Writer

## When to use
A webinar just finished and the user needs an attendee follow-up email plus a public recap post drafted from the actual content covered, not generic thank-you copy.

## Procedure
1. Read the transcript, outline, or slides to identify 3-5 real takeaways, not a generic summary of the topic.
2. Draft the attendee follow-up email: thank you, recording link placeholder, takeaways, and any resources promised live.
3. Pull actual Q&A questions from the transcript and answer each briefly in the email or a linked FAQ section.
4. Draft a separate public recap blog post for non-attendees, written to stand alone without assuming they watched anything.
5. Suggest one clear next step rather than several competing calls to action.

## Guardrails
- Don't fabricate a Q&A answer for a question that wasn't actually asked or answered live, note it as unanswered instead.
- Keep the public recap generic enough that it doesn't reveal attendee-specific comments or names without permission.