AI导哈

其他

event-venue-sourcing

samber/dev-even…r-skills

Find and negotiate the venue for a technical event. Covers the written space program built from an attendance estimate and chosen format (main room, breakouts, hallway track, sponsor tables, power and WiFi density, load-in), a sourcing ladder treating free campus, civic and company-hosted space as a real first rung, site visits at the depth the risk warrants, several venues carried against several dates, and the contract traps - attrition, food-and-beverage minimum, cancellation curve, insurance requirement. Use whenever the user mentions finding a venue, room or space for an event, venue requirements, a site visit, or a venue contract - even if they never say "sourcing". Do NOT use for non-venue suppliers - use samber/dev-event-organizer-skills@event-vendor-sourcing instead.

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

安装命令

npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-venue-sourcing

SKILL.md

Event Venue Sourcing

You are a venue sourcing and negotiation advisor for technical events. Find the space, prove it meets a written requirement sheet, and negotiate terms the organizer can live with - for a conference, a hackathon, or a multi-day event with satellite sites.

You do not decide whether to grow, which date to pick, or what insurance to buy. Those decisions arrive from siblings and you execute against them.

Two things this skill will not supply

  • Venue prices - venue rates are quoted per deal, not published: no rate card holds across markets, seasons and venue classes. Never invent a figure to fill that gap. One narrow, sourced exception exists (a UK marketplace's own published listing prices, see references/contract-traps-and-negotiation.md); treat it only as a planning-stage sense check, never as a number to bring into a negotiation. A fabricated benchmark anchors the organizer on a number the venue can immediately disprove, and the credibility lost is the leverage the rest of the negotiation runs on. Real quotes from three candidates on one identical requirements sheet are the only benchmark that is true for this city, this year, this size.
  • Hybrid and multi-venue technical specifications - choosing a hybrid format is settled on the format side. Translating that choice into venue-side requirements (guaranteed upstream bandwidth, rigging points, camera positions, uplink redundancy, control-room space) sits outside this skill. Do not invent an equipment list or a bandwidth figure; put it to the venue as a question it must answer in writing, and route the specification to samber/dev-event-organizer-skills@event-production and samber/dev-event-organizer-skills@event-format-selection.

Interview

Ask one question at a time, multiple-choice where possible. Questions 6-8 exist because the menus below diverge sharply on time-to-effect, durability and effort; those defaults cannot be chosen for the user.

相关 Skills

dev-event-hiringsamber/dev-even…r-skillsEmployer-side hiring for tech-event-organizing roles - producer/manager/coordinator, and the community-manager-shaped end of the field. Calibrates the scorecard to operating context (in-house, agency, non-profit/community, or a standing conference business), builds the loop from the general event-planner sequence plus CMX's five-competency set and paid mini-audit work sample, flags the "one hire owns sponsorship, content and production" consolidation pattern seen in postings, sources candidates from general event-industry boards since no tech-specific one exists, and gates compensation on named sources (PCMA, BLS, Glassdoor) rather than a blended figure. Use when the user asks how to hire an event producer or manager, write a posting, design a loop, or hire an event community manager. Do NOT use for candidate prep (samber/dev-event-organizer-skills@dev-event-career) or team org design (samber/dev-event-organizer-skills@event-team-structure).设计与多媒体5882tech-podcast-youtube-channelsamber/dev-even…r-skillsRun an organizer's own standing podcast or video channel as a cross-edition media property - whether to sustain a channel at all, the cadence commitment and its named owner in the quiet months, guest sourcing from the speaker pool outward, the two-way feed with the event cycle, and the wind-down or handover when organizers change. Use whenever the user mentions starting a conference podcast or YouTube channel, publishing between editions, where episode guests come from, who owns the show when an organizer leaves, or closing one down - even if they never say "podcast". Do NOT use for cutting one edition's talk recordings into clips - use samber/dev-event-organizer-skills@event-content-repurposing instead.营销与写作5882hackathon-brief-designsamber/dev-even…r-skillsWrite the hackathon challenge document teams read before they build - problem statements sized to the time box, thematic challenge tracks, the published rules and eligibility text, the submission-artifact checklist, sponsor-challenge framing, and naming (never weighting) the evaluation categories. Use whenever the user mentions a hackathon brief, challenge or track prompts, hackathon rules or eligibility, submission guidelines, or turning a sponsor's API into a challenge - even if they never say "brief". Challenge tracks here are thematic categories a team enters, not parallel session streams. Do NOT use for rubric weights and judging mechanics - use samber/dev-event-organizer-skills@hackathon-judging instead.设计与多媒体5879event-talk-selectionsamber/dev-even…r-skillsRun the review and selection process on CFP submissions a technical event already collected - committee composition, how blind review executes (platform hiding versus a dedicated anonymizer role) and what it cannot fix, scoring rubrics, multi-round score-to-shortlist-to-program-fit cascades, conflict-of-interest recusal, diversity and first-time-speaker balancing, acceptance-rate management, and accept/decline/waitlist communication. Use whenever the user mentions a program committee, a talk rating grid, blind CFP review, choosing which submitted talks make the programme, reviewer conflicts of interest, or acceptance and rejection emails - even if they never say "selection". Do NOT use to design the call itself - use samber/dev-event-organizer-skills@event-cfp-design.测试与安全5875event-landing-pagesamber/dev-even…r-skillsBuild a technical event's public front door and the small site around it - the page shape for the funding model (a ticketed event's single-CTA hero, or a free event's stats hero with no registration to sell), the section set, a date-gated CTA state machine so Propose renders only during the CFP window and Register only inside the registration window, the accessibility target, and the event structured data. Use whenever asked to build or review a conference, meetup or hackathon website, write the event home page, decide what the page should show before tickets go on sale, or run a pre-launch check on an event site. Do NOT use to set prices or positioning - use samber/dev-event-organizer-skills@event-ticket-pricing or samber/dev-event-organizer-skills@event-positioning.测试与安全5872event-date-selectionsamber/dev-even…r-skillsPick the date a technical event runs on - the decision every other plan hangs off. Covers weekday versus weekend from whose calendar the audience lives on (working professionals versus students), seasonality and the calendars constraining the real audience, competing and anchor events scanned for both conflict and deliberate piggybacking, candidate windows negotiated against venue availability instead of one date fixed first, and the announcement gate on payment handling existing. Use whenever asked to choose an event date, pick a conference weekend, check date conflicts with other events, decide how far ahead to announce, or resolve a clash with a competing event. Do NOT use for the work-back schedule from that date - use samber/dev-event-organizer-skills@event-planning-timeline.智能体工作流5871