event-b2b-matchmaking

Designs structured 1:1 business meeting programs matching two event populations into booked slots.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Event organizers are often pushed to run 1:1 meeting programs or promise sponsors a number of guaranteed meetings without a defensible way to decide whether the program should exist, how matches are made, what can honestly be promised, or how no-shows are absorbed. This Skill provides ranked decision menus for each of those choices, grounded in consent and measured data rather than vendor benchmarks. ## Core Features & Use Cases - Run-or-not gate: Decides whether a meeting program should exist at all, based on whether a signed package names a meeting number or two populations were deliberately invited to meet. - Matching and scheduling menus: Ranks five matching mechanisms (no program, mutual opt-in, open directory, scored ranking, organizer brokering) and four scheduling mechanics across effort, value, compliance, and efficiency axes. - Quota commitment posture: Shapes what a sponsor package may honestly promise, from no promise to a guaranteed count with verifiable criteria and a fundable make-good. - No-show handling and measurement: Chooses among reconfirm-and-remind, standby refill, doing nothing, and conditional overbooking, with self-measured counting rules for held-versus-booked reporting. - Use Case: A sponsor offers $25,000 if the prospectus prints "20 guaranteed meetings with senior platform engineers." The Skill refuses the bare number, shapes a guaranteed count with evidenced criteria and a defined make-good, and routes clause drafting to the sponsor-agreement skill. ## Quick Start Ask the Skill whether your event should run a 1:1 meeting program and how to structure matching, booking, quota commitments, and no-show handling for it.

Frequently Asked Questions about event-b2b-matchmaking

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

FAQPage Schema
Should our conference run a 1:1 meeting program at all?

Usually no. The program earns its place only when a signed sponsor package names a meeting number or the event deliberately assembled two populations that will not find each other in a corridor. Otherwise the hallway track and expo floor already cover sponsor-attendee contact.

How do I match attendees with sponsors without handing over the attendee list?

Use mutual opt-in or organizer brokering: both sides state what they want, and a pair exists only where both accepted. Never build a directory from registration data, since consent scope was fixed by the wording attendees saw at ticket purchase.

Can we guarantee a sponsor a specific number of meetings?

Only as a guaranteed count with written, verifiable criteria and a make-good you can still fund after the event. A bare number is satisfiable by filling slots with whoever is free, leaving the sponsor worse off than if nothing was promised.

Should we overbook meeting slots to compensate for no-shows?

Not without a measured booked-versus-held count from a previous edition of your own program. Overbooking creates collisions that turn away participants who did everything asked of them; reconfirm-and-remind plus a staffed standby queue is the safer default.

What is the difference between B2B matchmaking and hackathon team formation?

B2B matchmaking pairs two different populations into booked business meetings, and its failure mode is an undelivered sponsor quota. Hackathon team formation groups one population of participants onto build teams, and its failure mode is an unpicked participant.

Why shouldn't we use matchmaking platform benchmark figures for planning?

Published fill rates and no-show percentages come from vendors' own customer bases and are marketing material, not verified planning data. The only legitimate planning number is the held-versus-booked count you measured on your own program's previous editions.