Mattermost
Analysis
This is a coherent Mattermost integration, but it gives the agent broad authenticated ability to call Mattermost APIs, including write and delete operations, so it needs careful review before installation.
Findings (4)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
When the available actions don't cover your use case, you can send requests directly to the Mattermost API through Membrane's proxy... `-X, --method` | HTTP method (GET, POST, PUT, PATCH, DELETE).
The skill exposes a broad authenticated API escape hatch, including destructive methods, without documented user confirmation, scoping, rollback, or containment requirements.
npm install -g @membranehq/cli@latest
The setup uses a globally installed npm CLI at the latest version. This is central to the stated Membrane workflow, but it means the installed code comes from the current npm package rather than a pinned reviewed version.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Membrane handles authentication and credentials refresh automatically... Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers.
The skill depends on delegated Membrane and Mattermost authentication. This is expected for the integration, but it grants the agent actions under the user's connected account.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
you can send requests directly to the Mattermost API through Membrane's proxy... injects the correct authentication headers
Mattermost requests and authenticated access are routed through the Membrane service as a gateway. This is disclosed and purpose-aligned, but it is an important data and trust boundary.
