live_tweeting_events v1.0.0

name: "live_tweeting_events" description: "Cover an event live on social: pre-drafted post shells, photo and video cadence that doesn't flood the feed, threading discipline for key moments, and a post-event recap. Triggers when the user asks to live-tweet, live-post, or cover an event/conference/keynote/show in real time on social media." metadata: { "includeInPrompt": true }

Live Tweeting Events

Purpose

Turn event attendance into real-time social coverage that reads like a story, not a firehose: prep before, post selectively during, thread for continuity, and assemble the recap while details are fresh. Works for conferences, keynotes, trade shows, concerts, and community events, on X/Threads or anywhere with threaded short posts.

Workflow

1. Before the event (at least an hour out)

• Confirm the official event hashtag. If none exists, pick one: short, unique, easy to spell.
• Build the roster: official account handle, speaker handles, sponsor handles. Save them in a note so every post is one paste away. Attribute every quote by name or handle.
• Ask: is any content embargoed or off the record? Honor it. If a speaker asks not to be shared, don't post them.
• Draft the post shells (see references/post-shells.md): session kickoff, key quote, photo-with-speaker, audience reaction, poll or question, wrap-up. Fill slots, leave the meat blank.
• Decide the thread structure in advance: one lead post per session, replies under it. Late joiners should be able to read the lead post and get the gist.
• Make sure the phone is charged, the venue wifi details are saved, and the camera lens is clean.

2. During the event: post like a curator, not a transcriber

• Post the lead kickoff first: who is speaking, what the session is, the hashtag. One photo of the speaker or stage if it is worth it.
• Be selective. A speaker talking for 40 minutes yields 3 to 5 posts: the headline idea, the best quote, the surprising stat or slide, the audience reaction, the takeaway. Summarize several points into one post instead of drip-posting every sentence.
• Thread replies under the session's lead post. Keep related posts together so the thread reads as one story. Start a fresh thread for the next session or topic shift.
• Media cadence: one photo per key moment, not one per minute. Crop slides so the key point fits the preview. Retake blurry shots or skip them. Use short video for moments that carry energy (demo, applause, reveal); stills for quotes and slides.
• Write like a reporter: attribute quotes ("@handle: ..."), describe what's happening with enough context for someone not in the room, and add your own take when it adds value. Don't narrate yourself ("I'm sitting here thinking...").
• Engage the hashtag: reply to attendees, answer questions people ask about the session, reshare the best attendee posts. Polls during breaks are good crowd bait.
• Speed beats polish. Post the clip or quote now with a short caption; the clean version belongs in the recap. Keep captions factual and short so they read at a glance.
• Stop when there is nothing new worth posting. A quiet stretch with no posts is better than filler.

3. Key moments (plan for them, don't chase them)

• Mark the likely big beats ahead of time: opening, headline announcement, demo, Q&A highlight, closing call to action.
• For each: the shell post is drafted, the media is ready to shoot, and you know who to tag. When it lands, post within a minute.
• For product reveals: one clear photo, the core fact (what, price, availability), the hashtag, and the speaker handle. That post becomes the reference everyone links to.

4. Post-event recap (within 24 to 48 hours)

• Assemble while details are fresh. Gather: the threads you posted, any photos or clips you held back, the best attendee replies, poll results.
• The recap shape: a short thread or post series with 3 key takeaways, 1 or 2 standout quotes, the best 3 to 5 photos or clips, and a thank-you to organizers and speakers. Then, if the audience wants it, a longer piece (blog or carousel) repackaging the coverage.
• Keep the event hashtag in the recap so it joins the same stream as the live coverage.
• Review the metrics: which posts carried, which flooded. Feed that into the next event's plan.

Output Contract

Given an event name, date, hashtag, and speaker roster, produce:

1. coverage-plan.md: hashtag strategy, roster table (name, handle, role), thread map (lead posts per session/topic), likely key moments with their shells, and the embargo list.
2. post-shells.md (from references/post-shells.md, filled in): one copy per session, with slots filled for hashtag, speaker, handles.
3. After the event, the recap thread text: 3 takeaways, standout quotes, media picks, thank-yous, ready to post.

Operating Rules

1. Hashtag in every post. If followers muted the tag, your coverage won't reach them; if you forget the tag, delete and repost with it.
2. Attribute everything you quote. Never invent a quote, number, or stat: paraphrase when unsure, and drop it if you can't verify on the spot.
3. One thread per session. Don't start a new top-level post for every thought.
4. Flood test: before posting, ask whether this post adds something new. If a similar post went out in the last 10 minutes, merge or skip.
5. Embargoes are absolute. "Don't share this" always outranks "this would post well."
6. Never ask the model to post automatically mid-event. Every post gets a human glance before it goes out: typos during live coverage read as careless, not fast.
7. Keep the recap honest: if a session was thin, don't manufacture highlights from it.
8. Source the facts you claim. Coverage guidance here draws on live-tweeting best-practice writeups; the full source list lives in the job scratch notes at ~/workspace/skill-production/scratch/live-tweeting-events-sources.md.