Hospitality
v1.0.0Hotel and hospitality operations management — reservations, guest services, housekeeping, maintenance, revenue, F&B, events, and staff coordination.
⭐ 0· 91·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description match the SKILL.md: the document is a comprehensive operations guide covering reservations, housekeeping, maintenance, revenue, F&B, events and staff coordination — all consistent with a 'hospitality' agent.
Instruction Scope
SKILL.md prescribes runtime behaviors (heartbeat checks, templates, escalation rules, assignment and overbooking protocols). It does not instruct the agent to read unrelated system files or to call any specific external endpoints, but many actions assume access to operational data (bookings, room status, maintenance tickets, occupancy forecasts) and to channels for outbound communications (guest messaging, manager notifications).
Install Mechanism
No install spec and no code files — the skill is instruction-only, so nothing is written to disk and there are no downloaded packages to evaluate.
Credentials
The skill does not declare or request environment variables or credentials, but its instructions imply the agent will need access to PMS/booking systems, housekeeping/maintenance trackers, messaging/email/SMS channels, revenue management data, and possibly payment records. Because these are sensitive, the absence of explicit required creds means integrations will be configured out-of-band — require careful, least-privilege provisioning.
Persistence & Privilege
always: false and no install actions are specified. The skill does not request persistent system-level privileges or modify other skills/config. Autonomous invocation is allowed (platform default) but not combined here with other high-risk indicators.
Assessment
This skill is an instruction-only operational playbook and appears coherent for hotel operations, but it assumes access to internal systems and guest data that are sensitive. Before enabling or connecting this skill: 1) Identify the exact systems it will interact with (PMS, housekeeping/maintenance tracker, messaging/SMS/email gateway, revenue system, payment gateway). 2) Provide scoped, least-privilege API credentials or service accounts rather than broad admin keys. 3) Require manager approval/confirmation steps for actions with financial or guest-impact (refunds, walking guests, issuing credits). 4) Test in a sandbox environment first to verify templates, escalation flows, and that no unintended messages are sent. 5) Audit logging and retention: ensure all automated actions are recorded and reviewable. 6) Protect guest PII and payment data; comply with relevant privacy/regulatory rules. If you need the skill to operate autonomously with real credentials, plan out the exact integrations and access controls before granting them.Like a lobster shell, security has layers — review code before you run it.
latestvk97dt2xt5xatq2v2738xwk60hx84dfqn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.