agentleFS
NowistayNowistay/claude/skills/direct-bookings/SKILL.md

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.

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
  1. Distinctive:

    Use the booking workflow that matches the user's intent and avoid duplicate lookups.

    line 8
  2. Very specific:

    Check the exact stay dates with get_calendar_ari before staging the booking.

    line 13
  3. Very specific:

    Call create_booking_preview with the complete intended booking.

    line 16
  4. Very specific:

    If the user asked only to prepare the booking, stop.

    line 18
  5. Very specific:

    When request_payment=true, provide a positive amount.

    line 20
  6. Distinctive:

    Never request or accept payment-card data, bank credentials, government identifiers, medical or biometric data, account passwords, access …

    line 22
  7. Distinctive:

    Update only direct bookings created in Nowistay.

    line 27
  8. Distinctive:

    Check calendar availability before changing dates.

    line 28
  9. Distinctive:

    If a payment request already exists, do not attempt to change dates or pricing.

    line 29
  10. Distinctive:

    Do not retrieve guest contact details or private booking notes unless the user explicitly asks for that information and it is necessary for …

    line 32
  11. Distinctive:

    Never reconstruct a confirm payload.

    line 34

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Nowistay Direct Bookings

Use the booking workflow that matches the user's intent and avoid duplicate lookups.

Create a booking

  1. Resolve the property once with list_properties.
  2. Check the exact stay dates with get_calendar_ari before staging the booking.
  3. Reuse details the user already supplied. Do not search the guest base by default. Use list_guests only when the user explicitly asks to reuse an existing guest record, and search with information the user already provided.
  4. 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.
  5. Call create_booking_preview with the complete intended booking.
  6. Show a compact summary: property, dates, guest, occupancy, price, currency, status, and whether payment will be requested.
  7. If the user asked only to prepare the booking, stop. If the user explicitly asked to create it, call create_booking_confirm with 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

  1. Find the booking with list_bookings and read it with get_booking.
  2. Update only direct bookings created in Nowistay. If the booking came from an OTA, explain that it cannot be edited through this workflow.
  3. Check calendar availability before changing dates.
  4. If a payment request already exists, do not attempt to change dates or pricing.
  5. Stage with update_booking_preview, summarize the exact differences, then use update_booking_confirm only 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.