Create an Event Social Media Kit

Writes before, during and after posts for your company page, executives, employees, speakers and partners, with a dated posting calendar and a tracking link per poster.

Example prompts

Once the skill is added, start a chat with one of these and attach your file if you have one.

  • Write 10 LinkedIn posts for our team to share before the show. Not 'visit us at booth 402'.

  • Make a speaker promo kit: 3 posts each speaker can share with their session link.

  • Write a recap post from these show notes and photo captions.

What this skill does

This skill writes every social post around one event for everyone who'll post: the company page, executives in their own voice, employees with varied first lines, speakers and partners. Each pre-event post gives people a concrete reason to engage, like a session, a meeting slot or a demo, instead of just a booth number.

It plans the arc from announcement to recap, turns each slot into a real date, and adds a tracking link per poster group. You also get live posting prompts with a capture list, a speaker kit, a partner kit and a short how-to for employees.

When to use it

  • Promoting your trade show presence on LinkedIn
  • Giving speakers ready-to-post copy for their session
  • Running employee advocacy around an event
  • Writing a post-event recap that people will read
  • Promoting a webinar or user conference on social

How it works

  1. 1Find the reasonsLists every concrete reason someone would care, such as sessions, meetings, demos or research, and ranks them.
  2. 2Plan the arcMaps posts to announce, reasons, final push, live and recap phases with real dates.
  3. 3Write by voiceDrafts posts for the company page, executives, employees, speakers and partners, each in its own voice and length.
  4. 4Add trackingGives every poster group its own UTM value so you can see whose posts drove clicks.
  5. 5Check and hand overChecks asks, dates, embargoes and permissions, then returns drafts only.

What you'll need

  • Event name, dates, location and your role
  • Reasons to engage: sessions, meetings, demos, side events
  • Who will post and their voice
  • Show notes and photo captions for the recap

What you get

A posting calendar (also as CSV) with date, phase, poster, angle, hook, CTA, tracked link, asset needed and status. Then the full posts grouped by poster, a speaker kit, a partner kit, live posting prompts with a capture list, recap posts and a five-point how-to for employees.

Tips

  • Pair the booth number with what happens there and when, like demo times or a workshop slot.
  • Ask employees to rewrite the first line so feeds don't fill with identical posts.
  • Get permission before posting attendee photos or quotes, and blur badges.
  • Post the recap within two business days, leading with one useful takeaway.

What's in the download

  • event-social-kit/SKILL.md6.8 KB
  • event-social-kit/references/post-examples.md2.4 KB
  • event-social-kit/references/posting-plan.md1.8 KB
Read the SKILL.md
---
name: event-social-kit
description: Creates a social media kit for a B2B event, mostly for LinkedIn. Writes company page posts, employee and executive posts in different voices, speaker and partner share copy, booth, meeting and session promo posts, live posting prompts and post-event recap posts, with a dated posting calendar and tracking links. Use for LinkedIn event promotion, trade show posts that give a reason to visit beyond a booth number, speaker promo kits, employee advocacy for an event or a recap post.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: promotion
  source: https://eventmarketingsoftware.com/skills/event-social-kit
---

# Event Social Kit

Writes every social post around one event, before, during and after, for everyone who'll post: the company page, executives, employees, speakers and partners. Each post gives people a reason to show up, book time or register. "Visit us at booth 402" alone isn't a reason.

## Intake

If the user has an `event-context.md` file, read it first and don't ask for anything it already answers (company, ICP, tone, campaign naming).

Ask for whatever is missing in ONE message:

1. Event name, dates, city or "online", your role (host, exhibitor, sponsor, speaker, attendee) and the event hashtag if there is one.
2. The reason to engage: session titles and times, booth number, meeting booking link placeholder, demo of something new, giveaway, dinner or side event, report launch.
3. Who'll post: company page, named executives (with a line on each one's voice), employees attending, speakers, partners or sponsors.
4. Channels (default LinkedIn; add others only if asked) and how many posts per person.
5. Promotion start date, and anything that's under embargo until a date.
6. For a recap: notes, numbers they can share, photo captions and who appears in photos.

Work with partial answers and use placeholders like `[SESSION LINK]` and `[PHOTO: team at booth]`.

## Data sources (connectors optional)

- If a Google Sheets connector is available, offer to write the posting calendar to a new tab so posters can claim rows.
- If a Slack connector is available, you may draft a message for the event or employee channel with the employee posts. Post only after the user approves the exact text.
- Otherwise, return Markdown plus a downloadable CSV of the calendar.
- Don't fetch URLs or event pages. Never require a paid service. Don't post to any social network.

## Method

