Acuity Scheduling
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Installing the CLI gives locally installed external code the ability to run under the user's account.
The skill asks the user to install a global npm CLI package using the latest version, so the executable code is not pinned or included in the reviewed artifact. This is disclosed and purpose-aligned, but users must trust the external package source.
npm install -g @membranehq/cli@latest
Install only from a trusted environment, verify the Membrane CLI package source, and consider pinning or reviewing the package version if operating in a sensitive environment.
The connected account may allow the agent, through Membrane, to access or change Acuity Scheduling records according to the granted permissions.
The integration requires delegated authentication and ongoing credential refresh for Membrane/Acuity access. This is expected for an Acuity integration, but it is sensitive account authority.
Membrane handles authentication and credentials refresh automatically
Use the least-privileged Acuity/Membrane account possible, review granted permissions, and revoke the connection when the integration is no longer needed.
Mistaken or overly broad use could cancel bookings, change client details, or delete records in the connected Acuity account.
The documented Acuity actions include write and delete operations. These are aligned with the skill's stated management purpose, but they can materially affect business scheduling and client records.
Create Appointment ... Update Client ... Cancel Appointment ... Delete Client | Delete a client by ID
Before canceling, deleting, or updating records, review the target IDs and intended changes, and ask for explicit confirmation for destructive actions.