Google Vertex Ai
Analysis
The skill matches its Google Vertex AI purpose, but it delegates broad cloud access through Membrane, installs an unpinned global CLI, and lacks clear approval and scope guardrails.
Findings (9)
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.
The skill allows instructions returned from the Membrane connection flow to guide the agent programmatically, but does not state that those remote instructions must be validated against the user’s goal or treated as untrusted.
`membrane action run <actionId> --connectionId=CONNECTION_ID --json`
The skill enables running Membrane actions against a Google Vertex AI connection, including listed state-changing actions such as creating or canceling tuning jobs, but does not define approval or safety limits.
npm install -g @membranehq/cli@latest
The skill instructs installation of a global npm package using the floating @latest tag, so the executed CLI version can change over time and is not pinned by the skill artifacts.
npx @membranehq/cli connection get <id> --wait --json
The instructions rely on shell execution of npm/npx tooling even though the registry describes the skill as instruction-only with no install spec.
Create Tuning Job | create-tuning-job | Create a new tuning job to fine-tune a Gemini model with your custom data.
The skill can initiate cloud ML jobs and lists other Vertex AI resources such as endpoints, models, datasets, and deployed models; a bad action can propagate into cost, deployment, or data impacts.
Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.
The wording emphasizes convenience and may cause users to overlook the security significance of delegating and refreshing credentials through Membrane.
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
The skill relies on delegated authentication handled by Membrane, but the artifacts do not specify OAuth scopes, project restrictions, credential lifetime, or revocation expectations.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Embed Content | embed-content | Generate embeddings for text content using Vertex AI embedding models.
The skill exposes embedding functionality that processes user text through Vertex AI; this is purpose-aligned, but embeddings can encode sensitive content.
send requests directly to the Google Vertex AI API through Membrane's proxy
The skill uses Membrane as a proxy/gateway between the agent and Google Vertex AI, but the artifacts do not define data handling boundaries, identity guarantees, or permission limits for proxy requests.
