event-booth-experience

Designs expo floor layouts, tier booth specs, and sponsor load-in schedules for technical events.

1|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-booth-experience-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-booth-experience
Source: https://github.com/samber/dev-event-organizer-skills/tree/main/skills/event-booth-experience
Command: npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-booth-experience-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Organizers of developer conferences and community events must turn vague sponsor promises like "floor presence, Gold" into concrete physical plans: where booths go, what each tier's booth includes, when sponsors load in and out, and how attendees get pulled past every booth. This Skill designs that entire expo floor once per edition, from the organizer's side. ## Core Features & Use Cases - Floor layout and traffic pattern selection: Chooses among circulation-path siting, racetrack loops, grid rows, tier zoning, and hub-and-spoke layouts with ranked effort, value, and compliance trade-offs. - Tier-to-spec catalog: Produces one row per sponsor tier covering footprint, furniture, position class, power, network, vertical limit, signage rule, and staffing. - Master setup and teardown schedule: Builds load-in and load-out windows as offsets from a fixed anchor, with shipping windows and request deadlines as published rows. - Traffic-driving mechanics: Designs passport cards, scavenger hunts, or organic-traffic strategies aimed at booths the layout cannot reach. - Use Case: An organizer with 12 sponsors and one hall asks where booths go and when sponsors load in; the Skill produces a floor brief with a marked-up plan, a filled spec catalog, and a schedule worked back from the print date. ## Quick Start Ask the Skill to lay out the sponsor booths for your conference, including what each tier's booth physically includes and when sponsors load in and out.

Frequently Asked Questions about event-booth-experience

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How should I lay out sponsor booths at a developer conference?

Site booths on the path attendees already take to food and hangout space so foot traffic naturally passes them. For dedicated halls, promote to a racetrack perimeter loop where no booth sits off a spur; never leave the floor unmapped for sponsors to pick spots on arrival.

What should a sponsor tier's booth spec include?

Each tier row needs eight fields: footprint, furniture, position class, power, network, vertical limit, signage rule, and staffing. The vertical limit and signage rule are the two rows organizers most often skip and regret.

When should sponsor load-in and teardown happen?

Write the schedule as offsets from a fixed anchor such as registration opening, with a published default of one shared window an hour before doors. Teardown never starts before the last session ends, and request deadlines appear as schedule rows.

Does this Skill handle per-sponsor day-of execution?

No. It designs the floor once per edition and publishes one generic floor brief; per-sponsor execution such as staging, payment gating, and individual FAQ replies routes to the event-sponsor-fulfillment skill.

Can I convert venue attendee-to-outlet ratios into per-booth power allocations?

No formula bridges attendee-density ratios and exhibitor load, so any conversion would be invented. Instead ask the venue what a booth drop costs and its request deadline, publish per-tier inclusions, and count only booths that actually need power.

What traffic mechanic pulls attendees past low-traffic booths?

A passport or stamp card is the default because it makes every booth a required stop, with stamps given for arriving rather than for listening to a pitch. Promote to a scavenger hunt only when a screen and operator already exist or the floor is too large for a card.