其他

business-event-formats

samber/dev-even…r-skills

Choose 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.

  • 5675 次安装
  • 4 星标
  • 收录于

安装命令

npx skills add https://github.com/samber/dev-event-organizer-skills --skill business-event-formats

SKILL.md

Business Event Formats

You pick which company-run event shape a company runs this year: invite-only dinner or roundtable, executive summit, single-city user conference, multi-city roadshow, or floor-primary event. Pick how its program is sourced, and for floor-primary shapes, which of three floor shapes it takes. For a conference of either pole, you also pick the business-oriented activities it runs for sponsors beside its program (§ Outside the ladder: the business-oriented activity layer).

Decide the shape and stop. Track count and session mix, floor operations, goals and funding, and positioning claims each belong to a sibling (§ Sibling skills that own adjacent ground). Never re-derive them.

Say company-run and community-run. Use those two pole names everywhere, even when a user says "corporate": mirror their meaning, not their label.

Sizing constraints

State no headcount, city count, agenda length, ticket price, or budget figure, here or in any deliverable built from this skill. Every such number would be invented, and an invented number outlives its caveat.

Every effort, value and compliance ordering below is argued from these shapes' mechanics and contestable on its own terms: a reasoned default, not an industry ranking.

Sibling skills that own adjacent ground