Holded
Analysis
This appears to be a legitimate Holded/Membrane integration, but it gives broad authenticated access to read and change business data, including raw API requests, so it should be reviewed carefully 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.
Proxy requests ... send requests directly to the Holded API through Membrane's proxy ... `-X, --method` | HTTP method (GET, POST, PUT, PATCH, DELETE)
The skill exposes an authenticated raw API path, including write and delete methods, instead of only scoped prebuilt actions.
npm install -g @membranehq/cli
The user is directed to install a global npm CLI outside the registry install spec; this is user-directed and purpose-aligned, but it adds third-party code to the local environment.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
membrane login --tenant ... Membrane handles authentication and credentials refresh automatically
The skill relies on delegated Membrane/Holded authentication and persistent credential refresh, which is expected for this integration but sensitive.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
send requests directly to the Holded API through Membrane's proxy ... injects the correct authentication headers
Holded API traffic and authentication mediation flow through Membrane as a gateway; this is disclosed, but the artifact does not describe logging, retention, or data-handling boundaries.
