Booking Manager

v1.3.2

AI-powered booking manager that connects to any existing booking system and lets business owners manage appointments through their phone (Telegram, WhatsApp,...

1· 116·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (booking manager) match the declared config and env vars: SMTP is required for sending confirmations, and optional DB / Sheets / third-party API credentials are appropriate for connecting to existing booking data sources. No unrelated credentials or binaries are requested.
Instruction Scope
Instructions tell the agent to read and write a workspace file (TOOLS.md) for onboarding, poll configured external endpoints (DBs, Sheets, third-party booking APIs), and send email via the configured SMTP server. Reading/writing TOOLS.md and polling external services are expected for this skill, but they do give the agent access to workspace files and network endpoints — the user should avoid placing secrets in workspace files and confirm which endpoints will be contacted.
Install Mechanism
Instruction-only skill with no install spec and no code files; nothing is downloaded or written to disk by an installer — this is the lowest-risk install posture.
Credentials
Required environment config is SMTP_HOST/SMTP_USER/SMTP_PASSWORD (reasonable for sending emails). The optional database and Google Sheets credentials are relevant to supporting multiple data sources. No unrelated secrets or excessive credential demands are present. The SKILL.md consistently advises storing credentials in openclaw.json and using least-privilege tokens.
Persistence & Privilege
always is false and the skill does not request elevated agent-wide presence or modification of other skills. It does instruct updating TOOLS.md (its own workspace artifacts), which is normal for onboarding/config state.
Assessment
This skill appears coherent for a booking/notification assistant, but take these precautions before installing: 1) Only provide an SMTP app password (not a primary account password) and prefer a dedicated sending account. 2) If you connect a database or Google Sheets, create scoped/least-privilege credentials limited to bookings data. 3) Avoid placing any secrets or unrelated credentials in workspace files (TOOLS.md); keep them in openclaw.json env as advised. 4) Confirm which external APIs/endpoints will be polled and the polling frequency (default 15–30 min) to ensure it fits your privacy and cost constraints. 5) Review the upstream repository (homepage) or ask the publisher for audited code if you want to host the connector logic yourself — this skill is instruction-only and relies on the agent’s built-in network/email capabilities to act on the configured creds.

Like a lobster shell, security has layers — review code before you run it.

latestvk976y66ncvgervbkzvgrk3y3vd844zdp

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

Configenv.SMTP_HOST, env.SMTP_USER, env.SMTP_PASSWORD

Comments