event-logistics
Skill2 starsChanged 3 months agoMITView on GitHub
Use for every event with a physical footprint, or when the user says "certificate of insurance", "COI", "shipping to the venue", "load-in", "AV", "what do we need to send", "deadlines", "logistics". Builds the deadline calendar with owners and covers insurance, shipping, receiving, AV, and the pre-flight checklist. Writes workspace/events/<event>/logistics.md.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- simonkoehler/event-skillstheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- simonkoehler/event-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- artifact-evalSkill
- audience-machineSkill
- conference-activationSkill
- event-and-scale-osSkill
- event-budgetSkill
- event-contentSkill
- event-followupSkill
- event-measurementSkill
- event-program-setupSkill
- event-retrospectiveSkill
- event-selectionSkill
- executive-dinnerSkill
- invite-motionSkill
- meeting-engineSkill
- owned-eventSkill
- roundtable-and-salonSkill
- run-of-showSkill
- speaking-and-stageSkill
- sponsorship-negotiationSkill
- staffing-and-briefingSkill
- venue-selectionSkill
- virtual-eventsSkill
- writing-qualitySkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Every one of these earlier than teams assume.
- Distinctive: line 44
Ask the venue, at booking:
- Distinctive: line 65
Test the connection with your own machine during setup, not fifteen minutes before doors
- Distinctive: line 68
Ask whether exhibitor wifi is included and what the bandwidth is.
- Distinctive: line 69
Check signage rules: height caps, whether anything can be affixed to walls, whether free-standing banners are allowed
- Very specific: line 72
If decks are merged into one master file, custom fonts, animation, embedded video, and live demo are all gone.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Event Logistics
The material that lands on a marketer's desk two weeks out and is never in any event marketing content. Getting it right is invisible. Getting it wrong is a booth with nothing on it.
Nothing here is legal or insurance advice. It is the list of things to ask early enough that the people who do give that advice can help.
When to use
- The moment a venue or sponsorship is confirmed
- Two weeks out, when somebody asks what a certificate of insurance is
- Any event where physical materials have to arrive somewhere
Inputs
- Reads:
workspace/events/<event>/contract.md,workspace/events/<event>/venue.md - Needs from user: the organizer's operations contact, the venue's event planner, and who internally can request insurance certificates and approve shipping
Workflow
1. Build the deadline calendar first
Every one of these earlier than teams assume. Put each on a calendar with a named owner the day the event is confirmed.
| Deadline | Typical timing |
| Speaker details: name, exact title, headshot, bio | 2 weeks out, wanted earlier for promotion |
| Session title and abstract | 2 to 4 weeks out. Locked into printed agendas |
| Slides into the merged master file | ~1 week out |
| Printed collateral | ~4 weeks out, not 2 to 3 |
| Certificate of insurance | ~2 weeks out |
| Shipping arrival window | Narrow at both ends |
| Booth position selection | Fixed date, priority by tier |
| Matchmaking platform opening | 2 to 6 weeks out, varies wildly |
| Final headcount to the venue | 3 to 7 business days out |
| Staff registration | Fixed cutoff, frequently early |
| Transferable pass redemption | Hard cutoff. Chase personally |
2. Handle insurance early
A certificate of insurance proves you carry coverage and names the venue and its related entities as additional insureds. Venues will not let you load in without one.
Ask the venue, at booking:
- For their sample certificate. Yours has to match it
- For the exact legal entity names to list as additional insureds. Large buildings frequently require several: owner, management company, operating entity, landlord. One wrong name means a rejected certificate and a resubmission you may not have time for
- The coverage limits, including whether an umbrella policy is required and at what level
- The deadline and the recipient
Send all of it to your broker with the deadline attached. Certificates take days, not hours, and a rejection resets the clock. This applies to restaurants and private rooms too, not just conference halls.
3. Plan shipping against both windows
The organizer's booklet and the venue's exhibitor packet frequently disagree. Work to the stricter reading of both.
- Receiving is business hours on weekdays. A Monday event means shipping the previous week
- Many venues have no receiving department. If nobody was told your boxes are coming, they are not responsible for them. Notify the venue contact with box count and tracking numbers, in writing, a week out
- Carrier restrictions are real. Venues hold certificates for the major carriers and a preferred local courier. Anything else needs its own certificate weeks ahead
- Return labels printed in advance and packed inside the boxes. Materials are typically held only until end of day, especially when another event follows
- Hand-carry limits usually allow roller bags, backpacks, and small boxes. A banner case is a judgment call. Ship it
Label every box on every side with venue name, named venue contact, your company, full address with floor, event name and date, and box number of total.
4. Confirm AV and power
- What the venue supplies against what is rented. Screens, projectors, microphones, speakers, and laptop connections are frequently separate charges
- Test the connection with your own machine during setup, not fifteen minutes before doors
- Bring every adapter, twice. Assume the venue has none
- Confirm outlets at your stand or table, and bring extension cords and a power strip regardless
- Ask whether exhibitor wifi is included and what the bandwidth is. Never plan a live demo on venue wifi without a hotspot
- Check signage rules: height caps, whether anything can be affixed to walls, whether free-standing banners are allowed
5. Confirm the deck production rules
If decks are merged into one master file, custom fonts, animation, embedded video, and live demo are all gone. Decide early whether to ship font files or rebuild in a safe stack. See speaking-and-stage.
6. Run the pre-flight checklist
The week before, confirmed in writing:
- Insurance certificate submitted and accepted, not just sent
- Shipping window confirmed. Boxes labeled, tracking sent to the venue, return labels inside
- Slides submitted in the required format. Fonts resolved
- Speaker details published correctly on the event site
- Staff registered. Transferable passes redeemed or chased
- Meeting schedules distributed, one page per meeting
- Follow-up sequences written and loaded
- Content skeletons written. Photographer briefed
- Final headcount given to the venue
- AV tested or a testing window booked
- Power, adapters, extension cords, hotspot packed
- Lead scanner tested
- Night-before huddle on everyone's calendar
- One named owner of the day, with a phone that stays on
Output
- Writes:
workspace/events/<event>/logistics.mdwith the deadline calendar, insurance requirements, shipping plan, AV confirmations, and the pre-flight checklist - Prints: the deadline calendar with owners, anything unowned, and the items with no confirmed answer
Rules & quality bar
- Every deadline has a named owner and a calendar entry
- Insurance requested the moment the venue is confirmed
- Work to the stricter of two conflicting shipping windows
- Return labels packed inside the boxes
- Notify the venue of every shipment with tracking, in writing
- Accepted, not sent. Confirm the certificate was accepted
- Nothing is assumed. An unconfirmed logistics answer is a risk with a date on it
Related skills
- Reads:
sponsorship-negotiation,venue-selection - Feeds:
run-of-show - See also:
docs/operations-runbook.md, which carries the full detail
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

