| name | event-recap-generator |
| description | Use this skill whenever someone shares notes, a transcript, or a summary from an event, webinar, panel, training, workshop, study hall, or open mic and wants it turned into a shareable recap. Triggers on: "write a recap", "summarize this event", "turn this into a blog post", "I need a writeup of this webinar", "recap this for the newsletter", or when event/webinar notes or transcripts are shared with intent to publish or distribute. Also triggers when someone asks for social media posts about an event that happened.
|
Event Recap Generator
You are turning raw event content (notes, transcripts, summaries) into polished, shareable recaps
in multiple formats. Your job is to capture what was valuable about the event and present it in a
way that makes people who weren't there wish they had been -- and gives attendees a useful reference
to share.
Output Format
Always produce all three formats together, separated by clear headers.
Format 1: Full Recap (Blog/Website)
Length: 300-500 words
Structure:
[Event Title]: [Compelling subtitle that captures the main theme]
Opening paragraph: What was this event? Who was there? What was the main thread or question?
(2-3 sentences, engaging and specific -- not "On [date], [org] hosted a webinar about AI.")
Key Takeaways
3-5 takeaways, each as a bolded one-line summary followed by 1-2 sentences of context. These
should be the things someone would actually want to know -- insights, surprises, practical advice,
or important framings.
Notable Quotes (if available from transcript)
1-3 direct quotes that were particularly sharp, surprising, or well-stated. Attribute clearly.
Only include if the source material has actual quotes -- don't fabricate.
Resources Mentioned
Bulleted list of any tools, articles, reports, or organizations referenced during the event.
Include links if available.
What's Next
1-2 sentences on upcoming events, follow-up opportunities, or next steps mentioned.
Format 2: Short Version (Newsletter/Email)
Length: 100-150 words
Structure: One tight paragraph that answers: What happened? What mattered? Why should
someone care?
This should work as a standalone newsletter blurb or email section. No headers, no bullets --
just a well-crafted paragraph that makes someone want to click through to the full recap.
End with a clear CTA if appropriate: a link to the full recap, the next event, or a resource.
Format 3: Social Posts
Produce 3 posts, each tailored to a different platform:
Twitter/X (~280 characters): The single most compelling takeaway or quote. Direct, punchy.
Include a relevant link placeholder.
LinkedIn (~600-800 characters): A slightly more developed version -- what happened, why it
matters, what people should do about it. Professional but not corporate. Can include 2-3 short
bullet points.
Bluesky (~280 characters): Similar to Twitter but can assume a slightly more insider/tech-savvy
audience. More casual tone.
Steps
-
Read the full input before starting. Understand the arc of the event -- what was it about?
What moments stood out? What would someone tell a colleague about it the next day?
-
Identify the 3-5 strongest takeaways. These drive all three output formats. Look for:
insights that surprised the room, practical advice people could act on, new framings of
familiar problems, and moments of agreement or productive disagreement.
-
Pull notable quotes if the transcript includes direct speech. Choose quotes that are
specific and vivid, not generic. "We need to stop treating AI like a magic wand and start
treating it like a power tool" is good. "AI is really important for the future" is not.
-
Write the full recap first -- this is the foundation. Then compress for the other formats.
-
Write the short version by distilling the full recap to its essence. Don't just cut words --
rewrite for the format.
-
Write social posts last -- by now you know the strongest hook.
-
Present all three formats in a single response with clear section headers.
Tips
- The voice should match the event's energy. A high-energy open mic with 200+ attendees reads
differently from an intimate 10-person workshop. Match the tone.
- For progressive movement events, the audience likely shares certain values -- you can assume
familiarity with concepts like "building power," "ecosystem," "downballot," etc. Don't
over-explain movement language.
- If the event had multiple speakers or panels, give credit by name. People share recaps when
they're mentioned in them.
- If the notes are thin (just bullet points, no transcript), work with what you have and note
what you'd need for a richer recap: "For future events, a transcript would allow me to pull
direct quotes and capture more nuance."
- Don't hype. If the event was a straightforward information session, say so. The recap should
be honest about what happened, not inflate it into something it wasn't.
- Avoid cliches: "In today's rapidly changing landscape," "now more than ever," "exciting
developments." Be specific instead.
