Post-show social pack by Hive Backstage
Four post-show social captions covering crowd, artist, the moment, and the next show, built from real setlist and crowd notes so each caption has its own anchor instead of restating the same recap four ways.
What this skill does
Produces four distinct social captions from a single show, each anchored on a different angle so the venue gets four posts that work without repeating themselves. The recap email goes to the list. The social pack lives on the venue's feed, where the audience scrolls and the captions compete with everything else on the platform. The angles are crowd, artist, the moment, and the next show. If two captions feel interchangeable, the pack has failed.
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 post-show social pack.
To make it match your venue, tell Claude the details it doesn't know yet: your venue name, your standard channel mix (Instagram, X, Facebook), whether you use hashtags, your posting cadence, anything your team does differently. Then ask Claude to update the skill with that information. The file will be tuned to how you actually post, without you ever opening a code editor.
Works best with: install the venue-voice-profile-builder first. Social captions are voice-sensitive because they are the venue's public face the morning after the show. The skill checks for the profile 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 post-show social pack skill" and pasting the setlist, two or three real moments from the night, and the next show on your calendar. Do not use it for the recap email, the longer recap blog, or the show-day pinned post. Those have their own skills.
--- name: post-show-social-pack description: Draft four post-show social captions covering crowd, artist, the moment, and the next show, built from real setlist and crowd notes from the night so each caption has its own anchor rather than restating the same recap four ways. Trigger whenever an operator says "write the post-show socials", "draft the recap captions", "the [artist] show was last night, write the social pack", "Instagram captions from the show", or pastes setlist notes, crowd observations, or photos from the night and asks for captions. Also trigger when the operator wants a multi-post social pack for Instagram, X, Facebook, or all three. This is the social side of the post-show cycle. Distinct from the recap email (use `post-show-recap-email`) and the longer-form recap blog (use `recap-blog-opener`). --- # Post-show social pack ## What this skill does This skill produces four distinct social captions from a single show, each anchored on a different angle so the venue gets four posts that work without repeating themselves. The recap email goes to the list. The social pack lives on the venue's feed, where the audience scrolls and the captions compete with everything else on the platform. Four captions is the right shape because it gives the venue enough material to space across 24 to 48 hours without exhausting the show. The angles are crowd, artist, the moment, and the next show. Each one is its own caption with its own anchor. If two captions feel interchangeable, the pack has failed. ## When to trigger Trigger when an operator wants social copy from a show that just happened. Trigger on "post-show socials", "recap captions", "Instagram captions for the [artist] show", "social pack from last night", or when they paste setlist or crowd notes and ask for captions. Do not trigger for the recap email (use post-show-recap-email), the longer recap blog (use recap-blog-opener), or for the show-day pinned post (use show-day-faq-pinned-post). This skill is the multi-post social pack only. ## Required inputs The pack is only as good as the inputs. Ask for these in one message before drafting. Artist name and show date. The setlist or at least two or three songs the operator wants referenced. Setlist context anchors the crowd-and-artist captions. Two or three real moments from the night. The same input the recap email needs. Examples of what counts: a song that hit, a guest, an unexpected cover, a stretch where the room locked in, the support's standout song, a line the artist said between songs, a moment with the crowd. Specifics are non-negotiable. The next show on the calendar with the ticket link. The fourth caption points there. Channel. Instagram, X, Facebook, or all three. Instagram is the default. The structure is the same per channel but the length and the hashtag use vary. Optional: photo or video selects the operator is posting with each caption. If they share what is in the photo, the caption can speak to the image rather than describe it generically. If the operator only gives you one moment and a setlist, ask once for a second moment. Four distinct captions are hard to write from a single anchor. ## Voice Read the venue voice profile if one exists. Social captions are voice-sensitive. They are the venue's public face the morning after the show. Default Backstage operator voice if no profile exists: warm, observational, in-the-room. Same baseline as the recap email. The captions read like the venue was there, because the venue was there. Hard voice rules: No em-dashes. Use commas, semicolons, or periods. No fragment chains. No fabricated specifics. If the operator did not say the room sang along to the final chorus, do not write that. The captions are tied to real moments only. No "what a night" openers. The single most predictable recap caption opener possible. Cut it. No generic gratitude captions. "Thank you [Artist] for an incredible show" is the AI-default. The captions thank by naming what specifically the artist did. No hashtag spam. Default to zero hashtags unless the venue voice profile uses them. If the profile uses hashtags, use the venue's standard set, not invented ones. ## The four angles Each caption is built on one angle. The angles are labeled so the operator can see which caption is doing which job. Crowd. The caption is about the room. The audience, the energy, the moment a song hit, the way the room responded to a specific song. Anchor: a moment the operator captured. Default visual: a wide shot of the audience or a shot of a singalong moment. Artist. The caption is about the performance. A specific song, a guitar tone, an arrangement choice, a moment of stage chatter, the way the artist closed the set. Anchor: the setlist plus an artist-specific moment. Default visual: a close-up of the artist. The moment. The caption is about a single specific thing that happened that no one expected. A guest sit-in, an unannounced cover, a story the artist told, a tour debut, a song dedicated to someone in the room. Anchor: the operator's note on the moment. Default visual: video clip if available, otherwise a still from that part of the set. Next show. The caption is about what is on the calendar. Tie loosely to the recap if possible, name the next show, link the ticket. Anchor: the next show's artist and date. Default visual: the next show's announce art or a photo from a previous show by the same artist. ## Output structure Always use this exact structure. The operator should be able to copy each caption straight to the platform. ``` # Social pack: [Artist] at [Venue], [Date] ## Caption 1: Crowd [Caption text] Suggested visual: [Wide audience shot, singalong clip, etc.] Notes: [Optional one-line note for the operator, e.g. "post this one first while the show is fresh"] ## Caption 2: Artist [Caption text] Suggested visual: [Close-up, performance shot, etc.] Notes: [Optional] ## Caption 3: The moment [Caption text] Suggested visual: [Video clip preferred, still acceptable] Notes: [Optional] ## Caption 4: Next show [Caption text] Suggested visual: [Next show announce art, throwback photo, etc.] Notes: [Optional] ## Posting cadence [Two to three sentences. Recommended order and spacing. Default: caption 1 the morning after, caption 2 that afternoon, caption 3 the next day, caption 4 the day after that.] ``` ## Length caps by channel Instagram caption: 100 to 220 words per caption. Captions can run long on Instagram and still convert. X post: 250 to 280 characters per caption. The structure compresses; the angle stays. Facebook: 100 to 200 words. Same shape as Instagram. If the operator did not specify a channel, default to Instagram and note that X and Facebook variants can be shortened from the same captions. ## Hard rules Anchor every caption. If a caption could be posted after any show by this venue, it is too generic. The anchor pulls from real notes. One angle per caption. Crowd captions do not pivot to "and see you at the next show". The next show has its own caption. Direct quotes go on their own line. If the operator gave you a line the artist said, set it on its own line with a clear attribution. Skip the hashtag stack. The default is no hashtags. The venue voice profile is the only override. The next-show caption is information, not a sales push. Same rule as the recap email's next-show paragraph. The link is the link; the hype is not the angle. If the operator gave you a quote from a fan in the room, the moment caption is a great place to use it. ## Common failure modes to avoid Four versions of the same recap. The most common failure pattern. The pack is four angles, not four rewrites. Generic crowd language. "The energy was unreal" is the failure phrase. The crowd caption names a moment in the crowd, not the brand of the energy. Treating the artist caption as a thank-you. "Thank you [Artist]" is filler. The artist caption is about what the artist did on stage. Inventing the moment. If the operator did not tell you about a guest or a cover, the moment caption draws from a real moment in the operator's notes. If the operator did not give you a moment, ask for one. Forcing the tie between captions and the next show. If the next show is unrelated, the tie reads as marketing. The next-show caption can stand alone. Hashtag stacks like #livemusic #concert #venue #[city]nightlife. The default is zero. Use only what the venue voice profile uses. ## What to deliver Return the four captions in the structure above, with the suggested visual and posting cadence. If the operator gave you only one moment and the moment caption is leaning on it heavily, name what is still thin in two or three sentences at the end. Specifically: which caption you would want a second anchor for and the single piece of show context that would tighten it. Do not walk through every word choice.
New to running Claude as part of your event marketing stack? Read how to use Claude as an event marketer first.
FEATURED TOOLS
Jump in and start experimenting
Project management
Lorem ipsum dolor sit amet ectetur adipiscing elit vel ut congue variuso.
Project management
Lorem ipsum dolor sit amet ectetur adipiscing elit vel ut congue variuso.
Project management
Lorem ipsum dolor sit amet ectetur adipiscing elit vel ut congue variuso.
© 2026 Hive. Experimental tools for live event marketers.
