Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From veeva-pack
Provides performance tuning guidance for Veeva Vault REST API, VQL queries, and VAPIL Java SDK in clinical operations and document management.
How this skill is triggered — by the user, by Claude, or both
Slash command
/veeva-pack:veeva-performance-tuningThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guidance for performance tuning with Veeva Vault REST API, VQL queries, and VAPIL Java SDK.
Guidance for performance tuning with Veeva Vault REST API, VQL queries, and VAPIL Java SDK.
https://{vault}.veevavault.com/api/v24.1/-- List documents by type
SELECT id, name__v FROM documents WHERE type__v = 'Trial Document'
-- Find objects
SELECT id, name__v FROM site__v WHERE status__v = 'active__v'
-- Join related objects
SELECT id, name__v, study__vr.name__v FROM study_country__v
| Error | Cause | Solution |
|---|---|---|
INVALID_SESSION_ID | Session expired | Re-authenticate |
INSUFFICIENT_ACCESS | Missing permissions | Check security profile |
INVALID_DATA | Bad VQL or field name | Validate against metadata |
OPERATION_NOT_ALLOWED | Lifecycle state conflict | Check document state |
See related Veeva Vault skills for more patterns.
8plugins reuse this skill
First indexed Jul 10, 2026
Showing the 6 earliest of 8 plugins
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin veeva-packOptimizes Veeva Vault API costs using REST, VQL queries, and VAPIL Java SDK. For clinical operations, document management, and CRM workflows.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.