Brainshop
Analysis
The BrainShop integration is coherent, but it gives the agent broad authenticated API access through Membrane, including raw requests that can mutate or delete BrainShop data, so users should review its scope before installing.
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 BrainShop API through Membrane's proxy... HTTP method (GET, POST, PUT, PATCH, DELETE).
This provides a raw authenticated API escape hatch, including destructive methods, without clear limits, confirmation requirements, or endpoint scoping.
Install the Membrane CLI so you can run `membrane` from the terminal: npm install -g @membranehq/cli
The skill depends on a globally installed npm CLI, while the registry lists no required binaries or install spec. This appears purpose-aligned, but users should notice the external dependency.
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 login --tenant... The user completes authentication in the browser.
The skill requires delegated Membrane and BrainShop account access with managed credential refresh. This is expected for the integration, but it is sensitive authority.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers... Membrane manages the full Auth lifecycle server-side with no local secrets.
Requests and authentication flow through Membrane as an intermediary gateway to BrainShop. This is disclosed and expected, but it is a data and authorization boundary users should understand.
