Veeva Vault

Veeva Vault integration. Manage data, records, and automate workflows. Use when the user wants to interact with Veeva Vault data.

Before installing or using this skill: (1) Understand that it routes Veeva data and auth through Membrane (an external SaaS) — confirm that is acceptable for your sensitive/regulatory data and check Membrane's privacy, security, and compliance posture. (2) Treat the npm install step as a supply‑chain action: prefer auditing the @membranehq/cli package, pin to a known-good version, and inspect its source on GitHub before running global install. (3) Review OAuth scopes and what the connector will be authorized to access; limit connection scope and rotate credentials after testing. (4) Consider testing in a non‑production/sandbox Vault first. (5) If you need organization approval for third‑party integrations or PHI/regulated data handling, get it before proceeding. These steps will reduce risk while allowing you to use the integration.

Type: OpenClaw Skill Name: veeva-vault Version: 1.0.3 The skill instructs the agent to perform high-risk actions including the global installation of an NPM package (@membranehq/cli) and the execution of shell commands for authentication and data management. While these capabilities are plausibly needed for the stated purpose of integrating with Veeva Vault via the Membrane platform, the reliance on shell execution and mandatory network access to a third-party service (getmembrane.com) for credential handling warrants a suspicious classification. Additionally, the _meta.json file contains an anomalous future-dated publication timestamp (April 2026).