Name: veeva-vault
Rating: 65.60000000000001 (1 reviews)
Author: membranedev

veeva-vault

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

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/veeva-vault/SKILL.md

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is highly actionable with executable Membrane CLI commands and a solid connection workflow, but it lacks validation/verification guidance for destructive operations and carries minor verbosity. Splitting the action catalog into a reference file would improve disclosure.

Suggestions

Add explicit verification steps around destructive actions (e.g. "Before delete-document, run get-document to confirm the target id; after, run list-documents to verify removal") so destructive workflows have validation checkpoints.

Trim the introductory Veeva Vault marketing paragraph and the "so you can focus on the integration logic rather than auth plumbing" phrasing to reduce token overhead.

Consider moving the Popular actions table into a references/actions.md file linked from the body, keeping only the most common actions inline.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but the opening "Veeva Vault is a cloud-based content management platform..." paragraph and phrases like "so you can focus on the integration logic rather than auth plumbing" add minor over-explanation that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready, executable commands for every common case (install, login, connection ensure/get with --wait, action list/run with --input, request proxy) plus a concrete action-key table, matching the anchor for fully executable guidance covering common cases.	5 / 5
Workflow Clarity	The connection flow has clear state-based sequencing with polling feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED), but destructive actions like delete-document and delete-object-record are listed without any validation or verification step, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	There are no bundle files and the content is well-organized into clear sections with appropriate inline commands; the 18-row Popular actions table and detailed connection state machine could optionally live in a reference file, which keeps this just below the ideal split.	4 / 5
	Total	16 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description cleanly answers both what and when with a distinct niche trigger, but its action verbs are generic rather than concrete. Tightening the capability list with specific operations would raise specificity.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete operations such as "query records with VQL, create and update documents and object records, trigger workflows".

Add a few more natural trigger terms users say, e.g. "documents", "regulatory submissions", "clinical trials", or "VQL".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Veeva Vault domain plus a couple of actions, but the verbs are generic ("manage", "automate") rather than concrete like "extract", "fill", or "merge", so it sits at the anchor for naming the domain with 1-2 actions but not comprehensive.	3 / 5
Completeness	It explicitly states both what it does ("Veeva Vault integration. Manage data, records, and automate workflows.") and when to use it ("Use when the user wants to interact with Veeva Vault data."), matching the anchor for clearly and explicitly answering both with a concrete trigger phrase.	5 / 5
Trigger Term Quality	"Veeva Vault", "data", "records", and "workflows" plus the trigger phrase "interact with Veeva Vault data" give good natural keyword coverage; a few likely user terms (documents, submissions, reports) are missing, so it is above the midpoint but not comprehensive.	4 / 5
Distinctiveness Conflict Risk	Veeva Vault is a specific life-sciences platform, so "Veeva Vault" and "interact with Veeva Vault data" form a clear niche trigger with minimal overlap risk against other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/veeva-vault/SKILL.md
Commit: f484c82

Reviewed: ~3 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.