From event-marketing
INTERNAL skill — invoked by the venue-research skill (in this plugin) when an event is an experience rather than a fixed-location venue, OR invoked manually by the user with /experience-research. Sources VIP experiences from hospitality programs, suite brokers, motorsports/F1 corporate hospitality, golf-with-a-pro programs, Sphere, helicopter operators, museum buyouts, celebrity-led experiences, luxury weekend retreats, and novel curated experiences. DO NOT auto-trigger from general user messages about events, venues, dinners, happy hours, workshops, or conferences — venue-research is the entry point and will delegate here when appropriate. Only trigger when (a) called via the Skill tool by venue-research, or (b) the user explicitly references this skill by name or types /experience-research.
How this skill is triggered — by the user, by Claude, or both
Slash command
/event-marketing:experience-researchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill is **not** a general-purpose entry point. It is invoked in two ways:
This skill is not a general-purpose entry point. It is invoked in two ways:
venue-research — after that skill collects intake (budget, persona, event goals, expected turnout, location) and determines the request is for an experience, not a fixed-location venue. The intake is passed in via args./experience-research or explicitly references this skill.When invoked directly (case 2) without intake context, gather the same five inputs first (Step 1 below). When delegated from venue-research (case 1), the inputs are already in the conversation — skip the intake step and use them.
Required:
anywhere (valid for experiences not tied to a city)If anything is missing, ask for all missing items in a single message.
The persona research file lives at a user-level path so it persists across projects and survives plugin updates:
Path: ~/.claude/event-marketing/audience-research.md
Always reference this exact path. Never write to a copy inside the plugin folder — the plugin is git-distributed and any writes there will be lost.
mkdir -p ~/.claude/event-marketing) and seed the file with the template that venue-research defines (see its "Audience research file template" section). Then proceed as if empty.Last researched is within ~6 months, use the existing entry.lu.ma/discover), Eventbrite, and LinkedIn (search competitor companies + "hosted" / "thank you to everyone who joined us at"). Append findings using the entry template.Two parallel jobs:
Most briefs need both. Even when the user names a specific experience, add 1–2 novel options they can react to.
Suite hospitality (any team, any venue):
Premium ticketing:
Event-specific official hospitality programs (better inventory + on-site treatment than third-party):
Motorsports / Velocity Invitational tier (go to the event's own "Corporate Hospitality" page):
Golf with a pro:
Sphere (Las Vegas):
Aviation / scenic:
Museum after-dark / cultural buyouts:
Celebrity-led dinners / fireside chats / surprise appearances:
Luxury weekend retreats:
Pattern-match across these for unexpected ideas:
"hosted" / "thank you to everyone who joined us at" / "had a great time at". Shows the bar competitors are setting.Always check these for the user's vertical. These differentiate because competitors can't easily copy live:
Aim for 8–15 options mixing:
For each, capture: experience name, vendor/provider, location, format (suite vs. buyout vs. private session vs. retreat), rough capacity, rough price tier.
Experiences mostly lack Google Maps review pools, so filter on:
"thank you" / "had a great time"Before finalizing, for each candidate:
Rank for fit, not for prestige. A perfectly-matched mid-tier experience beats an over-the-top one that signals "we're trying too hard".
Markdown report in chat. Don't write a file unless asked.
# Experience shortlist: <event> — <city or "various">
**Brief:** <one-line restatement: format, persona, headcount, budget, location, goal>
---
## 1. <Experience Name> — <Vendor / Provider, Location>
**Why it fits:** <1–2 sentences tying to persona + goal>
**Format:** <suite | buyout | private session | retreat | hospitality package>
**Capacity:** <X guests>
**Estimated price:** <$X–Y per head | $Z total> — *confirm directly*
**Notable features:**
- <signature element>
- <on-site treatment / hospitality detail>
- <photo / story moment>
- <logistics: travel, lodging, dietary handling>
**Booking:** <vendor link / contact path>
**Caveats:** <lead time, blackout dates, contract minimums, weather risk, etc.>
## 2. <Experience Name> — ...
[same structure]
[5–8 total — mix of user-named + novel discoveries]
---
## How to proceed
**Top picks:** <top 1–2 with one sentence each on why>
**Confirm via direct outreach:** exact capacity, pricing, date availability, lead time, dietary, travel/lodging block
**Logistics flags:** lead time on premium hospitality (often 3–6 months for F1/Masters), weather risk, blackout dates, deposit and cancellation terms
npx claudepluginhub zuddl/claude-plugin-event-marketingCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.