1. **Find the reasons.** List every concrete reason someone would care: a session, a meeting slot, a new product, a customer speaker, research, a small event. Rank by audience value. Build posts around the top reasons, not the logistics.
2. **Plan the arc.** Use the default calendar in [references/posting-plan.md](references/posting-plan.md): announce (2 to 3 weeks out), reasons (1 to 2 weeks out), final push (1 to 3 days out), live (during), recap (within 2 business days after). Turn every slot into a real date.
3. **Write by voice.**
   - Company page: clear, factual, one CTA, can tag speakers and partners.
   - Executive: first person, a point of view on the topic, why they're going, no product pitch. 80 to 200 words.
   - Employee: first person, short, personal reason ("I'll be at the demo bar Wednesday, come say hi"), easy to edit. Write several variants so feeds don't fill with identical posts.
   - Speaker kit: first person for the speaker to post, with the session title, time and link; plus a short version.
   - Partner or sponsor kit: share-ready copy that names both companies and the joint reason.
4. **Write live prompts, not live posts.** Give templates with blanks ("Best line from [speaker] so far: [quote]") and a short list of what to capture (session moments, booth demos, team photo) with a reminder to get permission before posting people's faces or quotes.
5. **Write the recap.** Lead with one useful takeaway, not "what a week". Include numbers only if the user gave them and can share them. Thank speakers and partners by tag placeholder. End with a next step (replay, report, next event).
6. **Add tracking.** Give each poster group its own UTM content value (e.g. `utm_source=linkedin&utm_medium=social&utm_content=exec-maria`) on the CTA link.
7. **Check format details.** Hooks in the first line (it's what shows before "see more"), line breaks for scanning, 3 or fewer hashtags, mentions as `@[Name]` placeholders so the poster tags the right account.

Domain rules that matter:
- Every pre-event post has one clear ask: register, book a meeting, attend a session, or find a specific person.
- Exhibitors: pair the booth number with what happens there and when.
- Don't post attendee names, photos or quotes without permission. Don't share customer names as attendees unless they agreed.
- Respect embargoes: no launch details before the date the user gives.
- Executives' posts must sound like them. If no voice notes are given, write neutral first drafts and say so.

Examples by voice: [references/post-examples.md](references/post-examples.md).

## Output templates

**1. Posting calendar** (also as CSV):

| # | Date | Phase | Poster | Channel | Reason or angle | Hook (first line) | CTA | Link with UTM | Asset needed | Status |
|---|---|---|---|---|---|---|---|---|---|---|

Phase is `Announce`, `Reasons`, `Final push`, `Live` or `Recap`. Status starts as `Draft`.

**2. Posts grouped by poster**, each with: date, full text, hashtags, mentions, asset note.

**3. Speaker kit** (per speaker or one template), **4. Partner kit**, **5. Live prompts and capture list**, **6. Recap post(s)**, **7. Employee how-to** (5 bullets: when to post, edit the first line, tag, reply to comments, don't post attendees without permission).

## Validation checklist

- [ ] Every pre-event post states one ask and a reason beyond a booth number.
- [ ] Dates are real, in order, and match the arc; recap is within 2 business days after.
- [ ] Employee variants differ in their first lines.
- [ ] No invented facts, numbers, attendees or customer names.
- [ ] Each poster group has its own UTM content value.
- [ ] Hashtags 3 or fewer per post; mentions are placeholders.
- [ ] Embargoed details don't appear before their date.
- [ ] House style: contractions, plain words, no hype, no dashes as punctuation.

## Approval gates

- Return all posts as drafts. Never publish to any social network, and never post to Slack or write to a sheet without showing the exact content and getting a clear yes.
- For executive posts, recommend the executive approves their own text.

## Privacy

- Get permission before naming or showing attendees, customers or booth visitors. Blur badges in photos.
- Don't include personal data from lead lists in any post.

## Related skills

event-invite-sequence (email promotion), event-landing-page (the page posts link to), pre-show-meeting-outreach (1:1 meeting asks), webinar-repurposing (post-event content from recordings).

FAQ

What should I post on LinkedIn before a trade show?
Give people a reason to find you beyond a booth number: a session, a demo of something new, a short workshop, a dinner or bookable meeting slots. Announce two to three weeks out, share specific reasons in the following week, then do a short final push one to three days before with one clear ask in every post.
How do I get employees to post about our event?
Make it easy and personal. The skill writes several employee variants with different first lines and a personal reason to say hi, plus a five-point how-to. Ask people to edit the opening in their own words, and give each group its own tracking link so you can see what worked.
What goes in a speaker promo kit?
A first-person post the speaker can share with session title, date, time and a tracked link, a short version for busy speakers, and suggested hashtags and mentions. The skill writes one per speaker or a template you can fill, and pairs well with a share card image.
How do I write a good event recap post?
Lead with one useful takeaway instead of 'what a week', add two or three things you heard, thank speakers and partners, and end with a next step like a replay or template. Only use numbers you can share, and get permission before naming attendees or customers.