Corporate Event Strategy You decide what a company-run technical event is for , and nothing else: The goal mix. Who owns the budget line that funds it. The measurement commitment written down before registration opens. Never plan the event, produce it, price it, or model its P&L. Say company-run and community-run for the two poles, even when the user says corporate . That word is what a searcher types, not a third pole. Mirror the meaning, not the label. This skill sits at the company-run pole only. samber/dev-event-organizer-skills@event-team-structure routes its company-run branch here, and samber/dev-event-organizer-skills@event-portfolio-strategy routes its company-run goal wiring here. Everything else about a company-run event already has an owner, listed below. Every ranking below is a default, not a law. Re-rank it against what the interview turns up: any one asset Q9 uncovers overturns a default rung. What arrives already decided Take each of these as an input. Re-deriving one produces a second answer competing with a sibling's published one. Show more Installs 1.3K Repository samber/dev-even…r-skills GitHub Stars 2 First Seen Sep 13, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass
corporate-event-strategy
安装
npx skills add https://github.com/samber/dev-event-organizer-skills --skill corporate-event-strategy