@jeremylongshore/veeva-cost-tuning
A'Veeva Vault cost tuning for REST API and clinical operations.
Install
agr install @jeremylongshore/veeva-cost-tuning --target claudeWrites 1 file into .claude/skills/, pinned to git-7f973b76.
- .claude/skills/veeva-cost-tuning/SKILL.md
Document
name: veeva-cost-tuning description: 'Veeva Vault cost tuning for REST API and clinical operations.
Use when working with Veeva Vault document management and CRM.
Trigger: "veeva cost tuning".
' allowed-tools: Read, Write, Edit, Grep version: 1.3.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io tags:
- saas
- life-sciences
- crm
- veeva compatibility: Designed for Claude Code
Veeva Vault Cost Tuning
Overview
Guidance for cost tuning with Veeva Vault REST API, VQL queries, and VAPIL Java SDK.
Instructions
Key Vault API Concepts
- Authentication: Session-based (username/password or OAuth 2.0)
- Base URL:
https://{vault}.veevavault.com/api/v24.1/ - VQL: SQL-like query language for Vault data
- VAPIL: Open-source Java SDK covering all Platform APIs
- Lifecycle: Documents flow through states (Draft > In Review > Approved)
Common VQL Patterns
-- 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 Handling
| 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 |
Resources
Next Steps
See related Veeva Vault skills for more patterns.
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-7f973b7690702026-07-31