What problem does it solve? Taking a technical audience into a company you do not control is structurally different from renting a venue: the host supplies both the place and the programme, so a host who withdraws deletes the event entirely. This Skill decides how much of your agenda depends on the host and what attendees may see and repeat afterwards, while routing catering, transport, code of conduct, and measurement to their proper owners. ## Core Features & Use Cases - Host-dependency posture selection: Ranks four rungs (host speaker in your room, host-led site visit, negotiated agenda, multi-host circuit) against effort, place value, fit value, and compliance axes with explicit delete rules. - Access and repeatability posture: Chooses between open-on-the-record, named ground rules, per-attendee written undertakings, and host-controlled publication clearance, without naming any legal instrument. - Routing and handoffs: Directs transport, catering, code-of-conduct scope, recording, and goal measurement to sibling skills rather than duplicating them. - Use Case: A meetup organizer whose members want to see how a streaming company runs CI gets a clear recommendation to host the engineer as a speaker instead of planning an office visit, because the question is conversational and nothing physical needs to be seen. ## Quick Start Ask the assistant to design a learning expedition or company site visit for your technical audience, describing the host, the audience's question, and any restrictions the host has stated.
