direct-bookings
Skill0 starsChanged 37 days agoMITView on GitHub
Create or update direct Nowistay bookings with availability checks, minimum required guest details, pricing, status, operational notes, and optional payment links. Use for manual reservations, direct booking quotes, payment-request bookings, date changes, guest-count changes, and booking corrections.
In this repository8 other files it gives its agents.
- calendar-revenueSkill
- daily-briefSkill
- guest-messagingSkill
- guest-recordsSkill
- portfolio-reportingSkill
- property-knowledgeSkill
- team-operationsSkill
- welcome-guideSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 7 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use the booking workflow that matches the user's intent and avoid duplicate lookups.
- Very specific: line 13
Check the exact stay dates with get_calendar_ari before staging the booking.
- Very specific: line 16
Call create_booking_preview with the complete intended booking.
- Very specific: line 18
If the user asked only to prepare the booking, stop.
- Very specific: line 20
When request_payment=true, provide a positive amount.
- Distinctive: line 22
Never request or accept payment-card data, bank credentials, government identifiers, medical or biometric data, account passwords, access …
- Distinctive: line 27
Update only direct bookings created in Nowistay.
- Distinctive: line 28
Check calendar availability before changing dates.
- Distinctive: line 29
If a payment request already exists, do not attempt to change dates or pricing.
- Distinctive: line 32
Do not retrieve guest contact details or private booking notes unless the user explicitly asks for that information and it is necessary for …
- Distinctive: line 34
Never reconstruct a confirm payload.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Nowistay Direct Bookings
Use the booking workflow that matches the user's intent and avoid duplicate lookups.
Create a booking
- Resolve the property once with
list_properties. - Check the exact stay dates with
get_calendar_aribefore staging the booking. - Reuse details the user already supplied. Do not search the guest base by default. Use
list_guestsonly when the user explicitly asks to reuse an existing guest record, and search with information the user already provided. - Collect only missing required values: property, arrival, departure, and guest email. Explain that email is required to create and service a direct booking. Ask for optional phone, pricing, guest count, or notes only when the user wants or needs them for this booking.
- Call
create_booking_previewwith the complete intended booking. - Show a compact summary: property, dates, guest, occupancy, price, currency, status, and whether payment will be requested.
- If the user asked only to prepare the booking, stop. If the user explicitly asked to create it, call
create_booking_confirmwith only the approval token.
When request_payment=true, provide a positive amount. Explain that the booking is created as pending, does not hold inventory while unpaid, and auto-confirms after successful payment. Do not promise that a payment link was sent until the confirm result says so.
Never request or accept payment-card data, bank credentials, government identifiers, medical or biometric data, account passwords, access tokens, or unrelated personal information. Keep free-text notes short and strictly operational.
Update a booking
- Find the booking with
list_bookingsand read it withget_booking. - Update only direct bookings created in Nowistay. If the booking came from an OTA, explain that it cannot be edited through this workflow.
- Check calendar availability before changing dates.
- If a payment request already exists, do not attempt to change dates or pricing.
- Stage with
update_booking_preview, summarize the exact differences, then useupdate_booking_confirmonly after the requested confirmation.
Do not retrieve guest contact details or private booking notes unless the user explicitly asks for that information and it is necessary for the requested booking operation.
Never reconstruct a confirm payload. Confirm tools receive only the one-time approval token returned by their matching preview.
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.

