• VillaSlotDocumentation
  • Introduction
  • Getting Started
  • Agents
    • Claude Code
    • Codex
    • OpenClaw
    • Hermes
  • API
    • Discovery
      • GETGet my context
    • Villas
      • GETList villas
      • POSTCreate a villa
      • GETGet a villa
      • PATCHRename a villa
      • POSTArchive a villa
      • POSTUpload a villa photo
      • GETGet opening hours
      • PUTReplace opening hours
      • GETGet the rate grid
      • PUTReplace the rate grid
      • GETGet availability
    • Bookings
      • GETList bookings over a period
      • POSTCreate a booking
      • GETGet a booking
      • POSTConfirm a booking
      • POSTComplete a booking
      • POSTCancel a booking
      • POSTReschedule a booking
    • Customers
      • GETList customers
      • POSTCreate a customer
      • POSTImport a batch of customers
      • GETGet a customer
      • PATCHUpdate a customer
    • Booking settings
      • GETGet booking settings
      • PATCHUpdate booking settings
  1. Documentation
  2. Agents
  3. OpenClaw
Buydocschangelogsdemocommunity

OpenClaw

PreviousCodexNextHermes
On this page
Install the VillaSlot skillGenerate an API keyVerify the organizationPrepare a daily booking summaryAct on a client requestLimits and troubleshooting

Use OpenClaw with VillaSlot to review upcoming bookings, check villa availability and prepare operational changes. The skill gives the agent the API contract; your organization API key determines which data it can access.

Install the VillaSlot skill

Run the command on the machine where OpenClaw runs, from the workspace you use with the agent:

bash
npx skills add https://github.com/mikecodeur/skills --skill villaslot

Select OpenClaw in the installer. To target it directly:

bash
npx skills add https://github.com/mikecodeur/skills --skill villaslot --agent openclaw

Choose an installation scope accessible to your OpenClaw instance. If the agent runs on a server, installing the skill on your laptop alone will not make it available there. Open a new session after installation and ask it to use the villaslot skill.

Generate an API key

Sign in to VillaSlot, open Account → API Keys, and create a key for the organization you want to manage. Provide the key securely to OpenClaw's runtime as VILLASLOT_API_KEY and set:

bash
export VILLASLOT_BASE_URL="https://www.villaslot.io"

A background service or container needs these variables in its own environment. Avoid putting the key in a shared chat or tracked workspace file.

Verify the organization

Use the villaslot skill and the API key from your environment.
Read /api/v1/me and list my active villas. Tell me the organization,
its timezone and whether its booking settings are configured.
Do not make changes.

Check the returned organization before asking OpenClaw to manage its listings or bookings. The key acts with its creator's current permissions.

Prepare a daily booking summary

Read tomorrow's bookings in the organization's timezone. Group them
by villa, show the local start and end times, customer names and
booking statuses. Flag unpaid and partially paid bookings separately.
Return the summary here; do not contact customers or change bookings.

The agent should convert the local day boundaries to ISO instants for the calendar query. A booking's confirmation and payment status are separate: a confirmed reservation may still have a balance due.

Act on a client request

After reviewing the summary, you can ask OpenClaw to check another slot, create a customer record or reschedule a booking. Identify the booking and the intended change, and specify whether its current price should be preserved.

Owner/admin permissions are needed to create or edit villa listings, hours and rate grids. Reading a free slot does not guarantee a subsequent booking will succeed: the API checks availability again when writing.

Limits and troubleshooting

A 401 means the key cannot authenticate; a 409 can mean a slot conflict or plan ceiling. Ask the agent to explain the response before retrying. Do not turn a repeated error into an unlimited background retry loop.

The skill does not expose automatic customer messaging, payment collection or refunds. Those actions remain in the application. A scheduled workflow also needs to be configured separately; installing this skill does not create a schedule.

Continue with the Agents index, API reference, or the Skills CLI documentation.