Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
appointment-scheduler
v1.0.0Automated appointment management for beauty salons, clinics, studios, and photo booths. Handles booking requests, calendar sync, conflict detection, reminder...
⭐ 0· 755·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the included scripts and README: booking, conflict detection, reminders, no-show tracking, waitlist, and calendar sync are implemented. The Google Calendar OAuth flow is documented and the code expects OAuth credential/token files in ~/.secrets, which is appropriate for calendar integration.
Instruction Scope
SKILL.md and README instruct running local Node scripts that read/write data under the user's home (~/.openclaw/workspace and ~/.secrets). The runtime instructions do not ask the agent to read unrelated system files, contact unknown endpoints, or exfiltrate arbitrary data. Reminder outputs are printed as JSON for the host agent to hand to a message tool (as documented).
Install Mechanism
Registry metadata lists no install spec (instruction-only), but the bundle includes code and a package.json; README instructs running npm install in the scripts directory. That means installing npm packages (chrono-node, googleapis) from the public registry is required to use the scripts — moderate risk relative to an instruction-only skill but not unexpected for a Node-based tool. No downloads from untrusted URLs or extract steps were observed.
Credentials
The skill declares no required env vars, which is accurate, but it expects and documents local credential/config files (e.g., ~/.secrets/google-calendar-credentials.json and ~/.secrets/google-calendar-token.json, plus ~/.openclaw workspace config and data). Those file accesses are proportional to calendar sync and local data storage, but users should be aware Google OAuth credentials/tokens will be read from the home directory if calendar sync is enabled.
Persistence & Privilege
Skill does not request elevated privileges and does not set always:true. It writes its own config and data under ~/.openclaw/workspace and saves tokens under ~/.secrets — behaviour consistent with a local scheduler. It does not modify other skills or system-wide agent configurations.
Assessment
This package appears to implement an on-disk Node-based appointment scheduler. Before installing or running: 1) Note the registry entry omitted an install spec even though package.json exists — run npm install only in a trusted environment and inspect package-lock.json (it references chrono-node and googleapis). 2) If you enable calendar sync, you'll need to place OAuth credentials/tokens in ~/.secrets — treat those files as sensitive. 3) The scripts read/write data under ~/.openclaw and ~/.secrets; back up any existing files and consider filesystem permissions. 4) If you don't need Google sync or certain features (reminders, waitlist), disable/uninstall the related scripts. 5) The source owner is unknown in the registry metadata; if you require higher assurance, request an upstream repository or signed release, or review the included code yourself before use.Like a lobster shell, security has layers — review code before you run it.
latestvk97easzy8r0n6rkqc67x38apsx81d4q4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.