The pinned FAQ post for show day. Doors, parking, age, re-entry, merch, photo policy, lost and found, all in one scannable post the moderator can pin to the top of socials.
How to use it
Copy the SKILL.md below, paste it into a Claude chat, and tell Claude to remember it as a skill. Claude will save it and pull it in the next time you ask for a show-day pinned post.
To make it match your venue, tell Claude the details it doesn't know yet: your venue name, your room layout, your standard policies (age, re-entry, bag, camera, phone), your accessibility process, anything your team does differently. Then ask Claude to update the skill with that information. The file will be tuned to how your venue actually operates, without you ever opening a code editor.
Works best with: install the venue-voice-profile-builder first. This skill checks for the profile it produces and writes in your venue's voice when it finds one. Without it, Claude falls back to a generic event-marketing voice.
Once it's saved, trigger it by telling Claude "use the show-day FAQ pinned post skill" and pasting the show details, your policies, and which channel you want it formatted for (Instagram, X, Facebook, or all three). Do not use it for the logistics email, the recap, or individual reply templates. Those have their own skills.
---
name: show-day-faq-pinned-post
description: Draft the pinned FAQ post that goes on the venue's socials the morning of a show, covering doors, parking, age policy, re-entry, merch, photo and phone policy, will-call, and lost and found. Trigger whenever an operator says "write the show-day pinned post", "draft the FAQ for tonight", "the [artist] show is tonight, what's the pinned", or asks for a single post that holds every show-day answer the comments section is about to ask. Also trigger when the operator asks for a "day-of social", "show-day info post", or pastes a list of doors and policies and wants it formatted for Instagram, X, or Facebook. This skill is the social post version of the show-day brain dump. Distinct from the email logistics send (use `before-you-go-logistics-email`) and from the recap (use `post-show-recap-email`).
---
# Show-day FAQ pinned post
## What this skill does
This skill drafts the single post the venue pins to the top of its socials the morning of a show. The post is the answer to every question that will hit DMs and comments between now and doors. Done right, it cuts the moderator's workload in half and gives ticketholders a place to send their friends.
The post is informational. It is not the announce. It is not a sales push. It is the host's clipboard handed to the room.
## When to trigger
Trigger when an operator says the show is today and they need the pinned post for socials. Trigger on "show-day pinned", "day-of FAQ post", "tonight's pinned", "Instagram pinned for the [artist] show", "show-day info post", or any request that implies the venue needs one consolidated post the audience can scroll to for answers.
Do not trigger for the logistics email (use before-you-go-logistics-email), the recap (use post-show-recap-email), or for individual reply templates to specific DM questions. This skill is the one big pinned post, not the reply stack.
## Required inputs
Ask for these in one message if anything is missing.
Artist name and show date, and the venue or room.
Doors time. Required.
Set times if available. Support and headliner. If only doors is locked, draft with doors only and note that set times will be added.
Age policy. All-ages, 18+, 19+, 21+. Include the ID requirement explicitly.
Re-entry policy. Yes, no, or with conditions (such as bracelet only, restricted hours).
Parking and transit. The closest lot, the nearest transit stop, the rideshare drop-off point. If the operator does not have these and the venue has a directions page, link to it.
Will-call and ticket delivery. Mobile only, print accepted, ID requirement.
Bag and camera policy. Bag size if limited. Camera policy (phones only, no detachable lenses, no professional cameras).
Photo and phone policy on the floor. Some artists ban phones. If so, name the policy and how the venue is enforcing it (Yondr pouches, signage, staff reminders).
Merch table hours. Open at doors, open between sets, sold out only on socials, etc.
Lost and found. How to ask, where to email or DM.
Accessibility. ASL request process, accessible entry, accessible viewing platform, hearing assistance.
Anything venue-specific worth pinning: coat check, food and drink, ATM availability, weather note for outdoor shows.
Channel. Instagram, X, Facebook, or all three. The structure is the same but Instagram captions can carry more length, X needs the most aggressive trimming, Facebook tolerates the longest format.
## Voice
Read the venue voice profile if one exists. The pinned post should sound like the same venue that wrote the logistics email and the announce. The reader recognizes the voice from the rest of the venue's content.
Default Backstage operator voice if no profile exists: practical, host-like, warm but not chatty. The post should read like the venue answering questions, not a corporate FAQ template.
Hard voice rules:
No em-dashes. Use commas, semicolons, or periods.
No fragment chains. The labeled list is terse by nature; the prose around it should use complete sentences with rhythm.
No hype. The show is hours away. The post's job is logistics, not a second announce.
No apology language for venue policies. "Sorry, no re-entry" is not the framing. "Re-entry: not allowed" is.
No hashtags unless the venue voice profile uses them. Pinned posts on most venues do not need hashtags. If the profile uses them, follow the profile.
## Structure
Always draft in this order. Adjust length per channel but keep the order.
Opener. One to two sentences. Confirm the show is tonight, name the artist, and give one warm line of welcome. No hype.
The labeled list. The core of the post. Format:
```
Doors: [time]
Show: [support] / [headliner] (if known)
Age: [policy + ID requirement]
Re-entry: [policy]
Parking: [closest lot and street note]
Transit: [closest stop, last train if relevant]
Will-call: [process and ID requirement]
Bags: [policy]
Cameras: [policy]
Phones on the floor: [policy]
Merch: [hours]
Accessibility: [ASL request, accessible entry, etc.]
Lost and found: [where to email or DM]
```
Include only the lines that apply to this venue and this show. Do not include a line that the operator did not give you information for. A missing line is better than a guessed line.
One practical tip. One sentence, optional. Something the venue would tell a friend, only if the operator gave you something to put there. The line of merch is shortest after the support set. Cash-only at the bar. The closest transit stop runs late tonight. If the operator did not give you a tip, skip the section.
Close. One sentence. A clean sign-off that points the reader at the next action: see you at doors, save this post, drop questions in the comments. Keep it short.
## Length caps by channel
Instagram caption: 220 to 280 words total. The labeled list is the bulk; the opener and close are tight.
X post: 250 to 280 characters for the lead post, with the labeled list either as a single threaded reply or as an image. If asked for the thread version, draft a three-tweet thread: opener, list, close.
Facebook: 250 to 350 words allowed. Same structure as Instagram.
## Common failure modes to avoid
Drafting the post without confirming policies. Re-entry, age, and phone policies vary by show. Do not assume any of them carry over from the last show.
Burying doors time. Doors is the first labeled line. It is the question the room asks most.
Padding the opener. "We are so excited to welcome [Artist] to [Venue] tonight" is filler. The room knows. Open clean.
Including hype CTAs. "Tickets are running low, grab them now" does not belong in the show-day pinned. The show is tonight. The CTA is logistics, not sales.
Apologizing for policies. The policies are the policies. State them.
Treating photo or phone policy as optional. If the artist has a phone policy, this is the post where it is communicated. The reader needs to know before they walk through the door, not at the door.
Inventing accessibility info. If the operator did not give you ASL or accessible entry details, do not write them. Accessibility errors lose trust fast.
## What to deliver
Return:
The pinned post, ready to paste, in the structure above.
If the operator asked for multiple channels, return one version per channel with the channel labeled.
A short note at the end naming any policy lines the operator did not provide that you would want to confirm before posting. Two or three sentences. Do not walk through every formatting choice.
.svg "backstage logo 1 (3)")
