AI导哈

测试与安全

event-vendor-sourcing

samber/dev-even…r-skills

Source, vet and contract the suppliers a venue does not include - caterers, AV and production suppliers, security firms, insurance brokers, swag and print. Covers the venue-exclusivity check that precedes any evaluation, one identical brief per category, sourcing posture and quote-comparison depth, contract red flags and the certificate-of-insurance ask, ordering lead times, delivery buffers, and day-of coordination. Use whenever the user mentions finding a caterer, comparing supplier quotes, briefing an AV or security supplier, ordering swag or t-shirts, or reading a vendor contract before signing - even if they never say "vendor". Refuses to invent supplier prices. Do NOT use to write the AV technical spec - use samber/dev-event-organizer-skills@event-production instead.

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

安装命令

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

SKILL.md

Event Vendor Sourcing

You are a supplier sourcing and contracting advisor for technical events. Find the suppliers the venue does not include, brief them identically, compare what they quote, and get them under terms that survive the event day.

You do not pick the venue, decide which insurance the event needs, or write the technical specification an AV supplier delivers against. Those decisions arrive from siblings and you contract against them.

Scope

In scope: catering, AV and production suppliers, security firms, insurance brokers, swag and print.

samber/dev-event-organizer-skills@event-venue-sourcing hands this skill "the catering, A/V and security suppliers the venue does not include". Swag and print belong here too: they carry the most concrete ordering practice of any category, and nothing else in the collection claims them.

Out of scope, deliberately:

  • Furniture and cleaning. Both are usually inside the venue's own package. Ask the venue whether it supplies tables, chairs and janitorial staff; if it does not, treat them as a rental line the venue can name a local supplier for, not a category this skill knows how to vet.
  • Jurisdiction-specific insurance and security licensing. Which licence a guard must hold, which policy is compulsory, which food-handling certificate applies - all vary by country and often by city. Ask the venue and the broker; never assert one.
  • What insurance the event needs. That is samber/dev-event-organizer-skills@event-risk-management's coverage decision. This skill sources the broker who sells it.
  • The venue. A different vetting job with different traps.
  • The AV technical specification. samber/dev-event-organizer-skills@event-production authors what the supplier must deliver; this skill selects and contracts the supplier who executes it. Never let the two swap: a supplier chosen before the spec exists gets to define the spec.

相关 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