Beamer
ReviewAudited by ClawScan on May 10, 2026.
Overview
This appears to be a normal Beamer integration, but it requires installing and signing into Membrane and can change or delete Beamer data when used.
Install this only if you trust Membrane’s CLI and are comfortable granting it access to your Beamer account. Before any create, update, delete, or post-publishing action, confirm the exact target and input, and use the least-privileged account or connection available.
Findings (3)
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.
A mistaken or overly broad request could change, publish, or delete Beamer content or user records.
The action catalog and generic run command show that the skill can perform high-impact Beamer mutations such as deleting users or posts and creating announcements. This matches the stated management purpose, but users should treat these as approval-required operations.
Popular actions ... Delete User | delete-user ... Delete Post | delete-post ... Update Post | update-post ... Create Post | create-post ... membrane action run <actionId> --connectionId=CONNECTION_ID --json
Require explicit user confirmation for create, update, and delete actions; show the target IDs and inputs before running them; and prefer list/get actions before destructive changes.
Actions will run with whatever Beamer permissions are granted through the Membrane connection.
The skill requires delegated Membrane/Beamer authentication and ongoing credential refresh. This is expected for a Beamer integration, but it gives the agent actions access under the authenticated connection.
Membrane handles authentication and credentials refresh automatically ... membrane login --tenant --clientName=<agentType>
Use a least-privileged Beamer/Membrane account where possible, review the connection permissions, and revoke the connection when it is no longer needed.
The installed CLI version may change between installs, and trust shifts to the npm package and Membrane CLI supply chain.
The setup asks users to install the latest Membrane CLI globally from npm. This is central to the skill’s purpose, but @latest and global installs can change over time and execute third-party package code locally.
npm install -g @membranehq/cli@latest
Install only from the trusted package source, consider pinning a known-good CLI version, and run it in a controlled environment if the Beamer account is sensitive.