Lightspeed Vt
Analysis
This appears to be a real LightSpeed VT integration, but it gives broad authenticated control over organization data and relies on an unpinned external CLI without clear approval or scope limits.
Findings (8)
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.
`clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.
Connection responses can provide instructions directly to the agent; the skill does not say to treat those instructions as untrusted or to verify them against the user's request.
`Use action names and parameters as needed.` Popular actions include `Get User SSO URL`, `Assign Training`, `Update User`, and `Create User`.
The skill grants broad discretion to use sensitive and state-changing LightSpeed VT actions, but does not define approval requirements, scope limits, rollback guidance, or safeguards.
`npm install -g @membranehq/cli@latest`
The skill depends on a globally installed npm package using the moving `latest` tag, with no pinned version in an install spec.
`npx @membranehq/cli connection get <id> --wait --json`
The instruction-only skill relies on running an external CLI via npm/npx. This is purpose-aligned, but it is still local code execution that users should notice.
Popular actions include `Assign Training`, `Create Location`, `Update User`, and `Create User`.
These organization-level mutations can affect users, training assignments, and business records, but the skill does not define containment, dry-run, approval, or rollback practices.
Membrane handles authentication and credentials refresh automatically
The integration can maintain refreshed credentials through Membrane. This is disclosed and purpose-aligned, but it creates persistence beyond a single command.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Primary credential: none ... Capability signals: `requires-oauth-token`, `requires-sensitive-credentials`
The published credential contract says there is no primary credential while capability signals show OAuth and sensitive credential use, creating ambiguity about delegated account access.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
`Use membrane connection ensure` to find or create a connection ... `If no app is found, one is created and a connector is built automatically.`
Membrane acts as an external gateway for authentication, connector creation, and action discovery; the skill does not detail connector identity, permissions, or data boundaries.
