samber/dev-event-organizer-skills / skills/business-event-formats
business-event-formats
VerifiedChoose which company-run event shape to run - invite-only dinner, executive summit, single-city user conference, multi-city roadshow, or a floor-primary trade-show event - plus how its program is sourced and what shape its floor takes. Also owns the business-oriented activity layer any conference can run beside its program for sponsors (hiring corner, hands-on product feedback session, opt-in demo space, matchmaking). Use whenever a company weighs a user conference against a roadshow or a summit, asks what kind of event to put on for developers, customers or partners, or asks whether to run its own floor or exhibit on someone else's, or an organizer asks what to offer sponsors beyond talks, even if they only say "we want to do an event". Format catalog only. Do NOT use for track count or session mix - use samber/dev-event-organizer-skills@event-format-selection; for floor operations use samber/dev-event-organizer-skills@event-booth-experience; for goals and budget use samber/dev-event-organizer-skills@corporate-event-strategy.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 30.3 KB |
| evals/evals.json | config | 28.3 KB |
| references/company-run-format-catalog.md | markdown | 8.8 KB |
| references/ranking-dominance-analysis.md | markdown | 3.9 KB |
| references/vendor-conference-precedents.md | markdown | 5.8 KB |
evals/evals.json
View on GitHub{
"skill_name": "business-event-formats",
"evals": [
{
"id": 1,
"prompt": "I run marketing at Fenlow, a data-pipeline observability platform (~$40k ACV, sales-led). Leadership approved one flagship event investment for next year. Our CRO keeps talking about the 14 strategic accounts we need to crack, but my team wants maximum visibility in the ecosystem - honestly a big expo-style event with partners exhibiting sounds the most exciting. We have about 3,000 people on our newsletter and we've never run an event. What should we run?",
"expected_output": "An interview-driven shape brief that surfaces the volume-versus-named-accounts conflict before ranking anything, refuses to pick the expo on visibility alone, presents 2-3 candidate shapes with one recommendation and flip conditions, and routes goals, funding and internal structure to sibling decisions without inventing any figures.",
"files": [],
"expectations": [
"Establishes whether the goal is volume of qualified conversations or penetration of the 14-account list before ranking or recommending any shape, by asking the question or explicitly surfacing the conflict between the CRO and the marketing team",
"States that reach and account depth order the event shapes in exactly opposite ways, so the choice between those two axes decides the ranking",
"Does not recommend the expo or floor-primary shape on the strength of visibility or reach alone",
"States that the floor-primary shape is top of reach but bottom of account depth, so neither efficiency ordering ever selects it",
"Names the floor-primary promotion condition as the combination of having no audience that will travel and the ecosystem rather than the product being the year's story",
"Ties the shape candidates to the chosen axis: dinner or roundtable and executive summit lead if the named-account axis wins, roadshow or single-city conference lead if volume wins, rather than one generic pick",
"Asks for evidence that an audience would travel (customer base, mailable list, past registrations) rather than impressions before proposing a single-city conference",
"Presents 2-3 candidate shapes with trade-offs and exactly one recommendation",
"Names, for each choice made, the interview answer that would flip it next year",
"Routes goal mix, funding ownership and success measurement to a separate corporate event strategy decision rather than fixing goals or KPIs itself",
"Contains no invented headcount, city count, agenda length, ticket price or budget figure",
"Offers the deliverable for validation section by section rather than delivering one final block"
]
},
{
"id": 2,
"prompt": "I'm head of growth at Corvassa, a compliance-automation SaaS. Budget is tight so we're planning a series of intimate invite-only dinners in Chicago and Austin next quarter - low cost, low risk, no venue contracts to sign. We don't have specific accounts picked out; the idea is to fill about ten seats per city with whatever fintech ops leaders we can pull from LinkedIn outreach and see what pipeline shakes out. Sound like a plan?",
"expected_output": "A response that removes the dinner from the menu because no named account list exists, corrects the low-risk framing by naming hospitality compliance as the dinner's top exposure, and redirects the volume goal to a shape that serves it.",
"files": [],
"expectations": [
"Advises against the dinner series because no named account list exists",
"States that without named invitees the dinner degrades into a generic mixer that buys neither reach nor account depth",
"Removes the dinner from the menu entirely rather than keeping it as a low-ranked or fallback option",
"Rejects the framing that the dinners are low risk because they are small and involve no venue contracts",
"Places the dinner or roundtable at the top of the compliance ordering among event shapes",
"Names the guest's own employer's gift, hospitality or anti-bribery policy as where hosted hospitality for a named guest lands",
"States that an accepted invitation cannot be quietly withdrawn",
"Recommends a shape matched to a volume goal, such as a multi-city roadshow or single-city conference, instead of the dinners",
"Asks what evidence exists that an audience would travel, or what audience assets exist, before choosing between the volume shapes",
"Names the condition that would bring the dinner back onto the menu: a real named account list",
"Adds no invented headcount, seat count, budget or price figures of its own"
]
},
{
"id": 3,
"prompt": "Ops lead at Merrow, a CI/CD platform. We've committed to a roadshow: my draft plan has 12 cities across the US and Europe, and each city gets a custom agenda built around local case studies and region-specific integrations, since audiences differ. Two asks: sanity-check whether 12 cities is the right number, and help me design each city's agenda - how many talks and which formats. Also, leadership hopes this becomes our flagship annual thing.",
"expected_output": "A response that refuses to bless a city count and installs a per-city stop rule instead, warns that bespoke per-city content destroys the roadshow's reuse economics, routes agenda design to the format-selection sibling, and redirects the annual-flagship ambition to the single-city conference shape.",
"files": [],
"expectations": [
"Declines to validate 12 cities or to supply any specific right number of cities",
"Prescribes fixing a per-city stop rule before the first city: what a stop must return for the next one to run",
"States that the stop rule set in advance is the only defence, because the marginal-city question has no general answer",
"Routes the per-city economics and payback question to the goals-and-budget decision rather than guessing a count",
"Warns that bespoke per-city content forfeits the roadshow's core advantage",
"Names the reuse structure: later stops reuse one deck, one crew and one run-of-show while the first stop absorbs the setup",
"Distinguishes a roadshow (one program re-run across places) from a conference series (different programs across time)",
"Declines to design per-city agendas, talk counts or session formats, and routes internal program structure to the format-selection sibling",
"States that a roadshow does not become an owned annual property: it has stops, not editions",
"Identifies the single-city user conference as the only shape that becomes an owned annual property, and ties the flagship ambition to it",
"Notes that the compounding-annual-property answer can promote the single-city conference past the roadshow even though the roadshow leads reach per unit effort",
"Flags the per-jurisdiction registration-data and marketing-consent review triggered by stops across the US and Europe"
]
},
{
"id": 4,
"prompt": "CEO of Trellick here - we make an open-source feature-flag platform, adoption is bottom-up: engineers adopt the free tier, then teams convert. A board member pointed at how well a competitor's Executive Innovation Summit works, and honestly AWS re:Invent proves big vendor events print money. I want a VP-and-above summit in Lisbon in May where we'll also publicly announce our v2 platform. My question is mostly about guest list mechanics - or would an executive roundtable be simpler?",
"expected_output": "A response that challenges the summit for a developer-led product because the seniority gate excludes the actual adopters, refuses to import the competitor's or AWS's shape without their constraints, flags that a summit cannot carry a public launch, distinguishes summit from roundtable by list assembly, and offers a developer-compatible alternative.",
"files": [],
"expectations": [
"Warns that a seniority-gated guest list excludes the engineers who actually drive adoption under a bottom-up, developer-led motion",
"Identifies that inverted buying hierarchy as the main reason executive summits underperform when copied to developer products",
"Challenges copying the competitor's or AWS's shape: their audience, launch cadence and installed base do not transfer, so import the reasoning rather than the format",
"States that a summit cannot carry a public launch, so the v2 announcement needs a different shape or channel",
"States that a summit cannot serve an audience that evaluates products hands-on",
"Distinguishes a summit from a roundtable by how the list is built - assembled through nomination or application versus invitees personally known to the company - not by seniority or size",
"Notes that a summit needs runway that a roundtable does not",
"Names the summit's live risk as compliance from hosted hospitality, not budget",
"Establishes who the intended attendee is, or whether the goal is named-account depth versus volume, before endorsing any shape",
"Does not use any named company's attendance or scale figures to size the proposal",
"Offers at least one alternative shape consistent with a developer audience and the fixed launch, with its trade-off stated",
"Routes why the event is run, who funds it and how it is measured to a separate strategy decision rather than fixing them here"
]
},
{
"id": 5,
"prompt": "I'm the events lead at Quenholt, a B2B data-catalog vendor. We're running our first-ever user conference in Denver this fall, and it's explicitly a one-year experiment - if it doesn't produce pipeline we won't repeat it. To make it credible with data engineers I want a fully open CFP. One wrinkle: our CPO and three VPs have each already claimed keynotes, and I can't realistically push back on them. Also, how should we later tell whether the program approach worked?",
"expected_output": "A response that talks the user out of the open CFP because both promotion conditions fail, recommends the mixed practitioner program with labelled company slots, sets the company-slot drift count as the measurement gate, and routes claim entitlement and session formatting to the sibling decisions.",
"files": [],
"expectations": [
"Advises against the fully open CFP for this edition",
"Names both promotion conditions for open submissions: a compounding annual property and the political capital to tell an executive their slot did not make the program",
"States the collapse failure: without that political capital the open posture becomes a company-supplied program with extra administration, the worst outcome on the menu",
"Recommends the mixed practitioner program with labelled company slots as the default posture",
"Requires the company slots to be labelled as company content rather than dressed as neutral sessions",
"States the credibility ordering across postures: open submissions above mixed labelled above customer-story above company-supplied",
"Notes that open submissions also tops the effort ordering, citing the review cycle and the cost of refusing internal speakers",
"Does not justify a posture on cheapest-first or message-control-per-effort grounds",
"Sets the measurement gate as counting company slots on the final program against the planned number, watching for drift",
"Routes what the chosen posture entitles the event to claim about itself to the positioning decision rather than declaring the event neutral or community-run",
"Routes session formats and track structure to the format-selection sibling rather than designing the agenda"
]
},
{
"id": 6,
"prompt": "Marketing director at Ostrave Logistics Tech. Our annual customer day has always been our own people walking through the roadmap - customers love it. This year the CEO wants to open registration to prospects and rebrand it 'FreightStack Forum - the independent gathering for supply-chain developers'. We do have a customer advisory board that meets quarterly, if that helps. Can you help me plan the agenda mix?",
"expected_output": "A response that deletes the all-internal program once prospects are marketed to, shows the independence claim fails against the single-vendor-content threshold owned by the positioning sibling, concludes the program or the marketing must change, and promotes the customer-story program on the strength of the existing advisory board.",
"files": [],
"expectations": [
"Flags that marketing the event to people who are not customers yet changes what the program may honestly consist of",
"Deletes the all-internal, company-supplied program from the menu for this edition rather than merely ranking it low",
"States that a company-supplied program remains legitimate for the customers-only roadmap day it used to be",
"States that the 'independent gathering' claim is forfeit when single-vendor content dominates, citing the roughly 30-40% single-vendor-content share threshold",
"Attributes that threshold to the positioning sibling and labels it a reasoned default, not an industry standard",
"Concludes that either the program or the prospect-facing marketing must change - the two cannot both stay as-is",
"Recommends the customer-story program and explicitly promotes it because the customer advisory board already meets",
"Warns of the customer-story program's hidden cost: reference approval and legal sign-off per customer",
"Offers the mixed practitioner program with labelled company slots as another compliant candidate",
"Does not invent an alternative neutrality threshold or re-derive the positioning analysis instead of citing it",
"Routes final agenda mechanics such as session formats and track structure to the format-selection sibling"
]
},
{
"id": 7,
"prompt": "Halvern Robotics - we sell a fleet-orchestration SDK. This year the leadership story is entirely about our partner ecosystem: 30+ integration partners, and we want the market to see them building on us. Problem: we have no event audience of our own - no past event, tiny newsletter, and customers spread worldwide who told us outright they won't fly for us. So: do we build our own partner expo, or take a large stand at RoboLogistics Expo, the industry show with about 20k attendees? If the stand: give me booth layout and staffing recommendations. And how would we judge success either way?",
"expected_output": "A floor-shape decision that works the tension between ecosystem visibility and the missing audience, presents own-floor versus third-party stand with one recommendation, refuses booth layout advice for exhibiting on someone else's floor while stating why support ends there, routes own-floor physical questions to the floor-operations sibling, and sets returning exhibitors as the own-floor success gate.",
"files": [],
"expectations": [
"Recognizes that both floor-primary promotion conditions hold - no audience that will travel and the ecosystem as the year's story - so the floor-primary family is legitimately in play",
"States the floor-shape trade-off: an own floor buys ecosystem visibility while only the third-party rung borrows an audience someone else assembled",
"Notes that an own floor fills its own room and borrows no attendees, which the company's missing audience makes the central risk",
"Presents the own showcase floor and the third-party stand as candidates with trade-offs and makes exactly one recommendation",
"When discussing the own-floor options, names the own showcase floor as the cheapest buy of partner visibility or the program-plus-floor promotion condition as the ecosystem being what is sold this year",
"Declines to give booth layout and staffing recommendations for exhibiting at the third-party show",
"States the reason for declining: the floor-operations sibling serves the organizer who owns the hall, not a company exhibiting on someone else's floor, so support ends at naming the shape",
"States that limit explicitly instead of improvising generic booth tips",
"For an own floor, routes layout, tier specs, setup windows, staffing and traffic to the floor-operations sibling instead of answering them inline",
"Sets the own-floor success gate as exhibitors who return, not attendee walk-past traffic",
"States that attendee traffic reads on the floor's operation, which is the floor-operations sibling's outcome, not on the shape choice",
"Adds no invented attendee counts, exhibitor counts or booth prices of its own"
]
},
{
"id": 8,
"prompt": "I'm one of the volunteer organizers of PolyglotPy, a community-run Python conference in Porto - nonprofit, about 15 volunteers, no company behind us. We're rethinking our corporate event format for next year: should we become a roadshow across three Iberian cities, or go upmarket with an executive summit for engineering leaders? Sponsors also keep asking us for more.",
"expected_output": "A response that identifies the organizer as community-run, routes the shape question to the community-pole format skill instead of applying the company-run ladder, declines to recommend the summit or roadshow from this catalog, and keeps sponsor appetite out of the shape decision.",
"files": [],
"expectations": [
"Identifies the event as community-run, not company-run",
"Routes the shape question to the community-pole format-selection skill instead of answering from the company-run catalog",
"Stops rather than applying the company-run shape ladder: delivers no roadshow-versus-summit recommendation from this catalog",
"Does not recommend the executive summit for the community conference",
"Uses the pole names company-run and community-run while addressing what the user called corporate, mirroring the meaning rather than the label",
"Explains why the routing happens: the shape ladder here serves companies choosing a company-run event",
"Does not let sponsor appetite drive the shape choice, noting sponsor offerings are priced and delivered against a chosen shape rather than being a reason to pick one"
]
}
],
"trigger_queries": [
{ "query": "Should we run a user conference or a multi-city roadshow next year?", "should_trigger": true },
{ "query": "What kind of event should we put on for our developer customers?", "should_trigger": true },
{ "query": "We have 15 target accounts to crack this year - what kind of event actually moves them?", "should_trigger": true },
{ "query": "Marketing wants a big annual conference but sales wants executive dinners. Who's right?", "should_trigger": true },
{ "query": "Is an executive summit the right move for our API platform?", "should_trigger": true },
{ "query": "Should we run our own expo floor for partners or just take a big booth at the industry trade show?", "should_trigger": true },
{ "query": "We're a Series B SaaS - is it too early to launch our own flagship customer conference?", "should_trigger": true },
{ "query": "Thinking about a multi-city tour to demo the product to prospects - good idea?", "should_trigger": true },
{ "query": "Our CEO wants us to have our own re:Invent. Talk me into it or out of it.", "should_trigger": true },
{ "query": "Invite-only dinner versus executive summit for our enterprise prospects - which one?", "should_trigger": true },
{ "query": "What's the difference between a roadshow and just running our conference in three cities?", "should_trigger": true },
{ "query": "We're launching v3 next spring and want an event to carry the announcement - what shape of event can do that?", "should_trigger": true },
{ "query": "Should our vendor conference run an open call for papers or keep the agenda in-house?", "should_trigger": true },
{ "query": "Our conference agenda is 100% our own product managers - is that a problem if prospects attend?", "should_trigger": true },
{ "query": "How do we decide between hosting a partner expo ourselves and exhibiting at someone else's?", "should_trigger": true },
{ "query": "We're debating a customer dinner series versus a proper summit for our top accounts.", "should_trigger": true },
{ "query": "What event format gets us in front of developers who have never heard of us?", "should_trigger": true },
{ "query": "Planning our first vendor conference - walk me through the options.", "should_trigger": true },
{ "query": "Do trade-show style events still make sense for a devtools company?", "should_trigger": true },
{ "query": "We want to do an event for our customers this year. Where do we even start?", "should_trigger": true },
{ "query": "Which is more effective: ten small city events or one big annual conference?", "should_trigger": true },
{ "query": "Should our event be customers-only or open to prospects, and does that change what the agenda can be?", "should_trigger": true },
{ "query": "Executive roundtable or dinner for our top eight accounts - and what's actually the difference?", "should_trigger": true },
{ "query": "We got budget approved for one big event play this year. How do we choose what to run?", "should_trigger": true },
{ "query": "Our partner ecosystem wants more visibility - should we build an event around them?", "should_trigger": true },
{ "query": "Is a roadshow cheaper than a conference for the same reach?", "should_trigger": true },
{ "query": "What kind of event works when our buyers won't travel to us?", "should_trigger": true },
{ "query": "Every VP here wants a keynote at our conference - how should we actually source the program?", "should_trigger": true },
{ "query": "Should we put customers on stage at our conference or keep control of the message ourselves?", "should_trigger": true },
{ "query": "B2B SaaS here - dinner series or summit for our ABM account list?", "should_trigger": true },
{ "query": "What's the right kind of event to move 20 named enterprise accounts?", "should_trigger": true },
{ "query": "Our field marketing team already runs city events - does that change what our big annual event should be?", "should_trigger": true },
{ "query": "How risky is hosting an invite-only dinner for prospects, really?", "should_trigger": true },
{ "query": "We sell infra software. Own conference, roadshow, or a huge booth at the big industry shows?", "should_trigger": true },
{ "query": "Choosing between an intimate executive event and something with real reach - how do we think about it?", "should_trigger": true },
{ "query": "Flagship user conference or several smaller regional stops - how do we pick?", "should_trigger": true },
{ "query": "What event shape becomes an annual property we actually own?", "should_trigger": true },
{ "query": "Should the expo floor be the main event or an add-on to the talks at our company event?", "should_trigger": true },
{ "query": "Our exec team saw a competitor's summit and wants one of our own - is it right for us?", "should_trigger": true },
{ "query": "How many of our own talks can we put on our conference program before it stops being credible?", "should_trigger": true },
{ "query": "Requesting a recommendation on the appropriate corporate event format for our FY27 developer engagement program.", "should_trigger": true },
{ "query": "Do existing customers and prospects need different events, or one event with two audiences?", "should_trigger": true },
{ "query": "We've outgrown webinars - what in-person format should we graduate to for our user base?", "should_trigger": true },
{ "query": "How many tracks should our conference have?", "should_trigger": false },
{ "query": "Should our conference be single-track or multi-track?", "should_trigger": false },
{ "query": "What mix of session formats should we run - talks, workshops, open spaces, panels?", "should_trigger": false },
{ "query": "Should our community meetup graduate into a hackathon or an unconference day?", "should_trigger": false },
{ "query": "How should we lay out the expo hall so foot traffic reaches every booth?", "should_trigger": false },
{ "query": "What physical specs does a Gold-tier booth get - table size, power, signage height?", "should_trigger": false },
{ "query": "Draft the setup and teardown schedule for our expo floor.", "should_trigger": false },
{ "query": "What should our user conference be funded to accomplish, and whose budget pays for it?", "should_trigger": false },
{ "query": "Which KPIs prove our developer conference was worth the spend?", "should_trigger": false },
{ "query": "Can we call our vendor conference 'community-run' in the marketing?", "should_trigger": false },
{ "query": "Write a positioning statement for our conference against the big industry show.", "should_trigger": false },
{ "query": "Should we add a second event property alongside our flagship conference, or would it cannibalize?", "should_trigger": false },
{ "query": "How much should tickets cost for our user conference?", "should_trigger": false },
{ "query": "What should we charge sponsors for the Gold tier at our event?", "should_trigger": false },
{ "query": "Draft the sponsor prospectus for our summit.", "should_trigger": false },
{ "query": "How do we find and contract a venue for a three-day conference?", "should_trigger": false },
{ "query": "Plan travel, hotels and guest care for the VIPs we invited to our summit.", "should_trigger": false },
{ "query": "How do we run our CFP review process fairly?", "should_trigger": false },
{ "query": "Build the run of show for day one of our conference.", "should_trigger": false },
{ "query": "Is there actual market demand for a Rust conference in our region?", "should_trigger": false },
{ "query": "How do we stream our conference talks to a remote audience without losing the room?", "should_trigger": false },
{ "query": "What's the marketing plan to sell out our user conference?", "should_trigger": false },
{ "query": "Help me schedule sessions so the popular talks don't clash.", "should_trigger": false },
{ "query": "How should we structure hackathon judging and the demo format?", "should_trigger": false },
{ "query": "What goes into the sponsor agreement for our expo exhibitors?", "should_trigger": false },
{ "query": "Pick a date for our conference that avoids the big industry shows.", "should_trigger": false },
{ "query": "How do we get press to cover our launch event?", "should_trigger": false },
{ "query": "Design the attendee email sequence from registration through day-of logistics.", "should_trigger": false },
{ "query": "It's our first edition - what does the planning timeline look like month by month?", "should_trigger": false },
{ "query": "Should we cross-promote with another organizer's meetup series, and what do we swap?", "should_trigger": false },
{ "query": "How do we measure booth traffic and get attendees moving across the expo floor?", "should_trigger": false },
{ "query": "What swag and demo setup should our booth run at the trade show next month?", "should_trigger": false },
{ "query": "How many volunteers do we need and how do we staff the registration desk?", "should_trigger": false },
{ "query": "What's a fair cash prize structure for our hackathon?", "should_trigger": false },
{ "query": "Plan the after-party and evening social program for our conference.", "should_trigger": false },
{ "query": "How do we handle no-shows at our free community meetup?", "should_trigger": false },
{ "query": "Should our conference talks be recorded and repurposed into a video series?", "should_trigger": false },
{ "query": "Help me write the code of conduct for our event.", "should_trigger": false },
{ "query": "How do we win sponsors for our community conference?", "should_trigger": false },
{ "query": "What roles do we need to hire to build an events team?", "should_trigger": false },
{ "query": "What's the best format for our quarterly company all-hands offsite?", "should_trigger": false },
{ "query": "Design the event store and projection schema for our order service.", "should_trigger": false },
{ "query": "Set up a recurring calendar event series for our team's release rituals.", "should_trigger": false }
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |