venue-selection
Skill2 starsChanged 3 months agoMITView on GitHub
Use when the user says "find a venue", "where should we host", "restaurant for the dinner", "private dining room", "compare venues", "book the space". Builds the shortlist, computes all-in per head across candidates, checks the requirements that ruin events when missed, and reads the contract terms that cost money. Writes workspace/events/<event>/venue.md.
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-logisticsSkill
- 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
- virtual-eventsSkill
- writing-qualitySkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 52
Put the all-in number in the comparison table for every option and rank on it.
- Distinctive: line 64
Overtime charges: if the room runs past the contracted end
- Distinctive: line 66
Insurance requirements: Ask at booking, not at payment
- Distinctive: line 70
Walk the space: if at all possible, at the same time of day as your event.
- Distinctive: line 83
All-in per head for every candidate: Never compare on menu price
≈ “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
Venue Selection
The menu price is roughly two-thirds of the real price, and the ranking by menu price is frequently not the ranking by final cost. This skill gets to the real number and checks the things that ruin a room.
When to use
- Any hosted event: dinner, roundtable, owned event, suite
- Comparing options for a private dining room
- A venue has been proposed and nobody has read the contract
Inputs
- Reads:
workspace/events/<event>/decision.md,workspace/events/<event>/budget.md, the format plan - Needs from user: the city, the date, the headcount including your team, the budget position, and any exclusions
Workflow
1. Set the requirements before looking at anything
| Requirement | Why it matters |
| Truly private room | Walls and a door, not a curtained corner. Ask directly, and ask whether anything else is booked in the space at the same time |
| One table at your headcount | Two tables of eight is two dinners. Confirm the room seats your number on a single table |
| Its own kitchen | A private dining room with a dedicated kitchen serves a seated dinner on a tight clock far better than one plated across a restaurant. Ask. Few people do |
| A separate reception space | Arrival drinks in the same room you eat in kills the transition. An adjacent lounge on the same floor is ideal |
| Sound and light | Too loud to hear across the table or too dark to read a menu ruins the format |
| Location | Near where the guests work or stay, not near where you like eating. Convenience drives attendance more than prestige |
| Accessibility | Step-free access and restrooms on the same floor. Ask, do not assume |
Note the exclusions explicitly too. Cuisine, chains, anywhere the guests have obviously been to a vendor dinner already, and anywhere a specific stakeholder has ruled out.
2. Build a shortlist of five to seven
Sources: the co-host's or partner's preferred vendors (frequently the best option and it saves days of work), private-dining directories, hotel event teams, and asking the account team where their customers actually go.
A note on prestige. A famous restaurant is not automatically the right answer. Guests at this level have been to the famous ones. A room they have not been in, or one with genuine character, frequently outperforms a familiar three-star.
3. Compute all-in per head for every candidate
Menu per head
+ beverage package (per person per hour x contracted hours)
+ reception cost per head, if arrival is separate
= subtotal
+ service charge or gratuity (%)
+ coordination or administration fee (%)
+ tax (%)
= ALL-IN PER HEADPut the all-in number in the comparison table for every option and rank on it. Show the per-head figure even when there is no cap, so the number is visible rather than hidden.
Expect the stacked add-ons to add a third or more. A cheaper menu at a venue with heavy add-ons routinely loses to a more expensive menu at a venue with light ones.
Label your pricing basis. Verified from a quote, verified from a published kit, or estimated. An estimate presented as a quote is how budgets get missed.
4. Read the contract before signing
- Minimum spend, and whether it covers food and beverage only or includes room hire
- Final headcount date, usually three to seven business days out. After it you pay for the guaranteed number
- Attrition terms
- Cancellation schedule, usually a sliding scale by weeks out
- Deposit and payment terms
- Overtime charges if the room runs past the contracted end
- Outside vendors allowed or not, for photography, AV, gifting
- Insurance requirements. Ask at booking, not at payment
- Corkage, if you are bringing anything
5. Verify before you commit
- Walk the space if at all possible, at the same time of day as your event. Noise and light change completely between lunch and 7pm
- Confirm any negative you have read. Closure rumors, renovation reports, and review complaints are frequently stale or recycled. Ask directly
- Verify the contact details are real. Booking pages and third-party listings carry dead or wrong addresses. Use the venue's own booking system or phone line
- Get the quote in writing, itemized, with the add-ons broken out
6. Hold a backup
Hold a second option informally until the contract is signed. Private rooms in good restaurants go quickly in peak season and a date change is much easier when the alternate is already warm.
Output
- Writes:
workspace/events/<event>/venue.mdwith the requirements, the comparison table with all-in per head, the recommendation with reasoning, and the contract terms to negotiate - Prints: the ranked comparison, the recommendation, the pricing basis per option, and the open verification items
Rules & quality bar
- All-in per head for every candidate. Never compare on menu price
- Label the pricing basis. Verified or estimated, stated
- Ask whether the private room has its own kitchen
- Confirm the room is genuinely private and that nothing else is booked in it
- Read the final headcount and cancellation terms before signing
- Verify contact details through the venue's own channels. Third-party listings carry bad data
- Walk the space at the event's time of day where possible
- Hold a backup until signature
Related skills
- Reads:
event-budget, the format skill - Feeds:
event-logistics,run-of-show - See also:
docs/operations-runbook.mdsection 5,docs/field-notes.mdnote 4
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.

